Vaultspec Code Research

Code research (vaultspec-code-research)

Produces a Reference record: how a codebase (this project, a submodule, or an external reference) implements the thing, as patterns with locators. It is an entry point alongside vaultspec-research; sufficient Audit evidence can also ground an ADR. This skill terminates within one run.

Steps

• Locate by meaning: vaultspec-rag search "<concept and domain nouns>" --type code, and the governing decisions with vaultspec-rag search "<intent>" --type vault --doc-type adr. Read the epicenter or nearest analogue whole, then confirm exact symbols with grep. Where vaultspec-rag is unavailable, the vaultspec-core discovery verbs and grep carry the same sequence.
• Scaffold: vaultspec-core vault add reference --feature {feature} (or the create tool). Read .vaultspec/templates/reference.md; its hint blocks fix the body shape.
• Audit in this run, or dispatch the vaultspec-reference-auditor persona to locate and audit the {feature} implementation in the named codebase; it returns findings for you to persist. If the record exists already, update its body.
• Verify with vaultspec-core vault check all.

Quality gate

• Faithful. Exact module and file:line; the reference's version or commit pinned.
• Pattern-level. Abstractions, boundaries, and module interactions; never pasted implementation.
• Mapped. How the pattern translates to this codebase, and where it will not fit.
• Load-bearing only. The abstractions a re-implementation needs, not a tour.

Next

Apply the system's decision coverage test to findings that suggest a change. Routine execution uses existing scope; a new costly commitment routes to vaultspec-adr. Report findings without changing implementation unless that work is authorized.