Kernel v0.1 Freeze Candidate
Purpose
The kernel freeze defines a stable contract boundary for v0.1: what is locked, what is excluded, and what the freeze commits to maintaining.
This is a scope-control document, not a feature list. The freeze serves to establish a known-good reference point for evaluation and evidence generation.
Included in v0.1 Freeze
| Component | Status |
|---|---|
| Stable DTO contracts | Frozen |
| Single policy/decision authority path | Frozen |
| Structural invariants separated from policy | Frozen |
| ExecutionCommit as side-effect boundary | Frozen |
| Runnable CEG Intent Registry | Frozen |
| Execution Gate | Frozen |
| Causal Bridge | Frozen |
| Replayable DecisionTrace evidence | Frozen |
| Critical kernel tests green | Verified |
| Public boundary documentation | Published |
Excluded from v0.1 Freeze
The following are explicitly excluded from the kernel v0.1 freeze:
- Full MCP hardening refactor
- OpenProject write integration
- Vercel/web demo as runtime control plane
- Plugin registry (next phase)
- Edition builds
- Model training infrastructure
- New memory system
- New architecture theory components
Excluding these is intentional. The freeze declares what is stable and under contract — not what is desirable or planned.
What the Freeze Means
- Stability: DTO contracts and structural invariants will not change within v0.1
- Evidence: Any evidence generated against the frozen kernel is reproducible
- Boundary: The separation between "in kernel" and "not in kernel" is explicit
- Audit: External reviewers can inspect the frozen boundary without chasing moving targets
What the Freeze Does Not Mean
- Development on excluded components stops — it continues outside the freeze boundary
- The kernel is feature-complete — it is scope-complete for v0.1
- All invariants are formally proven — they are structurally enforced and tested