Phase 2 Exit Evidence

This page tracks the evidence needed before we say Phase 2 is complete.

Phase 2 is not finished just because the code runs on one machine. It is finished when the UAPI contract, host adapters, language paths, samples, performance checks, docs, and CI evidence all line up.

How To Read This Page

Status meanings:

• Done means the gate is complete for the current Phase 2 scope.
• Strong draft means the design and local checks are solid, but the final freeze or external proof is still pending.
• Partial means useful work exists, but at least one planned proof is still missing.
• Pending means the gate still needs its first real proof.
• Blocked means we know what is needed, but another decision or toolchain step must happen first.

Exit Gate Ledger

What Is Already Strong

The current direction is still right.

Krate has the correct shape for a universal software layer: app code calls a portable UAPI, the runtime checks policy, and host adapters translate approved calls to the native operating system. That is the right path for the larger 6 by 6 goal because it avoids hardcoding one host model into every app.

The strongest Phase 2 pieces today are:

• the UAPI contract shape for io, fs, net, time, and locale
• capability parsing, launch grants, and runtime boundary checks
• Rust sample apps for clock, cat, and curl
• generated docs and CI freshness checks
• adapter split structure across Linux, macOS, and Windows crates

What Still Blocks Phase 2 Exit

The remaining work is mostly proof:

1. freeze UAPI v0.1 after review
2. collect clean Linux, macOS, and Windows evidence for the same samples
3. keep the Go track experimental until import purity passes
4. run longer fuzz and benchmark evidence
5. do one timed external walkthrough
6. record the retrospective and Phase 3 kickoff

Quick Readiness Command

To get the current gate count in one terminal command:

scripts/phase2-exit-readiness.sh

This does not replace the ledger. It reads this page and prints the current number of done, strong-draft, partial, pending, and blocked gates. It also prints the hard blockers so a returning session can start from the right place. Run it with --all when preparing a handoff or exit review packet; that mode prints every open proof item with its next step.

Local Evidence Commands

Run these before a Phase 2 exit review:

scripts/record-phase2-exit-bundle.sh --strict
scripts/check-uapi.sh
scripts/generate-uapi-freeze-evidence.sh
scripts/generate-uapi-freeze-lock.sh
scripts/check-uapi-freeze-lock.sh
scripts/check-phase2-freeze-decision.sh
scripts/check-adapter-boundary.sh
scripts/record-phase2-adapter-evidence.sh
scripts/compare-phase2-adapter-evidence.sh
scripts/check-phase2-exit-evidence.sh
scripts/record-phase2-sample-evidence.sh
scripts/compare-phase2-sample-evidence.sh
scripts/record-phase2-rust-sdk-evidence.sh
scripts/record-phase2-language-variant-evidence.sh
scripts/compare-phase2-language-variant-evidence.sh
scripts/record-phase2-go-readiness-evidence.sh
scripts/record-phase2-ucap-evidence.sh
scripts/compare-phase2-ucap-evidence.sh
scripts/record-phase2-benchmark-evidence.sh
scripts/compare-phase2-benchmark-evidence.sh
scripts/record-phase2-dependency-evidence.sh
scripts/record-phase2-fuzz-evidence.sh
scripts/check-phase2-rust-walkthrough-rehearsal.sh
scripts/record-phase2-walkthrough-template.sh
scripts/check-phase2-walkthrough-evidence.sh <filled-walkthrough.md>
scripts/record-phase2-ci-stability-evidence.sh
scripts/record-phase2-hosted-full-ci-evidence.sh
scripts/record-phase2-self-hosted-evidence.sh
scripts/check-phase2-closeout-docs.sh
scripts/smoke-rust-sdk.sh
scripts/build-phase2-language-variant-fixtures.sh
scripts/test-phase2-language-variants.sh
scripts/phase2-exit-readiness.sh

The Exit Bundle command gives the quick local review report. The other commands are still useful when you need the detailed per-area reports. The exit bundle now includes the closeout docs check and can optionally include hosted CI stability and self-hosted full-gate evidence, so the final review packet can carry current GitHub run history beside the local proof.

For performance and soak checks:

cargo bench -p krate-runtime --bench startup
cargo bench -p krate-runtime --bench uapi_dispatch
scripts/check-benchmark-regression.sh
scripts/check-dependencies.sh
scripts/record-phase2-fuzz-evidence.sh --strict
scripts/run-phase2-fuzz-smoke.sh

CI Evidence We Still Need

For formal exit, save the run links in the Phase 2 plan:

• one recent hosted CI green run
• one hosted CI stability report from scripts/record-phase2-ci-stability-evidence.sh
• one hosted full CI report from scripts/record-phase2-hosted-full-ci-evidence.sh
• one recent self-hosted full gate green run on macOS ARM64
• Linux and Windows hosted or trusted runner evidence for the sample outputs
• one longer self-hosted fuzz run after the final UAPI freeze candidate
• one benchmark baseline check after the final sample set is fixed
• one dependency evidence report for the final commit, with hosted advisory proof if local advisory DB locking is unavailable
• one final pass of scripts/check-phase2-closeout-docs.sh after the retrospective and Phase 3 kickoff issue are updated from draft to final

That is enough to move Phase 2 from strong engineering progress to a clean phase exit.

The hosted CI stability recorder is documented in CI Stability Evidence.