Skip to content

LastVet positions

Ryan writes and approves every position. Agents must not invent stance text.

This folder is a dated ledger of stances, the same family as /claims and /legal/changelog. It is not a blog.

Add or publish an entry

  1. Copy a draft in this folder, or edit one of the three stubs.
  2. Fill all four sections: What changed, Why it matters for veterans, LastVet's position, What we're doing.
  3. Add real https:// source URLs. Publish is rejected without them.
  4. Write stanceOneLiner (index card). No stance, no publish.
  5. What we're doing is dated actions only. Each published action needs a YYYY-MM-DD date. Do not publish a "we will" with no current act. Describe the nature of the work, not the stack: no servers, vaults, object stores, table names, or encryption internals. Same opsec rule as docs/legal/LEGAL_RELEASE_SOP.md.
  6. Set "status": "published" only when Ryan has approved the copy.
  7. HIPAA Security Rule entries must keep "instrumentStatus": "proposed" until a final rule exists. The loader will reject a current label on hipaa-security-rule-2027.

Drafts never appear on the public index or in the sitemap. next dev can preview them.

File shape

JSON front matter between --- fences, then exactly four ## headings, in order:

---
{ ... }
---

## What changed

## Why it matters for veterans

## LastVet's position

## What we're doing

slug must match the file name. domain is identity | cds | privacy. status is draft | published. instrumentStatus is current | proposed.

Scope

Veteran care, health data, coordination, identity-for-records, device/CDS, privacy/security. If a bill is outside that standing, it does not get a file.

Update vs new file

If the same instrument is revised, update that entry (bump updatedOn, keep the URL). Do not spawn a second post.