Skip to content

Contributing to lastvet-gates

Thank you for helping build LastVet Phase 1. Read AGENTS.md and .cursor/rules/00-invariants.mdc before opening a PR.

Gates and scope

Work only the current gate (/gates). Do not pull forward features from later gates or PARKED.md.

Public documentation (external-docs/)

Public LastVet documentation ships at docs.last.vet from external-docs/ in this repo. It is separate from the internal wiki (last1-internal-docs).

Merge gates for external content

  1. WSGR approval before merge for any substantive external content (legal, medical, privacy, compliance, or trust claims).
  2. No PHI in examples, screenshots, or sample data.
  3. No security implementation details (architecture diagrams with credential flows, key material, internal hostnames, etc.).
  4. No internal references (internal wiki URLs, gate specs, staff-only runbooks, R940/BWS internal codenames).

Placeholder shells (infrastructure Phase 4) may merge without WSGR review. Phase 4b content PRs require WSGR sign-off.

Style guide (external voice)

  • Write for veterans, providers, and partners, not staff.
  • Prefer plain language over internal jargon.
  • Link official policies on last.vet rather than duplicating legal text in docs.
  • Use audience: external and a valid external_slug on every page; run python external-docs/scripts/validate-frontmatter.py before pushing.

Local checks

cd external-docs
pip install -r requirements.txt
python scripts/validate-frontmatter.py
mkdocs build --strict

See external-docs/README.md for deployment and DNS details.

Internal product docs

Gate specs, architecture, and Phase 1 build docs live under /gates and /docs in this repo. Those sync into the internal wiki via last1-internal-docs; they are not published to docs.last.vet without an explicit export review.