coulomb/interface-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record Repo Manager adoption and complete publication assessment

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87
This commit is contained in:
tegwick 2026-09-09 22:45:40 +02:00
parent 95eb7c9081
commit 35e30e3731
8 changed files with 79 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

10
infospace/interfaces/federation.yaml
View file

@ -15,6 +15,10 @@ peers:
relationship: FIAM terminology and conformance authority
review_record: docs/interface-canon-boundary.md
acceptance_manifest: infospace/reviews/acceptance/facetted-interfaces-sources.json
- repository: repo-manager
relationship: consumer of interface terminology for Statehub synchronization documentation
review_record: docs/interface-canon-statehub-consumer.md
acceptance_manifest: infospace/reviews/acceptance/repo-manager-sources.json
- repository: commerce-canon
relationship: structural precedent for a focused domain canon
exports:
@ -22,7 +26,7 @@ exports:
kind: domain-model
path: infospace/models/interface/InterfaceCanonInterfaceModel.md
status: draft
availability: referenceable for review; adoption not asserted
availability: draft reference; Repo Manager documentation adoption is recorded for reviewed version 0.1.1
imports:
- repository: info-tech-canon
artifacts: [itc-land, itc-ident, itc-evid, itc-gov, itc-data, itc-infospace, itc-net]
@ -35,9 +39,9 @@ mapping_rules:
- FIAM retains ownership of standard semantics, schemas, and conformance.
- Local definitions remain FIAM-qualified where upstream names overlap.
known_deviations:
- FIAM accepted draft 0.1.1 derivation and authority boundaries; other acceptance/adoption evidence remains tracked in INTERFACE-WP-0004.
- FIAM accepted draft 0.1.1 derivation and authority boundaries; Repo Manager adopted that documentation mapping; InfoTechCanon committed acceptance remains pending.
- The completed identity/commerce migration ledger is not a universal registration gate.
- Evidence records require an explicit assertion/source mapping, not a direct alias.
expectations:
- Review source changes and retain commit and content-hash provenance.
- Initial mapping and consumer-description review is complete in INTERFACE-WP-0003; external acceptance and adoption remain INTERFACE-WP-0004.
- Initial mapping and consumer-description review is complete in INTERFACE-WP-0003; consumer adoption and draft publication assessment are complete in INTERFACE-WP-0004-T02; T01 awaits InfoTechCanon committed acceptance.