fd0ebd64f4
Document the already-decided decomposition of subplan-02 Slice 1 so the P2.1 boundary is verifiable from the repo: - P2.1 = Core Structs + boundary validation (validation portion of Slice 1) - P2.3 = in-memory repository + db.json (rest of Slice 1) - Token = Slice 5 (Token Security), out of both Planning-doc record only; no domain or test code changed.
Detailed Subplan Index
These subplans break PLAN.md into implementation slices that can be handed to
Snarky and Opus without reloading the whole plan every time.
Reading Order
01-language-and-stdlib.md02-domain-and-storage.md03-cli-and-ci.md04-http-api-and-install.md05-artifact-validation.md06-admin-ui.md07-packaging-nas.md08-orchestration-and-qa.md
Session Contract
- Read
PLAN.md,.agents/ORCHESTRATION.md,.agents/CHECKPOINT.md, and the active subplan before doing work. - Keep work sequential. Do not use parallel implementation agents.
- Use git branches for implementation. Do not use worktrees.
- For product or UX scope, Snarky writes acceptance criteria and has final say.
- For layout and visual design, Opus has final say.
- For technical problems, consult Opus and resolve by consensus.
- Opus is the only role that writes application code during Opus phases.
- Update
.agents/CHECKPOINT.mdand.agents/checkpoint.jsonafter every completed slice, before any risky handoff, and after validation.
Slice Exit Criteria
Every slice should finish with:
- Changed files listed.
- Tests/checks run listed.
- Known risks listed.
- Next slice named.
- Checkpoint updated.
Current Priority
The first blocking priority is 01-language-and-stdlib.md. Product code should
wait until the required sx primitives exist or an explicit temporary shim is
approved.