tegwick
6b33ac2388
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87
37 lines
1.8 KiB
Diff
37 lines
1.8 KiB
Diff
--- a/README.md
|
|
+++ b/README.md
|
|
@@ -13,3 +13,7 @@
|
|
|
|
Normative releases should be promoted into a versioned top-level release
|
|
layout; `history/` remains reserved for superseded drafts.
|
|
+
|
|
+## InterfaceCanon boundary review
|
|
+
|
|
+See [InterfaceCanon boundary review](docs/interface-canon-boundary.md) for the draft proposal and review scope.
|
|
--- /dev/null
|
|
+++ b/docs/interface-canon-boundary.md
|
|
@@ -0,0 +1,24 @@
|
|
+# InterfaceCanon derivation boundary
|
|
+
|
|
+Status: draft review proposal. Review target: interface-canon draft 0.1.1 at
|
|
+`1fc82ec6655ed286cea3be284e33d08e7b27edc3`. Acceptance requires the FIAM owner's recorded review.
|
|
+
|
|
+InterfaceCanon translates FIAM interface terminology into a focused extension to
|
|
+InfoTechCanon. FIAM retains authority over standard semantics, Core schemas,
|
|
+controlled terms, profiles, policies, reference implementation, and conformance.
|
|
+
|
|
+The consumer pins FIAM v0.2 Draft 6 at commit
|
|
+`135326756913363b098bcdee791628b5e864b8be`, including retained Draft 1 explanation,
|
|
+frozen Core schema, and Canon. InterfaceCanon owns its derived presentation and
|
|
+cross-canon mappings; it does not issue a new FIAM conformance specification.
|
|
+
|
|
+Review the definitions and distinctions in interface-canon
|
|
+`infospace/models/interface/InterfaceCanonInterfaceModel.md`, especially
|
|
+contract versus binding; endpoint versus resource selector; channel versus retained
|
|
+resource; shape versus describing artifact versus representation; and
|
|
+assertion/source versus derived lens conclusions.
|
|
+
|
|
+Accept or correct the derivation and record reviewer identity and revision.
|
|
+Acceptance concerns fidelity and authority boundaries, not FIAM release promotion,
|
|
+consumer runtime conformance, or stable InterfaceCanon publication. The FIAM draft
|
|
+and its historical package layout remain unchanged by this proposal.
|