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

infospace/standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md

@@ -6,8 +6,8 @@ type: standard
 standard_family: InfoTechCanon
 repository_context: info-tech-canon
 recommended_path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
-status: draft
-version: 0.1.0
+status: candidate
+version: 0.2.0
 schema_version: "0.1"
 canonical_owner: InfoTechCanonEmissionCadenceStandard
 namespace: itc-emission-cadence
@@ -30,15 +30,19 @@ provenance:
   source_file: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
   assimilation: assimilation/emission-cadence
   decision: GH-DEC-2026-004
+promotion:
+  level: candidate
+  decision: INFO-DEC-2026-002
+  promoted_at: "2026-09-21"
 created_at: "2026-09-04"
-updated_at: "2026-09-04"
+updated_at: "2026-09-21"
 ---
 
 # InfoTechCanon Emission Cadence Standard
 
 **Short Name:** `ITC-EMISSION-CADENCE`  
-**Document Status:** Draft  
-**Version:** 0.1.0  
+**Document Status:** Candidate  
+**Version:** 0.2.0  
 **Schema Version:** `0.1`
 
 ## 1. Purpose
@@ -212,3 +216,37 @@ unsupported versions and forms, and keeps observation results separate from
 the source's declaration.
 
 Profile conformance is additional and is assessed by the profile owner.
+
+## 10. Promotion levels
+
+Promotion is assessed at two levels, because one gate was doing two different
+jobs and neither could be claimed (INFO-DEC-2026-002).
+
+**Candidate** asserts that the contract is specified, machine-checkable and
+stable enough to implement against. It requires, and this standard has:
+
+- a schema that covers every declared form, with an arbitrary source-owned
+  declaration validatable by one command against the named schema;
+- a content-addressed contract bundle a source owner can pin to;
+- validation that keeps a source's declaration separate from observation, and
+  reports that operational truth is not assessed;
+- a documented consumption path for a consumer outside this repository.
+
+Candidate asserts nothing about adoption. No consumer has implemented this
+contract, and this standard's own worked example is explicitly not a
+source-owned declaration.
+
+**Stable** asserts that the contract survives contact with independent
+implementers. It requires, and this standard does **not** have:
+
+- two source-owned declarations from owners independent of each other and of
+  this repository, pinned to a contract digest;
+- at least one observer result produced by a party other than the declaring
+  source, exercising the comparison references;
+- a recorded incompatibility or a recorded absence of one, from the attempt.
+
+A `0.x` version number continues to mean that incompatible changes remain
+possible with migration guidance. Candidate status does not freeze the wire
+contract, which stays at schema version `0.1`; it records that the canon side
+of the work is finished and that what remains is adoption, which the canon
+cannot perform on its own behalf.