nevenincs 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.
- Confirm sufficient Research, Reference, or Audit evidence. Gather missing evidence
through
vaultspec-researchfor option research orvaultspec-code-researchfor 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>(orcreate). Read.vaultspec/templates/adr.md. - Draft the decision, or dispatch
vaultspec-adr-researcherwith 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 runvaultspec-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.