Establish InterfaceCanon with Statehub integration and FIAM-derived model

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

infospace/kernel/InterfaceCanonCore.md

@@ -0,0 +1,29 @@
+---
+id: interface-core
+title: InterfaceCanon Core
+type: kernel
+status: draft
+version: 0.1.0
+---
+
+# InterfaceCanon Core
+
+Maintain one focused domain model extending InfoTechCanon. `canon.yaml` is the
+entry-point registry. Models live under `infospace/models/`; standards, if later
+needed, belong under `infospace/standards/`. Workplans stay in the repository shell.
+CommerceCanon is the structural precedent, not an imported commercial dependency.
+
+Every new term must have a definition, distinguishing counterexample, source
+locator or explicit local rationale, and an ownership disposition. Preserve FIAM
+identifiers in mappings; do not relabel protocol families as primitive entity types.
+Import shared roots from their owner. A name collision requires an explicit
+mapping and review, not a silent replacement or an assertion of equivalence.
+
+Changes to source pins require review of changed semantics and a work record.
+Keep previous manifests in Git history. A draft may expose unresolved mappings;
+stable promotion requires their resolution and named consumer evidence. Do not
+represent availability as adoption or a local card as reciprocal federation acceptance.
+
+FIAM Core facts, exchange profiles, derived indexes, and policy/lens conclusions
+remain separate layers. This canon summarizes terminology; FIAM owns wire formats,
+validation, conformance, and implementation behavior.