coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Check import manifests by hash and name together (INFO-WP-0028 T01-T03)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
import-review takes any partner manifest and returns, per concept, whether the
name resolves in the ownership index and to which artifact, and per entry
whether the pinned SHA-256 matches the blob at the declared source commit. Both
run in one pass so neither can be recorded without the other, which is the
failure this workplan exists to prevent. It exits non-zero on a finding, reads
JSON or YAML, needs no partner checkout, and carries its own limit: resolution
proves a name exists and names one owner, nothing more.

Accepted manifests are registered under infospace/interfaces/manifests/ as
provenance-preserving copies owned by the partner, with the partner revision and
retrieval date recorded. Editing a copy to make a check pass is forbidden in the
file itself. Validation re-resolves them and reports drift as
federation_import_drift, a warning naming the partner rather than an error,
because a stale partner pin is not this repository's file to fix.

The review kit gains an extension-boundary-review template requiring hash count,
resolution count and conflict count as three separate lines, and an operating
rule saying one is never evidence of another. Both boundary files carry the
standing-check result.

Verified live: security-canon resolves 11 of 11, interface-canon 23 of 25 with
the two known Interface and Endpoint pins. make check passes with 58 tests,
clean validation and those two 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
This commit is contained in:
tegwick 2026-09-20 23:43:34 +02:00
parent d1254aabe6
commit e1a6314131
14 changed files with 513 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

13
infospace/interfaces/security-canon-boundary.md
View file

@ -106,3 +106,16 @@ the wrong artifact or a name InfoTechCanon never used, not a contested concept.
file that was pinned. It says nothing about whether the concept named in the
manifest exists in it. Both checks are needed, and only the first was run in the
original acceptance.
## Standing check — 2026-09-20 (INFO-WP-0028)
This partner's import manifest is registered at
`infospace/interfaces/manifests/security-canon.json` as a provenance-preserving copy and is
re-resolved on every `make check`. Hash and name are checked together by
`info_tech_canon import-review`; a name that stops resolving, or resolves to a
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: **11 of 11 declared imports resolve**, all six pinned hashes match, no drift.