Release Readiness¶
Goal¶
Ensure QitOS can be published as a reliable framework, not just a working repo.
P0 must pass¶
- Core contracts documented and frozen.
- Examples runnable and aligned with docs.
- Hook payload schema stable and tested.
- Trace schema stable and tested.
- Public API exports audited for leakage.
P1 should pass¶
- Tutorial docs complete for researchers and builders.
- Comparison page reviewed for factual, non-hype language.
qitaboard/replay docs available with screenshots.- Regression taskset script available.
Release checklist template¶
| Item | Owner | Status | Evidence |
|---|---|---|---|
| API freeze | |||
| Hook schema | |||
| Trace schema | |||
| Examples validated | |||
| Docs build success |
Final go/no-go questions¶
- Can a new user run a tutorial end-to-end in under 15 minutes?
- Can a researcher reproduce one pattern and compare two variants in under 1 day?
- Can failures be diagnosed from trace artifacts without rerunning blindly?