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 |
||
|---|---|---|
| .. | ||
| agent | ||
| artifacts | ||
| assimilation | ||
| concepts | ||
| evaluations | ||
| examples | ||
| indexes | ||
| interfaces | ||
| kernel | ||
| mappings | ||
| models | ||
| patterns | ||
| profiles | ||
| reports | ||
| schemas | ||
| standards | ||
| validation | ||
| views | ||
| infospace.yaml | ||
| README.md | ||
InfoTechCanon Infospace
This directory is the single concrete infospace implemented by this repository. The repository root remains the service, governance, and workplan shell.
The current placement pass copies the seed documents into canonical
kernel/, models/, and standards/ paths while keeping seeds/ as
provenance until the scaffold migration is reviewed.