vaultspec-adr ยท diff

git:20260908.ce86e08 to git:20260924.afdc9ea

8 added, 2 removed. Audit A to A.

---
name: vaultspec-adr
description: Record a new or changed costly decision after checking accepted decision coverage and sufficient Research, Reference, or Audit evidence.
---
# ADR (vaultspec-adr)
Records one costly decision. Apply the coverage and approval contract in the vaultspec
system section before creating a record. Reuse an accepted ADR unchanged when it covers
the work, including across features; return its stem without drafting a duplicate.
## Steps
- - Discover governing decisions across features and read them whole, then their evidence.
- Classify the need as unchanged reuse, amendment, supersession, or a distinct decision.
+ - Check coverage per the `vaultspec-discovery` rule: search for the decision, then list
+ the ADRs across features. No covering record in the listing, together with a "nothing
+ in the vault answers this" (`nothing_answers`) verdict, shows the decision is new.
+ When search gives no such verdict (it declined or failed, or replied "no record that
+ was read answers this", `none_read_answers`), the ADR listing plus a targeted grep of
+ `.vault/adr/` decide coverage. That is the rule's `.vault/` grep, narrowed to
+ decisions. Read covering decisions whole, then their evidence. Classify the need as
+ unchanged reuse, amendment, supersession, or a distinct decision.
- Confirm sufficient Research, Reference, or Audit evidence. Gather missing evidence
through `vaultspec-research` for option research or `vaultspec-code-research` for code
patterns. Do not copy an adequate Audit into a new Research merely for its type.
- For a new decision, scaffold:
`vaultspec-core vault add adr --feature {feature} --related <evidence-stem>` (or
`create`). Read `.vaultspec/templates/adr.md`.
- Draft the decision, or dispatch `vaultspec-adr-researcher` with the existing evidence
and requested decision scope; it returns content for persistence.
- For an amendment, preserve accepted content while proposing the revision separately.
Follow the system's pending-proposal procedure if it must survive handoff.
- For a reversal, draft the successor first. After its content is authorized, set it
`accepted`, then run `vaultspec-core vault adr supersede OLD --by NEW`.
- Verify with `vaultspec-core vault check all`. Present the record and authorization
basis. If authorization is missing, ask and stop. Otherwise persist acceptance and
continue with the authorized work. Rejected proposals remain as evidence; rejection
never changes the accepted predecessor.
## Document boundary
Evidence stays in Research, Reference, or Audit. Cite it by stem; add missing facts to
their evidence home before using them. The ADR owns the decision, rationale, and
consequences. Decision language found in evidence moves here only when authorized.