Trust Model · pre-alpha
Status
Capability is not authority — and where to read it.
A feature being present does not mean your run gates on it. Every honest-measurement rule on the other Trust Model pages still applies: a fresh install is informational, thresholds start proposed, and judges start uncalibrated. “Shipped” means the machinery exists, not that your evaluation is enforcing anything yet — that always takes a deliberate, host-owned approval.
Where status lives
The site and docs may run ahead of the framework code: a capability can be documented before it ships. So a single register is the source of truth, and it is public:
| State | Means |
|---|---|
| now | Shipped at HEAD and shown executing only where real. |
| next | Committed, building — not yet shipped (e.g. the drift watcher, a hosted sink, the Codex listing). |
| planned | Intended, not near-term (e.g. a metrics explorer, more worked examples). |
| experimental | Exists but unstable (e.g. the local dashboard sink, a live-judge lane, live trace connectors reached with connect --live). |
| non-goal | A decision, not a deferral — deliberately not built (e.g. a connect --synth generator, per-source-function attribution). |
Read the per-capability detail on the Roadmap. Anything documented here that the framework has not yet built is badged there — never shown executing as if it were now.