# InterfaceCanon extension boundary

Status: accepted for the semantic boundary documented below, reviewed by Codex
in the InfoTechCanon repository on 2026-09-09. This is an agent review, not a
claim of separate human sign-off or a published peer merge.

Review target: interface-canon draft 0.1.1 at
`1fc82ec6655ed286cea3be284e33d08e7b27edc3`. Proposed patch: interface-canon
`reviews/INTERFACE-WP-0004/info-tech-canon.patch` in review package
`6b33ac2388190207c4373e6f288922ce5c0b0413`.
InfoTechCanon review base and import source:
`8eb1c83f2e119de57e7ad448b901381f8e92fb57`.

InterfaceCanon derives interface-domain terminology from FIAM in
facetted-interfaces and references shared InfoTechCanon concepts. It supplies a
focused interface model while InfoTechCanon retains the shared roots.

## Accepted dispositions

- FIAM Port is contract participation, distinct from ITC-NET network Port.
  Network profiles also distinguish physical/device ports from transport ports;
  the distinction is broader than the TCP example alone.
- InterfaceContract describes semantic interface behavior. Landscape's Interface
  seed and Network's attachment-point Interface are contextual mappings, not
  universal exact aliases.
- FIAM Endpoint locates or selects 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 retain their shared owners;
  these mappings establish neither universal subtyping nor exact equivalence.
- FIAM Representation concerns participation encoding; Data Representation also
  describes value-level forms. Consumers must qualify these scopes.
- Describing artifacts may be KnowledgeArtifact and Evidence Source. An Evidence
  Source is an addressable container with a relevant version or capture where
  mutable; Evidence is a separate assertion drawn for an explicit interest.
  An artifact implementing a contract is not automatically a KnowledgeArtifact.

## Evidence and limits

Reviewed `infospace/models/interface/InterfaceCanonInterfaceModel.md`,
`infospace/mappings/review-2026-09-09.md`, and
`infospace/models/interface/imports.json` at the InterfaceCanon revision above.
All seven manifest SHA-256 values match Git blobs at the declared InfoTechCanon
source revision, and those files are unchanged in the review checkout:
ITC-LAND, ITC-IDENT, ITC-EVID, ITC-GOV, ITC-DATA, ITC-INFOSPACE, and ITC-NET.

The proposed boundary is accepted with the clarifications above. This reciprocal
reference does not extend the completed identity/commerce ownership ledger,
transfer shared ownership, or establish a reverse semantic dependency.
InterfaceCanon remains draft; this review supplies no consumer implementation or
deployment evidence and does not satisfy INFO-WP-0019-T06's emission-cadence gate.

The file's eventual containing commit identifies the applied review revision;
the review base above must not be represented as a merge commit. Work and
verification are tracked in
[INFO-WP-0026](../../workplans/INFO-WP-0026-interface-canon-boundary-review.md).