lastvet-gates¶
Gate-organized build specs for LastVet Phase 1 (mental-health care-coordination wedge, San Diego).
Structure¶
AGENTS.md— agent orientation (read first).cursor/rules/00-invariants.mdc— always-apply non-negotiablesPARKED.md— the do-not-build list, with the gate each item is behindgates/— one spec per gate; build only the current one (seedocs/README.mdfor index)docs/— cross-product authoritative docs (Bible, AWS, compliance PDFs, architecture)MERIDIAN_GATES_PARALLEL_TRACK.md— Meridian parallel-track context for gates (implementation specs inlast1-meridian)CRISIS_PROTOCOL.md— crisis handoff verbatim text, grader blocklist, counsel/clinical review artifactLOOP_LEDGER_AND_PROOF_MACHINE_SPEC.md— loop ledger, proof machine, read surfacesTHE_RETURN_PATH.md— veteran-facing surface design law
Gate order¶
GATE_0 → GATE_0.5 (hardening & proof) → GATE_1 → GATE_1.5 (conditional) → GATE_2 → GATE_3
Each gate unlocks exactly one next thing, on its Definition of Done. Gates are earned, not scheduled.
Current sprint: gates/GATE_0.5_hardening_and_proof.md — earn Gate 0 formally, harden for Gate 1 entry. Not new features.
Companion strategy docs (context, not build specs)¶
IP_ACTION_PLAN.md— trade secret, patent, and data-moat actionsLASTVET_REVENUE_STRATEGY_LAYER1_REFRAMED.md— the Phase 1 strategy of recordLASTVET_REVENUE_STRATEGY___THE_PARALLEL_ECOSYSTEM.md— Layers 2–6 (future)