interface-canon/infospace/mappings/review-2026-09-09.md

Shared-concept review — 2026-09-09

Workplan: INTERFACE-WP-0003. Review scope: the initial model's structural terms and its explicit shared-root collisions. The import manifest pins the reviewed InfoTechCanon models; existing four source hashes are unchanged. This review expands the mapping set with Data, Information Space, and Network. It records local semantic dispositions, not an upstream ownership transfer.

Local/FIAM usage	Reviewed source section	Disposition and counterexample
Interface Contract	ITC-LAND §13.2 Interface seed	Related specialization of interface architecture. A network attachment called Interface does not imply a semantic operation contract.
Port	ITC-NET §§11.26–11.27 Interface/Port	Distinct concepts. FIAM Port participates in a contract; TCP port 8000 is a transport selector. Never equate them by spelling.
Endpoint	ITC-LAND §13.2; ITC-NET §11.45	FIAM-qualified locator of a Binding. A network ServiceEndpoint can realize that locator, but not all FIAM bindings are network-based.
Information Resource	ITC-DATA §§8.1–8.2, 11.4, 11.8–11.9	Related to Dataset/DataObject/Record by modeled scope. A dataset is a coherent managed unit; FIAM also covers a resource selection or state locus. No universal subtype or exact-equivalence claim.
Information Shape	ITC-DATA §§8.3, 11.15–11.16	Related to DataType/Constraint. Shape carries admissible semantic/structural form; a schema artifact describes details. A type name alone does not establish shape identity.
Representation	ITC-DATA §11.14	FIAM specializes encoding/notation selected for shape participation. Data Representation also covers value-level forms such as integer or date. JSON does not establish a field's semantic type.
Artifact	ITC-INFOSPACE §11.8 KnowledgeArtifact	A schema or interface document carrying reusable knowledge qualifies as KnowledgeArtifact. A FIAM Artifact can also implement a contract, so no blanket equivalence.
Source provenance	ITC-INFOSPACE §§11.30–11.31; ITC-EVID §2	Import Citation/SourceReference and Evidence Source. A Git blob is a source container; the claim extracted from it is separate Evidence.
Assertion / evidenceRecord	ITC-GOV Assertion; ITC-EVID §§1–2	FIAM property/relation assertion specializes architectural assertions. Its evidenceRecord supplies support metadata; model the ITC assertion, question, and source separately rather than renaming the record.
Identity correspondence	ITC-IDENT Synonymity Assertion; FIAM Draft 1 decision 7	Similarity is a correspondence candidate; governed identity and non-destructive equivalence remain separate.
Participant / SystemNode	ITC-LAND §13.2 SoftwareSystem/SoftwareComponent	Context-dependent alignment. A logical system, deployed process, and Actor must not collapse solely because a name is shared.
Zone, security profile, Policy, Lens	FIAM Draft 6 §§1, 6–7; ITC-GOV Policy/Decision	Contextual qualifiers and policy-derived interpretations. No new local owner for generic networking, security, policy, or decisions.

The reviewed Data document includes Schema/SchemaVersion in its taxonomy, but this review does not invent a fully authored Schema definition or import it as an exact InformationShape alias. The narrower authored DataType/Constraint meanings are sufficient to explain the boundary.

Remaining structural terms—Contract Participation, Operation, Binding, Channel, Interaction, Interaction Flow, Resource Selector, and Facet—retain their pinned FIAM-derived definitions. This review finds no reason to add a protocol-specific Core entity. Resource/shape details remain in describing artifacts.

Result: local mapping review complete; all collisions above have explicit qualified meanings. The Repo Manager consumer case exercises these distinctions. Publication remains draft for the reasons in the federation review.