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

18
infospace/examples/repo-manager-statehub.md
View file

@ -7,8 +7,10 @@ in the [consumer source manifest](../reviews/2026-09-09/repo-manager-sources.jso
and [provider source manifest](../reviews/2026-09-09/state-hub-sources.json).
This is a source-based application of InterfaceCanon to an existing integration.
It proves that the vocabulary can describe the consumer; it does not assert that
Repo Manager has adopted this canon or published a reciprocal card.
The initial example proved the vocabulary could describe the consumer. Repo
Manager has since accepted this documentation mapping in a
[pinned owner record](../reviews/acceptance/repo-manager-sources.json). Adoption
is limited to this interface description and reviewed model 0.1.1.
| Concept | Concrete interpretation | Source evidence |
| --- | --- | --- |
@ -53,4 +55,14 @@ Boundary acceptance cases:
Unresolved implementation detail: the response shape is implied by provider code
rather than a dedicated response schema. That limits machine contract checking,
not the ability to model the exchange. No provider change is required by this
review. Consumer adoption and reciprocal acceptance are tracked in INTERFACE-WP-0004.
review. Consumer adoption is now recorded in INTERFACE-WP-0004-T02;
InfoTechCanon boundary acceptance remains tracked in T01.
## Consumer-owned review clarification
The consumer checks health identity and reads the receipt outcome. It does not
independently validate the full receipt schema or compare returned commit fields;
the provider enforces equality with the derived Forge commit. The presence of an
Idempotency-Key header alone does not prove provider deduplication behavior.
Authentication, TLS, HTTP-version, and gateway properties remain unestablished by
this mapping. These limits match the committed Repo Manager acceptance record.