From 95eb7c9081abc0de2d5ffc3238c0d52bbf99fc97 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 9 Sep 2026 22:38:31 +0200 Subject: [PATCH] Record FIAM acceptance and clarify shared interface mappings Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87 --- README.md | 2 +- SCOPE.md | 2 +- canon.yaml | 6 +-- infospace/interfaces/federation.yaml | 7 +++- infospace/mappings/upstream.md | 16 +++++++- .../interface/InterfaceCanonInterfaceModel.md | 5 ++- infospace/reviews/acceptance/README.md | 37 +++++++++++++++++++ .../facetted-interfaces-sources.json | 14 +++++++ reviews/INTERFACE-WP-0004/README.md | 7 +++- ...INTERFACE-WP-0004-federation-acceptance.md | 17 +++++++++ 10 files changed, 101 insertions(+), 12 deletions(-) create mode 100644 infospace/reviews/acceptance/README.md create mode 100644 infospace/reviews/acceptance/facetted-interfaces-sources.json diff --git a/README.md b/README.md index 14ee1ca..377e4ea 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ the FIAM standard maintained in facetted-interfaces. Like CommerceCanon for commercial terminology, this repository adds domain semantics while importing shared concepts from InfoTechCanon. The initial model -is **draft 0.1.1**, based on **FIAM v0.2 Draft 6** and its frozen v0.2 Core. +is **draft 0.1.2**, based on **FIAM v0.2 Draft 6** and its frozen v0.2 Core. - [Intent](INTENT.md) and [scope](SCOPE.md) - [Canon manifest](canon.yaml) and [contribution rules](infospace/kernel/InterfaceCanonCore.md) diff --git a/SCOPE.md b/SCOPE.md index 884c26b..f5caf7e 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -16,7 +16,7 @@ ## Current state -Draft 0.1.1 derives its vocabulary from FIAM v0.2 Draft 6 and the frozen Core. +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 diff --git a/canon.yaml b/canon.yaml index 720e2b3..66440a6 100644 --- a/canon.yaml +++ b/canon.yaml @@ -1,7 +1,7 @@ repository: interface-canon title: InterfaceCanon status: draft -version: 0.1.1 +version: 0.1.2 description: Interface-domain semantics extending InfoTechCanon and derived from FIAM. layout: layout_family: kernel-models-standards @@ -20,10 +20,10 @@ models: title: InterfaceCanon Interface Model path: infospace/models/interface/InterfaceCanonInterfaceModel.md status: draft - version: 0.1.1 + version: 0.1.2 standards: [] interface_cards: - id: interface-canon/federation-interface path: infospace/interfaces/federation.yaml status: draft - version: 0.1.1 + version: 0.1.2 diff --git a/infospace/interfaces/federation.yaml b/infospace/interfaces/federation.yaml index b1e6c3b..0a682c2 100644 --- a/infospace/interfaces/federation.yaml +++ b/infospace/interfaces/federation.yaml @@ -3,7 +3,7 @@ title: InterfaceCanon Federation Interface Card consumer: interface-canon canon_surfaces: [interface-model] status: draft -version: 0.1.1 +version: 0.1.2 owner: interface-canon schema_source: repository: info-tech-canon @@ -13,6 +13,8 @@ peers: relationship: shared-concept upstream; interface-domain extension - repository: facetted-interfaces relationship: FIAM terminology and conformance authority + review_record: docs/interface-canon-boundary.md + acceptance_manifest: infospace/reviews/acceptance/facetted-interfaces-sources.json - repository: commerce-canon relationship: structural precedent for a focused domain canon exports: @@ -33,7 +35,8 @@ mapping_rules: - FIAM retains ownership of standard semantics, schemas, and conformance. - Local definitions remain FIAM-qualified where upstream names overlap. known_deviations: - - Reciprocal cards and federation ownership-ledger acceptance are not yet established. + - FIAM accepted draft 0.1.1 derivation and authority boundaries; other acceptance/adoption evidence remains tracked in INTERFACE-WP-0004. + - 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. diff --git a/infospace/mappings/upstream.md b/infospace/mappings/upstream.md index 7ace946..6d484ac 100644 --- a/infospace/mappings/upstream.md +++ b/infospace/mappings/upstream.md @@ -15,7 +15,7 @@ This is a draft local mapping; no upstream ownership transfer is asserted. | Assertion | ITC-GOV Assertion | FIAM specializes architectural property/relation assertions with evidence and polarity. | | FIAM evidenceRecord | Map to ITC-EVID Evidence plus Evidence Source | FIAM evidenceRecord is support metadata with source, mode and confidence. ITC Evidence is an assertion drawn for a question; source container is separately identified. This is not a one-to-one rename. | | Evidence score | ITC-EVID Evidence strength | A FIAM Lens computes a policy-specific heuristic; confidence and support scores are not universal truth probabilities. | -| Artifact | FIAM describing/implementing artifact role | It may serve as ITC Evidence Source when addressable and versioned; the artifact is not the assertion drawn from it. | +| Artifact | FIAM describing/implementing artifact role | It may serve as ITC Evidence Source when addressable and versioned/captured where mutable; the Evidence assertion must state its explicit interest. Implementing a contract does not automatically make an artifact a KnowledgeArtifact. | | Zone / security profile | Reference FIAM contextual classifications | No transfer of generic network, security, trust, tenant, or authorization ownership. | | Policy / decision | ITC-GOV Policy / Decision | A Lens finding is an interpretation, not automatically a governed decision or authorization. | @@ -33,3 +33,17 @@ mappings, not automatic equivalence or ownership transfers. The initial review is complete. External federation acceptance and evidence of consumer adoption remain in INTERFACE-WP-0004; publication stays draft. + +## Owner-review clarifications + +Network Port covers physical/device ports as well as protocol-level transport +ports; the TCP example is illustrative, not exhaustive. Resource/shape mappings +establish neither universal subtyping nor exact equivalence. Describing artifacts +may qualify as KnowledgeArtifact; implementation artifacts do not qualify merely +because they implement a contract. Evidence Source is the addressable container, +with version/capture where mutable; Evidence states the assertion and explicit +interest. These clarifications preserve the imported source meanings. + +Acceptance scope and source revisions are recorded in the +[acceptance report](../reviews/acceptance/README.md). Earlier owner reviews target +0.1.1; the local clarification revision is draft 0.1.2. diff --git a/infospace/models/interface/InterfaceCanonInterfaceModel.md b/infospace/models/interface/InterfaceCanonInterfaceModel.md index c519a13..93da500 100644 --- a/infospace/models/interface/InterfaceCanonInterfaceModel.md +++ b/infospace/models/interface/InterfaceCanonInterfaceModel.md @@ -4,7 +4,7 @@ title: InterfaceCanon Interface Model namespace: interface-model type: domain-model status: draft -version: 0.1.1 +version: 0.1.2 imports: [itc-land, itc-ident, itc-evid, itc-gov, itc-data, itc-infospace, itc-net] import_manifest: imports.json source_manifest: ../../assimilation/fiam/sources.json @@ -27,7 +27,8 @@ in the [pinned FIAM package](../../assimilation/fiam/README.md). An owned architectural participation point through which a participant or system node offers or requires a particular interface contract. An offer/require mode is contract participation, not message direction. This Port -is distinct from ITC-NET Port: TCP port 8000 is a transport selector. +is distinct from ITC-NET Port. Network profiles distinguish physical/device +ports from protocol-level transport ports; TCP port 8000 is one transport example. Source: `#/$defs/port`. Local identifier: `interface-model:port`. diff --git a/infospace/reviews/acceptance/README.md b/infospace/reviews/acceptance/README.md new file mode 100644 index 0000000..1cb0af3 --- /dev/null +++ b/infospace/reviews/acceptance/README.md @@ -0,0 +1,37 @@ +# Owner acceptance evidence + +Workplan: INTERFACE-WP-0004. Checked 2026-09-09 against repository Git records +as well as Statehub threads. Acceptance can be evidenced by an owner-repository +record before a message reply arrives; uncommitted files are not a pinned receipt. + +| Owner | Evidence | Status and scope | +| --- | --- | --- | +| 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. | + +## Implemented clarifications + +Draft 0.1.2 makes explicit that Network Port includes physical/device and +transport ports; the existing TCP example did not enumerate the full scope. +Mappings also clarify version/capture for mutable evidence containers, the explicit +interest required for Evidence, and that implementing a contract does not +necessarily make an artifact a KnowledgeArtifact. Resource/shape mappings remain +context-dependent, with no universal subtyping or equivalence claim. + +These clarifications agree with the already pinned ITC-NET, ITC-EVID, and +ITC-INFOSPACE definitions. They were prompted by the visible InfoTechCanon review, +but are supported independently by those committed imports. We do not represent +the uncommitted peer file as a finalized revision. + +The FIAM review targets InterfaceCanon commit +`1fc82ec6655ed286cea3be284e33d08e7b27edc3` / model 0.1.1. It is not a claim +that FIAM separately reread the local 0.1.2 clarification revision. The original +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 +this extension's acceptance scope. diff --git a/infospace/reviews/acceptance/facetted-interfaces-sources.json b/infospace/reviews/acceptance/facetted-interfaces-sources.json new file mode 100644 index 0000000..24ca773 --- /dev/null +++ b/infospace/reviews/acceptance/facetted-interfaces-sources.json @@ -0,0 +1,14 @@ +{ + "schema_version": 1, + "source_repository": "facetted-interfaces", + "source_commit": "cceb005c9cacbc1705c7a3f8e7367255de8a5731", + "sources": [ + { + "path": "docs/interface-canon-boundary.md", + "sha256": "00763784d23e049fdc7732a029cae62ebf1c3e739f2113fe06629efb3a4d4a52" + } + ], + "reviewed_interface_commit": "1fc82ec6655ed286cea3be284e33d08e7b27edc3", + "reviewed_model_version": "0.1.1", + "acceptance_scope": "draft derivation fidelity and authority boundary; no stable promotion or runtime conformance" +} diff --git a/reviews/INTERFACE-WP-0004/README.md b/reviews/INTERFACE-WP-0004/README.md index 9e23ad5..a5155fc 100644 --- a/reviews/INTERFACE-WP-0004/README.md +++ b/reviews/INTERFACE-WP-0004/README.md @@ -21,7 +21,8 @@ closing the corresponding task. ## Publication decision -Keep draft 0.1.1 while responses are absent. Reassess promotion only against actual +The local clarification revision is draft 0.1.2. Owner review targets remain +0.1.1; see the [acceptance report](../../infospace/reviews/acceptance/README.md). Reassess promotion only against actual upstream and consumer evidence, including the draft status of the source FIAM standard. Acceptance need not imply immediate stable promotion. @@ -32,7 +33,9 @@ reopening is proposed. Review belongs with the living canon/source/consumer owne ## Next action -Await owner replies on the three recorded message threads. Keep this workplan +FIAM acceptance is now pinned from its committed owner record. Await committed +InfoTechCanon review and Repo Manager adoption evidence; 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 80fdff2..d1e73f4 100644 --- a/workplans/INTERFACE-WP-0004-federation-acceptance.md +++ b/workplans/INTERFACE-WP-0004-federation-acceptance.md @@ -76,3 +76,20 @@ The offline brief was stale and has been regenerated from the current hub projection. T01 needs the InfoTechCanon and FIAM boundary responses; T02 needs Repo Manager adoption evidence before publication can be reassessed. Keep both open and preserve draft status until those records arrive. + +## Implementation from owner review — 2026-09-09 + +[Acceptance report](../infospace/reviews/acceptance/README.md) pins the committed +FIAM owner record and documents the remaining evidence limits. FIAM accepted the +0.1.1 derivation without blocking corrections. InfoTechCanon's visible but +uncommitted review prompted clarifications now implemented in draft 0.1.2: +physical/device versus transport Port, explicit evidence interest and source +capture, and the limits of Artifact/KnowledgeArtifact alignment. + +T01 remains `wait` for InfoTechCanon's committed record; FIAM's part is satisfied. +T02 remains `wait` for consumer-owned adoption evidence. Neither task is closed +solely because request messages have been read. The source model and card stay +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.