From 35e30e3731fcd08719a823c252b3f1b8f7d1f074 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 9 Sep 2026 22:45:40 +0200 Subject: [PATCH] Record Repo Manager adoption and complete publication assessment Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87 --- SCOPE.md | 5 ++-- WORK-RECORDS.md | 2 +- infospace/examples/repo-manager-statehub.md | 18 +++++++++++--- infospace/interfaces/federation.yaml | 10 +++++--- infospace/reviews/acceptance/README.md | 24 ++++++++++++++++--- .../acceptance/repo-manager-sources.json | 14 +++++++++++ reviews/INTERFACE-WP-0004/README.md | 2 +- ...INTERFACE-WP-0004-federation-acceptance.md | 18 +++++++++++++- 8 files changed, 79 insertions(+), 14 deletions(-) create mode 100644 infospace/reviews/acceptance/repo-manager-sources.json diff --git a/SCOPE.md b/SCOPE.md index f5caf7e..890b9ad 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -19,5 +19,6 @@ Draft 0.1.2 derives its vocabulary from FIAM v0.2 Draft 6 and the frozen Core. No local standard or runtime service is published. Source pins and reviewed mapping boundaries are explicit. The initial mapping -and consumer-description review is complete; external acceptance and adoption -are tracked in INTERFACE-WP-0004. +and consumer-description review is complete. FIAM acceptance and Repo Manager +documentation adoption are pinned. INTERFACE-WP-0004-T01 awaits committed +InfoTechCanon acceptance; publication remains draft after the T02 assessment. diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md index fbf55a4..1a0ac87 100644 --- a/WORK-RECORDS.md +++ b/WORK-RECORDS.md @@ -22,4 +22,4 @@ | task | INTERFACE-WP-0003-T02 | done | — | workplans/INTERFACE-WP-0003-mapping-and-consumer-review.md | | task | INTERFACE-WP-0003-T03 | done | — | workplans/INTERFACE-WP-0003-mapping-and-consumer-review.md | | task | INTERFACE-WP-0004-T01 | wait | — | workplans/INTERFACE-WP-0004-federation-acceptance.md | -| task | INTERFACE-WP-0004-T02 | wait | — | workplans/INTERFACE-WP-0004-federation-acceptance.md | +| task | INTERFACE-WP-0004-T02 | done | — | workplans/INTERFACE-WP-0004-federation-acceptance.md | diff --git a/infospace/examples/repo-manager-statehub.md b/infospace/examples/repo-manager-statehub.md index e75419e..88315cf 100644 --- a/infospace/examples/repo-manager-statehub.md +++ b/infospace/examples/repo-manager-statehub.md @@ -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. diff --git a/infospace/interfaces/federation.yaml b/infospace/interfaces/federation.yaml index 0a682c2..590f63a 100644 --- a/infospace/interfaces/federation.yaml +++ b/infospace/interfaces/federation.yaml @@ -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. diff --git a/infospace/reviews/acceptance/README.md b/infospace/reviews/acceptance/README.md index 1cb0af3..d225a26 100644 --- a/infospace/reviews/acceptance/README.md +++ b/infospace/reviews/acceptance/README.md @@ -8,7 +8,7 @@ record before a message reply arrives; uncommitted files are not a pinned receip | --- | --- | --- | | facetted-interfaces | [Pinned acceptance source](facetted-interfaces-sources.json), commit cceb005c9cacbc1705c7a3f8e7367255de8a5731 | Codex acting for FIAM accepted draft 0.1.1 derivation fidelity and authority boundaries. No blocking semantic corrections; no stable promotion or runtime certification. | | info-tech-canon | `infospace/interfaces/interface-canon-boundary.md` observed in the peer checkout | Agent acceptance text and clarifications are present, but the file has no containing commit at this check. Await a committed review record before counting T01 complete. | -| repo-manager | No `docs/interface-canon-statehub-consumer.md` or other InterfaceCanon adoption reference found in docs/workplans/README at this check | Consumer-owned adoption remains pending; T02 stays open. | +| repo-manager | [Pinned adoption source](repo-manager-sources.json), commit 84df076e95ccafaccb1d8f9ef0878da4cf9278a7 | Codex accepted draft 0.1.1 for documentation of the existing Statehub synchronization interface. No runtime dependency, blanket stable approval, or FIAM conformance claim. | ## Implemented clarifications @@ -32,6 +32,24 @@ FIAM standard pins and all shared-model import pins remain unchanged. ## Remaining work T01 needs the committed InfoTechCanon boundary record; FIAM's part is recorded. -T02 needs consumer-owned adoption evidence and a publication assessment. Keep -both tasks open and the model/card draft. The migration ledger remains outside +T02 is complete: consumer-owned adoption is pinned and publication was assessed +below. Keep T01 open and the model/card draft. The migration ledger remains outside this extension's acceptance scope. + +## Consumer adoption and publication assessment + +Repo Manager adopted the mapping with explicit limits: its client checks primary +health and consumes the outcome, but does not independently validate the entire +receipt schema or compare returned commit fields. Commit equality is checked by +the provider. Sending an idempotency header does not itself prove server-side +deduplication. These limits are now explicit in the local consumer example. + +Both FIAM and Repo Manager reviewed the requested 0.1.1 source revision. Repo +Manager acknowledges the later network-Port clarification while retaining its +0.1.1 review pin. This is evidence of scoped documentation adoption; it does not +establish that either owner reviewed all of 0.1.2 or accepted a stable standard. + +Publication decision: retain draft 0.1.2. Consumer adoption is sufficient to close +the bounded T02 evidence-and-assessment task; stable promotion remains premature +while InfoTechCanon's review lacks a committed record and the approvals themselves +are explicitly draft-scoped. A completed assessment may conclude “remain draft.” diff --git a/infospace/reviews/acceptance/repo-manager-sources.json b/infospace/reviews/acceptance/repo-manager-sources.json new file mode 100644 index 0000000..e6f1447 --- /dev/null +++ b/infospace/reviews/acceptance/repo-manager-sources.json @@ -0,0 +1,14 @@ +{ + "schema_version": 1, + "source_repository": "repo-manager", + "source_commit": "84df076e95ccafaccb1d8f9ef0878da4cf9278a7", + "sources": [ + { + "path": "docs/interface-canon-statehub-consumer.md", + "sha256": "87d9e6f1dccaacbd032de7f987ad74b503828a6c476557b4603c12c56adffc60" + } + ], + "reviewed_interface_commit": "1fc82ec6655ed286cea3be284e33d08e7b27edc3", + "reviewed_model_version": "0.1.1", + "acceptance_scope": "documentation of the existing Statehub projection interface; no runtime dependency or stable-canon promotion" +} diff --git a/reviews/INTERFACE-WP-0004/README.md b/reviews/INTERFACE-WP-0004/README.md index a5155fc..e255781 100644 --- a/reviews/INTERFACE-WP-0004/README.md +++ b/reviews/INTERFACE-WP-0004/README.md @@ -34,7 +34,7 @@ reopening is proposed. Review belongs with the living canon/source/consumer owne ## Next action FIAM acceptance is now pinned from its committed owner record. Await committed -InfoTechCanon review and Repo Manager adoption evidence; check peer Git records +InfoTechCanon review; Repo Manager adoption is now pinned. Check peer Git records as well as the three recorded message threads. Keep this workplan open until actual acceptance or corrections are recorded. Sending a request is not owner acceptance. diff --git a/workplans/INTERFACE-WP-0004-federation-acceptance.md b/workplans/INTERFACE-WP-0004-federation-acceptance.md index d1e73f4..17c9ad5 100644 --- a/workplans/INTERFACE-WP-0004-federation-acceptance.md +++ b/workplans/INTERFACE-WP-0004-federation-acceptance.md @@ -39,7 +39,7 @@ Done when accepted boundaries and their source records are recorded. ```task id: INTERFACE-WP-0004-T02 -status: wait +status: done priority: medium state_hub_task_id: "b9c8cedd-9aa0-5243-b3b5-880a3f0da9c9" ``` @@ -93,3 +93,19 @@ draft; prior review targets remain explicitly 0.1.1. Validation: make check-sources, local YAML parsing, pinned interface-card schema, and model/manifest/card version agreement. No runtime code changed. + +## Consumer adoption implemented — 2026-09-09 + +T02 is done. Repo Manager's committed acceptance at +`84df076e95ccafaccb1d8f9ef0878da4cf9278a7` is pinned in the +[acceptance report](../infospace/reviews/acceptance/README.md). The example now +states the client/provider validation boundary and the limits of idempotency-header +evidence. The federation card records scoped adoption at reviewed version 0.1.1. + +Publication was assessed and remains draft 0.1.2: documented adoption does not +itself imply stable approval. T01 still waits for InfoTechCanon's committed record; +its checkout contains review text but no containing commit at this check. FIAM's +committed acceptance already satisfies its portion. No new residual task is needed. + +Validation: source-integrity checks, local YAML and pinned card-schema validation, +plus workplan/index status consistency. No runtime implementation changed.