Spec and build

Use k-spec to resolve intent and write a compact packet; k-build produces an approved packet's artifacts. An existing implementation approval is not another approval gate.

The packet records old/new rules, intended and preserved differences, the impact map (affected consumers and co-edit set), owned scope, side effects, final check commands or judgment criteria, and external decisions. Unrun criteria are planned, not red/green evidence. Prepare tests with the change; no pre-approval mutation or check-runner ceremony.

Substantial research uses the strong research band; settled implementation uses the implementation band. The root integrates compact returns and retains decisions, not source transcripts. Workers return produced/blocked artifacts without private checks. Finish docs, generation, and formatting before one final Verify stage. Execute known commands directly, once per snapshot/input identity, and use strong final judgment where needed. Report failed/blocked criteria faithfully and apply SOP §3.5 for in-scope evidence-backed recovery. Revalidate failed and affected criteria after a repair; do not repeat unchanged checks or launch speculative post-review cleanup or convergence. Commits, pushes, publication, and destructive actions retain their own explicit authority and point-of-action checks.

See staged workflows for context/lifecycle policy and truth and verification for evidence semantics.