Close the last open import pins and the workplan (T04)

interface-canon corrected its Interface and Endpoint pins at 20d7bfc2. Both were
pinned twice, to ITC-LAND and ITC-NET, because ITC-LAND section 13.2 lists them
in a seed-concept block while the Network Model defines them. Landscape section
13.2 now says in this repository that Interface, Endpoint and API are pointers
there and that the Network Model owns the first two, so the next reader does not
repeat it.

That is the fourth time in one day a list of concept names was read as a
definition, after CARING's Scope ladder, CARING's Environment values, and the
Landscape seeds that hid SoftwareSystem and SoftwareComponent. The closure
section names the pattern.

Both boundaries now resolve completely, security-canon 11 of 11 and
interface-canon 23 of 23, the registered copy is refreshed to the corrected
revision, and validation carries no drift warnings. The CLI test is rebuilt from
a deliberately broken copy so that a partner fixing its own pins can no longer
break this repository's suite.

make check passes with 59 tests, clean validation and no warnings.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3588@bnt-lap001
Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da

infospace/interfaces/interface-canon-boundary.md

@@ -87,4 +87,13 @@ different owner than the manifest pins, is reported as a
 `federation_import_drift` warning naming this partner. It is a warning and not an
 error because a stale partner pin is not this repository's file to fix.
 
-Current result: **23 of 25 declared imports resolve** and all seven pinned hashes match. `Interface` and `Endpoint` remain pinned to ITC-LAND while the Network Model declares them; raised with interface-canon by State Hub message `13d355f2-554b-4a3a-a0ef-3f69eeafeae9` on 2026-09-20 and unanswered as of that date. The two warnings stand until that pin is corrected or qualified in place.
+Current result: **23 of 23 declared imports resolve**, all seven pinned hashes
+match, no drift.
+
+The `Interface` and `Endpoint` pins were corrected in interface-canon at
+`20d7bfc2` on 2026-09-20. Both names had been pinned twice, to ITC-LAND and to
+ITC-NET; the ITC-LAND pins are dropped, since section 13.2 lists them as pointers
+while the Network Model defines and owns them. Landscape section 13.2 now says so
+in InfoTechCanon, so the next reader does not repeat it. The accepted
+dispositions are unchanged: this was a citation fix, and the mapping tables that
+cite ITC-LAND section 13.2 as a related seed stand as they are.

infospace/interfaces/manifests/interface-canon.json

@@ -9,11 +9,10 @@
       "path": "infospace/models/landscape/InfoTechCanonLandscapeModel.md",
       "sha256": "4190b044fbd5e3eecf7b28e08608e99c7de3af5dd5f3a7554edee02423967fb1",
       "concepts": [
-        "Interface",
-        "Endpoint",
         "SoftwareSystem",
         "SoftwareComponent"
-      ]
+      ],
+      "note": "Interface and Endpoint were pinned here and to itc-net. ITC-LAND section 13.2 lists them as pointers; the Network Model defines and owns them, so they are pinned to itc-net alone. Corrected 2026-09-20 after InfoTechCanon INFO-WP-0028 name resolution."
     },
     {
       "model": "itc-ident",

infospace/interfaces/manifests/manifests.yaml

@@ -17,6 +17,6 @@ manifests:
   - partner: interface-canon
     file: interface-canon.json
     retrieved_from: infospace/models/interface/imports.json
-    partner_revision: 37fbe245bfd00fb1271af368eec7f0161247d57f
+    partner_revision: 20d7bfc2c3687fd15f00de10916d9ef976bf90ec
     retrieved_at: "2026-09-20"
     boundary: ../interface-canon-boundary.md

infospace/models/landscape/InfoTechCanonLandscapeModel.md

@@ -728,6 +728,14 @@ The Software and Solution domain represents logical and design-time software str
 
 ## 13.2 Seed Concepts
 
+`Interface`, `Endpoint` and `API` appear below as pointers into the software and
+solution domain, not as definitions. The
+[Network Model](../network/InfoTechCanonNetworkModel.md) defines and owns
+`Interface`, a network attachment point of a node, and `Endpoint`, an addressable
+network surface; this model imports them. `SoftwareSystem` and
+`SoftwareComponent` are defined here and declared in this artifact's
+`owned_concepts`.
+
 ```text
 SoftwareSystem
 Application