coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Split the Emission Cadence promotion gate and promote to candidate (T06)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
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
This commit is contained in:
tegwick 2026-09-21 00:10:33 +02:00
parent 9de170ecf9
commit 4d0851c3fc
4 changed files with 155 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

12
SCOPE.md
View file

@ -11,9 +11,9 @@ with executable proofs and mixed artifact maturity**.
The working-tree canon version is `0.7.0`; the Python package version is
`0.1.0`. These are separate version surfaces. Many models remain `RC1-seed`;
ITC-CAP is a frozen draft at `0.4.0`, and Emission Cadence is a draft document
at `0.1.0` with wire schema version `0.1`. This is not yet a stable,
ecosystem-wide conformance release.
ITC-CAP is a frozen draft at `0.4.0`, and Emission Cadence is a candidate
document at `0.2.0` with wire schema version `0.1` unchanged. This is not yet a
stable, ecosystem-wide conformance release.
## Ownership and boundaries
@ -92,8 +92,10 @@ Current limitations include:
- limited external mapping and independent consumer interoperability evidence;
- interface templates and evaluation packs without a complete set of
source-owned, version-pinned consumer declarations;
- draft promotion and compatibility questions, including the requirement for
two independent Emission Cadence source implementations;
- no independent adoption evidence for Emission Cadence: the standard is at
candidate, which asserts a specified and machine-checkable contract, and stable
still requires two source-owned declarations from independent owners plus an
observer result from a third party (INFO-DEC-2026-002);
- upstream full-application packaging limitations and consumer-owned adoption evidence.
INFO-WP-0019 adds reusable arbitrary Emission Cadence declaration validation,