coulomb/interface-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Othogonal vocabulary and canonical model for interface related concepts based on the fiam architecture control system.
21 commits 1 branch 0 tags 178 KiB
Find a file
Exact
tegwick 20d7bfc2c3 Pin Interface and Endpoint to the model that defines them 
Both names were pinned twice, to itc-land and to itc-net. InfoTechCanon's
name-resolution check (INFO-WP-0028) reports that ITC-LAND section 13.2 lists
Interface, Endpoint and API as pointers into the software and solution domain
without defining them, while the Network Model defines and owns both. The
itc-land pins are dropped; itc-net already carried them.

This is a citation fix, not a change of position. The accepted boundary already
treats the Landscape Interface seed and the Network attachment-point Interface as
contextual mappings rather than universal exact aliases, and the mapping tables
that cite ITC-LAND section 13.2 as a related seed stay as they are.

SoftwareSystem and SoftwareComponent keep their itc-land pins and now resolve:
InfoTechCanon declared them under INFO-WP-0027-T04 after finding they sat in a
seed-concept list its extraction could not read.

All 23 declared imports now resolve to the artifact they are pinned to.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3588@bnt-lap001
Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da
2026-09-20 23:48:17 +02:00
docs Record bootstrap validation and propose follow-up review 2026-09-09 22:06:42 +02:00
infospace Pin Interface and Endpoint to the model that defines them 2026-09-20 23:48:17 +02:00
reviews/INTERFACE-WP-0004 Pin InfoTechCanon acceptance and complete federation workplan 2026-09-09 22:50:47 +02:00
tools Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
workplans repo.work.assign_missing_identifiers 2026-09-09 23:06:07 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-09 22:52:11 +02:00
.gitignore Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
.repo-classification.yaml Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
AGENTS.md Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
canon.yaml Record FIAM acceptance and clarify shared interface mappings 2026-09-09 22:38:31 +02:00
INTENT.md Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
Makefile Establish InterfaceCanon with Statehub integration and FIAM-derived model 2026-09-09 22:05:18 +02:00
README.md Record FIAM acceptance and clarify shared interface mappings 2026-09-09 22:38:31 +02:00
SCOPE.md Pin InfoTechCanon acceptance and complete federation workplan 2026-09-09 22:50:47 +02:00
WORK-RECORDS.md Apply InfoTechCanon acceptance consistently across mappings and examples 2026-09-09 23:06:06 +02:00

README.md

InterfaceCanon

Interface terminology and canonical models extending InfoTechCanon, derived from the FIAM standard maintained in facetted-interfaces.

Like CommerceCanon for commercial terminology, this repository adds domain semantics while importing shared concepts from InfoTechCanon. The initial model is draft 0.1.2, based on FIAM v0.2 Draft 6 and its frozen v0.2 Core.

Run make check to validate local metadata, links, and pinned-source integrity. Python 3 is the only requirement; no install, build, or runtime service is needed. Source verification uses sibling checkouts by default; make check-sources requires them and verifies the pinned Git blobs, independently of working-tree edits.

Statehub identity: interface-canon, domain infotech, topic canon, workplan prefix INTERFACE-WP-. Repository work records are authoritative; Statehub indexes the committed Forge revision.