interface-canon/reviews/INTERFACE-WP-0004/info-tech-canon.patch
tegwick 6b33ac2388 Prepare owner review patches for InterfaceCanon federation and adoption
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87
2026-09-09 22:19:14 +02:00

48 lines
2.5 KiB
Diff

--- a/README.md
+++ b/README.md
@@ -146,3 +146,7 @@
[Published interface card](infospace/interfaces/federation.yaml) declares exports, imports, authority,
source-of-truth boundaries and reciprocal canon references.
+
+## InterfaceCanon boundary review
+
+See [InterfaceCanon boundary review](infospace/interfaces/interface-canon-boundary.md) for the draft proposal and review scope.
--- /dev/null
+++ b/infospace/interfaces/interface-canon-boundary.md
@@ -0,0 +1,35 @@
+# InterfaceCanon extension boundary
+
+Status: draft review proposal. Review target: interface-canon draft 0.1.1 at
+`1fc82ec6655ed286cea3be284e33d08e7b27edc3`. This document proposes a reciprocal boundary reference;
+acceptance requires the InfoTechCanon owner's recorded review.
+
+InterfaceCanon derives interface-domain terminology from the FIAM standard in
+facetted-interfaces and references shared InfoTechCanon concepts. It supplies a
+focused interface model rather than replacing InfoTechCanon shared roots.
+
+Reviewed imports: ITC-LAND, ITC-IDENT, ITC-EVID, ITC-GOV, ITC-DATA, ITC-INFOSPACE,
+and ITC-NET. Source commits and hashes are in the InterfaceCanon import manifest.
+
+Boundary dispositions for acceptance:
+
+- FIAM Port is contract participation, distinct from ITC-NET network Port.
+- InterfaceContract describes semantic interface behavior; it is not an exact
+ alias for all Landscape/Network Interface meanings.
+- FIAM Endpoint locates a Binding. Network Endpoint is related where realization
+ is network-based; local bindings need not have a network endpoint.
+- InformationResource/InformationShape map contextually to Data concepts;
+ Dataset, DataObject, Record, DataType, and Constraint keep their shared owners.
+- FIAM Representation concerns participation encoding; Data Representation also
+ describes value-level forms. The two scopes must remain qualified.
+- Describing artifacts may be KnowledgeArtifact and Evidence Source. An assertion
+ drawn from the source remains distinct from the source container.
+
+Review material: interface-canon `infospace/mappings/review-2026-09-09.md` and
+`infospace/models/interface/imports.json` at the revision above.
+
+This proposal does not extend the completed identity/commerce migration ledger,
+transfer shared ownership, or assert a reverse semantic dependency. Record accepted
+or corrected dispositions, reviewer identity, and review/merge revision before
+InterfaceCanon uses this document as acceptance evidence. Draft availability is
+not evidence that consumers have adopted the model.