Skip to content

Last 1 documentation index (lastvet-gates)

Purpose: Cross-product home for authoritative Last1 planning, architecture, compliance, and gate specs. Agents and engineers start here instead of inferring from Claude project attachments or repo fragments.

Last updated: August 2026 (docs-reorganization).

Directory layout

lastvet-gates/
├── AGENTS.md, PARKED.md, CRISIS_PROTOCOL.md, …   ← agent rules + design law (repo root)
├── gates/                                         ← gate build specs (peer to docs/, not under it)
├── MERIDIAN_GATES_PARALLEL_TRACK.md               ← Meridian × gates context only
└── docs/
    ├── README.md                                  ← this index
    ├── security/                                  ← canonical security posture (whitepaper source)
    ├── compliance/                                ← signed attestations, counsel letters (PDF)
    ├── lastvet/                                   ← Bible stack + AWS authoritative docs
    └── architecture/                              ← R940 / migration planning

Rule: gates/ stays at repo root. It holds planning artifacts with their own lifecycle, not reference documentation under docs/.

Reading order for a new engineer joining LastVet

  1. ../AGENTS.md — Phase 1 scope, gates, invariants.
  2. security/POSTURE.md — Canonical security posture index (whitepaper source).
  3. ../.cursor/rules/00-invariants.mdc — Non-negotiable compliance trip-wires.
  4. lastvet/LASTVET_BIBLE.md — v1.0 base (read header callout first).
  5. lastvet/LASTVET_BIBLE_AMENDMENT_v1.1.md — v1.1 delta (ecosystem + revenue).
  6. lastvet/LastVet_Bible_v1.1.pdf — Published merged v1.1 (optional single-file read).
  7. compliance/CARIN_Code_of_Conduct_2023_signed.pdf — Signed CARIN Code of Conduct attestation.
  8. compliance/CARIN_Confirmation_Email_Faltz_2026-04-15.pdf — Leavitt Partners confirmation (April 15, 2026).
  9. lastvet/AWS_ENVIRONMENT.md — What runs on AWS today (especially §14 for controls).
  10. lastvet/AWS_OPS_CONSOLE.md — How to operate AWS stacks.
  11. lastvet/README-zfs-recovery.md — R940 ZFS encryption key recovery (lastvet-imaging on tank-bulk).
  12. ../../last.vet-api/docs/deployment/ENVIRONMENT_TOPOLOGY.md — Staging vs prod hard walls.
  13. architecture/R940_PLATFORM_ARCHITECTURE.md — Target platform (if touching R940).
  14. architecture/LASTVET_MIGRATION_PLAN.md — If working on AWS → R940 migration.
  15. ../gates/GATE_0.5_hardening_and_proof.md — Current gate Definition of Done.

For Sovereign or Angel: read architecture/SOVEREIGN_ARCHITECTURE_V2.md or architecture/ANGEL_ARCHITECTURE_V2.md after step 12.

Bible + published PDF relationship

The Bible stack is architectural and strategic. It is separate from compliance attestation (see CARIN section below).

Artifact Role
LASTVET_BIBLE.md (v1.0) Version-controlled base markdown
LASTVET_BIBLE_AMENDMENT_v1.1.md Version-controlled delta markdown
LastVet_Bible_v1.1.pdf Published merged artifact (v1.0 + amendment rendered for print/share)

Source of truth in git: the two markdown files (base + amendment). Do not merge them into one markdown file.

PDF rule: the PDF is exported at publication time from the merged narrative. Any future change increments the amendment version (v1.2, v1.3, …), updates the markdown delta, and produces a fresh PDF at the next publication.

Header callouts at the top of each markdown file cross-link base, amendment, and PDF. Those callouts are the only intentional edits to the vendored markdown bodies.

CARIN authoritative sources

CARIN Code of Conduct attestation is not in the Bible stack. The Bible covers architecture, strategy, and product law. CARIN compliance attestation lives in docs/compliance/ plus public legal copy.

Signed artifacts (docs/compliance/)

File What it is
CARIN_Code_of_Conduct_2023_signed.pdf Signed CARIN Code of Conduct attestation. Attestor: Ryan Curry (Privacy Officer). Date: April 15, 2026. Adobe Acrobat Sign transaction ID: CBJCHBCAABAA5iGak22GtLC840ctqAxiyTGIUFZmVRZy.
CARIN_Confirmation_Email_Faltz_2026-04-15.pdf Email from Jaclyn Faltz (Jaclyn.Faltz@leavittpartners.com) to ryan@last1.enterprises, cc David Lee (David.Lee@leavittpartners.com), April 15, 2026, 12:07 PM PDT. Confirms adherence pending live FHIR API / VA Lighthouse connection. Includes forward-permission grant from Faltz for future API connection.

Current status: Adherence confirmed by Leavitt Partners; MyHealthApplication.com listing and public CARIN registry placement remain gated on live FHIR / VA Lighthouse production connection (see Faltz email and tracker below).

Other CARIN references

Source What it holds
last.vet-web Terms §13.1 Public CARIN Code of Conduct attestation language. Privacy Policy v1.0 (effective April 3, 2026) also references CARIN Trust Framework principles.
last.vet-api/docs/compliance/VA_PRODUCTION_ACCESS_TRACKER.md Timeline record for CARIN adherence confirmation and VA production access milestones.

Ryan Curry is designated Privacy Officer (Privacy Policy, Terms).

