Release-Candidate Checklist
This is the authoritative acceptance checklist that was used for declaring Karkain a Release Candidate (Phase 118). Every item below was satisfied; the list is retained as historical evidence of the RC readiness process.
Note
Completed — Phase 118 gate pkg/cli/phase118_rc_test.go passed
and the RC READY verdict was issued. The 1.0.0 stable release followed
from Phase 119 QA. See Release Notes and
Release-Candidate Scope for the current status.
Current state (Phase 118)
# |
Criterion |
Evidence |
State |
|---|---|---|---|
1 |
External developer journey works end to end |
|
[ ] |
2 |
Installation / build workflow is documented |
Installation, |
[ ] |
3 |
Version reporting works and identifies the Beta line |
|
[ ] |
4 |
Release artifact strategy is documented |
[ ] |
|
5 |
First-program tutorial works on a clean checkout |
[ ] |
|
6 |
Multi-file project example builds |
Your First Karkain Project, Phase 118 gate |
[ ] |
7 |
Workspace example works (app consumes sibling library) |
|
[ ] |
8 |
CLI documentation is accurate |
Command-Line Interface, |
[ ] |
9 |
Issue-reporting workflow exists |
|
[ ] |
10 |
Security reporting path exists |
|
[ ] |
11 |
Compatibility policy exists |
[ ] |
|
12 |
Migration notes exist |
[ ] |
|
13 |
Beta 1 release notes exist |
[ ] |
|
14 |
Documentation navigation is complete |
[ ] |
|
15 |
Stable API snapshot exists |
[ ] |
|
16 |
Feature-freeze policy exists |
[ ] |
|
17 |
Automated Phase 118 gate exists and passes |
|
[ ] |
18 |
Clean / fresh workflow passes |
|
[ ] |
19 |
Phase 117 regression baseline remains green |
Conformance 59/59, probes 11/11, example parity 49/49, verify-examples 49 pass / 0 fail |
[ ] |
20 |
No generated artifacts are committed |
|
[ ] |
21 |
Public status is synchronized everywhere |
README, docs index, status pages, release notes |
[ ] |
Interpretation
Every item marked [ ] must transition to [X] before
RC READYcan be declared.A missing roadmap feature is not a checklist failure unless it was promised in the Beta stable scope.
The checklist state is updated in the Phase 118 audit report (
docs/audit/PHASE-118-RELEASE-CANDIDATE-READINESS-FINAL-REPORT.md) and mirrored in the Release-Candidate Scope blockers section.
See also
Release-Candidate Scope — the status matrix that feeds this checklist. Compatibility Policy — what each bucket guarantees. Feature-Freeze Policy (Beta / Release-Candidate) — the freeze rules in force.