Skip to content

@media (max-width: 60rem) { .vs-docs-menu-toggle { display: none; } .vs-docs-nav { display: block; order: 2; } .vs-docs-main { order: 1; } .vs-docs-onpage-rail { order: 3; } }

How Vaultspec worksLink to How Vaultspec works

Vaultspec stores the reasoning and verification for a feature beside its code. One feature tag connects the records.

Stage	Record	Purpose	Approval
Research	`.vault/research/` or `.vault/reference/`	Evidence, existing behavior, and options	Confirm the evidence before a decision
Decision	`.vault/adr/`	Chosen approach, rejected alternatives, and consequences	Approve before planning
Plan	`.vault/plan/`	Ordered implementation steps and verification	Approve before execution
Execute	`.vault/exec/`	Files changed and verification evidence	Follow the approved plan
Review	`.vault/audit/`	Scope, findings, and recommendations	Resolve blocking findings

Feature indexes under .vault/index/ are generated. Runtime state under .vault/data/ is local and must not be committed.

What you approveLink to What you approve

Two decisions are yours, and the agent stops for both: the architecture decision before anything is planned, and the plan before anything is built. Approve a decision when it matches the requirement, and reject an ADR that leaves one unresolved.

The review at the end is a separate gate. Record validation checks structure and links, so it can pass over an implementation nobody has proved.

Find the current stateLink to Find the current state

vaultspec-core status search-api

Where to go nextLink to Where to go next

Run a feature from research to review - the three prompts and the two approvals, stage by stage.
Core CLI reference - exact commands and advanced plan management.
Document syntax - for authoring records by hand.