What "implemented" means
320 wordsPlan version 1.1
A capability is implemented only when all eight hold. Otherwise it MUST be described as partial, and the missing items named.
- Code exists in the crate this plan maps it to (§34).
- The crate ships a
CONTRACT.mdwith ten sections: purpose, inputs, outputs, invariants, refusals, determinism class, evidence class of outputs, validity domain, oracles, known gaps. - Known-answer tests pass against a pinned oracle that was never regenerated from the candidate (§38).
- Outputs that cross the agent boundary carry the claim product of §8: the kind of claim, the evidence class set by the weakest input, a tier, a determinism class, a model identity, a seed, and the no-authorization flags. No naked numbers reach an agent (§29).
- A CPU reference path exists. Where a GPU path is claimed, a retained differential check against the CPU path exists for the same kernels (§21).
- The capability is reachable through
frob --jsonwith a documented schema and exit code, and, where the verb registry exposes it to agents, throughfrob-mcp(§32). - Cancellation is tested: request, drain, finalize, with no leaked device resources (§38).
- Its gate has a recorded PASS carrying the measured values, not the targets, in a receipt that names the commit, the hardware fingerprint and the seed (§40).
Two riders apply to particular kinds of capability.
- Family certificates. A capability that emits a certificate about a family of designs or worlds (§25) is
implemented only when the certificate travels in a
.frobcertbundle and the independent offline auditorfrob-verifyaccepts it on a machine with neither the agent nor a GPU, and rejects the registered mutations of it (§12). - Upper tiers. An F or M capability is implemented only when its pilot and its kill-gate decision are on record (§0.7). A capability that fell back at its kill gate is described by the name of the fallback.