info-tech-canon/infospace
tegwick 4d0851c3fc
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Split the Emission Cadence promotion gate and promote to candidate (T06)
The gate required two independent source implementations before draft
promotion, which made one sentence do two jobs: whether the contract is
specified well enough to implement against, which this repository can answer,
and whether it survives implementers who did not write it, which it cannot. The
second blocked the first, so the standard sat at draft — a word that reads as
unfinished specification — when what was missing was adoption.

Candidate now requires schema coverage of every form, one-command validation of
an arbitrary source-owned declaration, a content-addressed bundle a source can
pin to, separation of declaration from observation, and a documented external
consumption path. All are met and were re-tested rather than assumed. Stable
requires two source-owned declarations from independent owners pinned to a
digest, an observer result from a third party, and a recorded incompatibility or
a recorded absence of one — stricter than the sentence it replaces.

Emission Cadence moves to candidate at document version 0.2.0. The wire contract
is untouched at schema version 0.1, and no field, form or validation rule
changes, so a producer conformant yesterday is conformant today.

What was given up: candidate carries no interoperability evidence at all. The
standard states that in its own section 10, naming that no consumer has
implemented the contract and that its worked example is not a source-owned
declaration. The gate now lives in the standard rather than only in SCOPE.md, so
a reader meets it where the contract is.

Recorded as INFO-DEC-2026-002 with the reasoning in history/. INFO-WP-0019
closes: all six tasks done.

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-21 00:10:33 +02:00
..
agent Check import manifests by hash and name together (INFO-WP-0028 T01-T03) 2026-09-20 23:43:34 +02:00
artifacts Publish reciprocal canon federation interface 2026-09-06 01:00:12 +02:00
assimilation Distribute frozen federation corpus by concept destination 2026-09-06 00:44:37 +02:00
concepts Register limited Family concept-area seed 2026-09-06 00:26:29 +02:00
evaluations ITC-WP-0012: integrate Repository Layout Standard 2026-06-13 14:25:54 +02:00
examples Add purpose and demand model extension 2026-05-23 04:59:16 +02:00
indexes Check import manifests by hash and name together (INFO-WP-0028 T01-T03) 2026-09-20 23:43:34 +02:00
interfaces Generalise the CARING section 32 role set (R-2, INFO-DEC-2026-001) 2026-09-20 23:55:11 +02:00
kernel Declare concepts and review boundaries for the silent artifacts (T02) 2026-09-20 23:19:22 +02:00
mappings Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review 2026-08-15 19:42:30 +02:00
models Close the last open import pins and the workplan (T04) 2026-09-20 23:50:52 +02:00
patterns feat(ITC-WP-0017): establish AgenticDrivesFunctional pattern 2026-08-22 18:54:01 +02:00
profiles Implement canon conformance and maintenance optimizations 2026-09-05 00:50:09 +02:00
reports Add small SaaS profile proof 2026-05-23 04:26:28 +02:00
schemas Implement canon conformance and maintenance optimizations 2026-09-05 00:50:09 +02:00
standards Split the Emission Cadence promotion gate and promote to candidate (T06) 2026-09-21 00:10:33 +02:00
validation Introduce identity model and reconcile upstream imports 2026-09-05 22:11:46 +02:00
views Check import manifests by hash and name together (INFO-WP-0028 T01-T03) 2026-09-20 23:43:34 +02:00
infospace.yaml Introduce identity model and reconcile upstream imports 2026-09-05 22:11:46 +02:00
README.md Implement infospace scaffold and service baseline 2026-05-23 03:12:02 +02:00

InfoTechCanon Infospace

This directory is the single concrete infospace implemented by this repository. The repository root remains the service, governance, and workplan shell.

The current placement pass copies the seed documents into canonical kernel/, models/, and standards/ paths while keeping seeds/ as provenance until the scaffold migration is reviewed.