View as Markdown

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/

One append-only ledger per plan: files changed and checks run, per step

Follow the approved plan

Review

.vault/audit/

Findings and their resolutions

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

Review the architecture decision before planning and the plan before implementation. The installed skills use your existing authorization when it covers the work. They do not promise a fixed number of approval prompts. Reject an ADR that leaves a requirement 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

Command

uvx vaultspec-core status

Where to go nextLink to Where to go next