interface-canon/infospace
tegwick 20d7bfc2c3 Pin Interface and Endpoint to the model that defines them
Both names were pinned twice, to itc-land and to itc-net. InfoTechCanon's
name-resolution check (INFO-WP-0028) reports that ITC-LAND section 13.2 lists
Interface, Endpoint and API as pointers into the software and solution domain
without defining them, while the Network Model defines and owns both. The
itc-land pins are dropped; itc-net already carried them.

This is a citation fix, not a change of position. The accepted boundary already
treats the Landscape Interface seed and the Network attachment-point Interface as
contextual mappings rather than universal exact aliases, and the mapping tables
that cite ITC-LAND section 13.2 as a related seed stay as they are.

SoftwareSystem and SoftwareComponent keep their itc-land pins and now resolve:
InfoTechCanon declared them under INFO-WP-0027-T04 after finding they sat in a
seed-concept list its extraction could not read.

All 23 declared imports now resolve to the artifact they are pinned to.

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
2026-09-20 23:48:17 +02:00
..
assimilation/fiam Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
examples Apply InfoTechCanon acceptance consistently across mappings and examples 2026-09-09 23:06:06 +02:00
interfaces Pin InfoTechCanon acceptance and complete federation workplan 2026-09-09 22:50:47 +02:00
kernel Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
mappings Apply InfoTechCanon acceptance consistently across mappings and examples 2026-09-09 23:06:06 +02:00
models/interface Pin Interface and Endpoint to the model that defines them 2026-09-20 23:48:17 +02:00
reviews Pin InfoTechCanon acceptance and complete federation workplan 2026-09-09 22:50:47 +02:00