Gate specs (gates/)

Gate specs live at ../gates/ (repo root). Build only the current gate. Index:

File Purpose
GATE_0_KICKOFF.md Cursor kickoff prompt: plan-first Gate 0 entry
GATE_0_foundation.md Gate 0 foundation scope (Facilities, Forms, ROI shell; no veteran auth required)
GATE_0_ROI_KICKOFF.md Kickoff prompt for ROI / consent-share flow
GATE_0_UI_ADDENDUM.md Gate 0 UI / information-architecture addendum
GATE_0.5_hardening_and_proof.md Current gate: earn Gate 0 on AWS, harden ops/security/legal, Gate 1 entry checklist
GATE_1_KICKOFF.md Kickoff prompt for Gate 1 (after VA production approval)
GATE_1_sovereign_profile_and_os.md Gate 1 sovereign profile + Operating System mechanics
GATE_1_TRACTION_THRESHOLD.md Gate 1 traction threshold, rollout, and recruitment (D11)
GATE_1.5_conditional_ehr_prebuild.md Conditional Gate 1.5: single EHR pre-build (evidence-triggered)
GATE_2_coordination_loop.md Gate 2 coordination loop (after Gate 1 pass)
GATE_2_PROVIDER_DIRECTORY_ADDENDUM.md Gate 2 non-VA provider directory addendum
GATE_3_revenue_and_domain2.md Gate 3 revenue + second domain
HORIZON_CROSS_ECOSYSTEM_VERIFICATION.md PARKED / HORIZON: LastVet × last1.app scoped-grant integration
meridian-implementation-spec-pointer.md Pointer to canonical Meridian implementation specs in last1-meridian

Meridian gates context: ../MERIDIAN_GATES_PARALLEL_TRACK.md.

Document catalog

Document Location Status One-line purpose
LASTVET_BIBLE.md (v1.0) lastvet/ Vendored Strategy, principles, product law (unamended sections)
LASTVET_BIBLE_AMENDMENT_v1.1.md lastvet/ Vendored Parallel ecosystem + layered revenue (April 30, 2026 delta)
LastVet_Bible_v1.1.pdf lastvet/ Vendored Published merged v1.1 (binary, unmodified)
AWS_ENVIRONMENT.md lastvet/ Vendored Full AWS inventory (ECS, RDS, EFS, S3 imaging, §14 controls)
AWS_OPS_CONSOLE.md lastvet/ Vendored Console navigation and day-to-day AWS ops
README-zfs-recovery.md lastvet/ In repo R940 ZFS key recovery for tank-bulk/encrypted-lastvet-imaging
CARIN PDFs compliance/ Vendored Signed attestation + Faltz confirmation email
R940_PLATFORM_ARCHITECTURE.md architecture/ In repo R940 tenant map, sovereignty, secrets, VLANs
SOVEREIGN_ARCHITECTURE_V2.md architecture/ In repo Sovereign two-VM layout on R940
ANGEL_ARCHITECTURE_V2.md architecture/ In repo Angel Cloudflare edge + angel-local
LASTVET_MIGRATION_PLAN.md architecture/ In repo AWS → R940 cutover (~4 weeks)

Meridian spec ownership

Topic Canonical home
Implementation specs (MERIDIAN_SPEC, eval bar, M0 kickoff, telemetry) last1-meridian repo — see gates/meridian-implementation-spec-pointer.md
How Meridian relates to Gate 0/1/2 (parallel track, no blocking) MERIDIAN_GATES_PARALLEL_TRACK.md at repo root

From docs/lastvet/AWS_ENVIRONMENT.md:

API-repo documentation index: last.vet-api/docs/README.md.

Doc Current home
API engineering docs last.vet-api/docs/ (categorized subdirs)
Terms / Privacy (CARIN §13.1 public copy) last.vet-web/content/legal/
Angel deployment recon angel/ANGEL_DEPLOYMENT_PLAN.md

Note: last.vet-web/LastVet_Bible_v1.1.pdf duplicates the canonical copy under docs/lastvet/; prefer the vendored path for agents.

Verification

Byte counts for vendored authoritative files (August 2026):

File Bytes in repo Source integrity
lastvet/LASTVET_BIBLE.md 26,479 Staged body + header callout
lastvet/LASTVET_BIBLE_AMENDMENT_v1.1.md 16,020 Staged body + header callout
lastvet/LastVet_Bible_v1.1.pdf 49,259 Binary; published merge
lastvet/AWS_ENVIRONMENT.md 14,490 Byte-identical to staged source
lastvet/AWS_OPS_CONSOLE.md 7,877 Byte-identical to last.vet-api copy
compliance/CARIN_Code_of_Conduct_2023_signed.pdf 609,453 Byte-identical to staged signed attestation
compliance/CARIN_Confirmation_Email_Faltz_2026-04-15.pdf 100,775 Byte-identical to staged Faltz email

Re-verify after re-vendoring with:

wc -c docs/lastvet/* docs/compliance/*
diff ~/staged-docs/"CARIN_Code_of_Conduct_2023 - signed-1.pdf" docs/compliance/CARIN_Code_of_Conduct_2023_signed.pdf
diff ~/staged-docs/"Last 1 Enterprises Mail - My Health Application Submission - LastVet.pdf" docs/compliance/CARIN_Confirmation_Email_Faltz_2026-04-15.pdf