Record FIAM acceptance and clarify shared interface mappings

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87

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.