id: interface-canon/federation-interface
title: InterfaceCanon Federation Interface Card
consumer: interface-canon
canon_surfaces: [interface-model]
status: draft
version: 0.1.2
owner: interface-canon
schema_source:
  repository: info-tech-canon
  path: infospace/schemas/interface-card.schema.yaml
peers:
  - repository: info-tech-canon
    relationship: shared-concept upstream; interface-domain extension
    review_record: infospace/interfaces/interface-canon-boundary.md
    acceptance_manifest: infospace/reviews/acceptance/info-tech-canon-sources.json
  - 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: repo-manager
    relationship: consumer of interface terminology for Statehub synchronization documentation
    review_record: docs/interface-canon-statehub-consumer.md
    acceptance_manifest: infospace/reviews/acceptance/repo-manager-sources.json
  - repository: commerce-canon
    relationship: structural precedent for a focused domain canon
exports:
  - artifact: interface-model
    kind: domain-model
    path: infospace/models/interface/InterfaceCanonInterfaceModel.md
    status: draft
    availability: draft reference; Repo Manager documentation adoption is recorded for reviewed version 0.1.1
imports:
  - repository: info-tech-canon
    artifacts: [itc-land, itc-ident, itc-evid, itc-gov, itc-data, itc-infospace, itc-net]
    manifest: infospace/models/interface/imports.json
  - repository: facetted-interfaces
    artifact: FIAM v0.2 Draft 6
    manifest: infospace/assimilation/fiam/sources.json
mapping_rules:
  - Shared concepts retain their InfoTechCanon owner.
  - FIAM retains ownership of standard semantics, schemas, and conformance.
  - Local definitions remain FIAM-qualified where upstream names overlap.
known_deviations:
  - FIAM accepted draft 0.1.1 derivation and authority boundaries; Repo Manager adopted that documentation mapping; InfoTechCanon accepted shared boundaries with clarifications implemented in 0.1.2.
  - 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.
  - Initial mapping and consumer-description review is complete in INTERFACE-WP-0003; consumer adoption and draft publication assessment are complete in INTERFACE-WP-0004-T02; T01 records committed FIAM and InfoTechCanon acceptance. All reviews are scoped to draft 0.1.1; no stable promotion is asserted.