10.9 Minimal implementation contract

A system should not be described as CoLT unless it records at least:

1. a versioned declaration and maintained realization;

2. a typed distinction between probes, observations, and obstruction witnesses;

3. the quotient and cover relative to which localization is claimed;

4. a registered repair language with explicit targets;

5. preserved obligations and provenance for every proposal;

6. accept, reject, and abstain as distinct outcomes; and

7. an independently checkable admission certificate for every state change.

The contract permits implementations in theorem provers, databases, agent workflows, argument graphs, causal models, differentiable programs, and hybrid systems. Their common object is not a token format but a governed structural trace.