coulomb/interface-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Apply InfoTechCanon acceptance consistently across mappings and examples

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87
This commit is contained in:
tegwick 2026-09-09 23:06:06 +02:00
parent ae20bc631c
commit 6ae63977e7
7 changed files with 163 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
infospace/models/interface/InterfaceCanonInterfaceModel.md
View file

@ -163,6 +163,11 @@ FIAM remains authoritative for exact validation requirements.
| Kafka topic with retained events | Channel for exchange, Information Resource for retained log, related by `backed-by`. |
| JSON document governed by a schema | Resource instance, Information Shape, describing Artifact, and Representation remain distinct. |
| Port offers a request-response contract | Offers is participation mode; requests and responses still travel in different directions. |
| A physical NIC port, TCP port 8000, and a service's offered Port | Device/transport network meanings and FIAM contract participation remain distinct; equal names do not identify one concept. |
| MCP stdio binding has no network address | A local realization need not have a Network Endpoint; FIAM does not require a network locator for every Binding. |
| JSON encodes a boolean field | JSON is FIAM participation Representation; the value's boolean form is a distinct Data Representation concern. |
| A schema document and a binary both implement or describe an interface | Reusable schema knowledge may qualify as KnowledgeArtifact; implementation alone does not establish that classification for the binary. |
| A mutable schema page supports a claim about an accepted field | Capture the page version and locator as Evidence Source; separately state the field assertion and the explicit interest it supports. |
| Two schemas have identical fields | Correspondence candidate; no automatic identity assertion. |
| Telemetry contains no authentication attributes | Unknown runtime authentication evidence; no inferred absence of protection. |
@ -171,3 +176,6 @@ fixtures or evidence of consumer adoption. The [mapping review](../../mappings/r
[Repo Manager case](../../examples/repo-manager-statehub.md) complete the initial
review. Scoped external acceptance and adoption are recorded in completed
INTERFACE-WP-0004; see the [acceptance report](../../reviews/acceptance/README.md).
These cross-canon cases apply the [accepted mappings](../../mappings/upstream.md)
without equating distinct FIAM and InfoTechCanon concepts.