@mangold/rvault 0.1.0

package/templates/research-vault/project-context/FIELD_NOTES.md

@@ -0,0 +1,28 @@
+# Field Notes
+
+Development outcomes, test results, and implementation learnings
+that should inform future vault research. This file is the bridge
+between development work and the vault's knowledge base.
+
+The human (or their coding agent during normal development) appends
+entries here after implementation sessions. Vault agents consume
+these notes during their normal processes.
+
+## Entry Format
+
+### YYYY-MM-DD — [Short Title]
+
+**Context**: What were you trying to do? Reference a decision brief
+or research finding if applicable.
+
+**What happened**: What worked, what didn't, what was surprising.
+
+**Implications for the vault**:
+- Claims to update (if vault knowledge was wrong or incomplete)
+- New research questions raised
+- Problems resolved (can be closed in PROBLEMS.md)
+- Problems discovered (should be added to PROBLEMS.md)
+
+---
+
+*No entries yet.*

package/templates/research-vault/project-context/REFERENCES.md

@@ -0,0 +1,48 @@
+# Local Reference Documents
+
+These are authoritative primary sources available on the local
+filesystem. They take precedence over web search results for any
+topic they cover. Researchers MUST check relevant local references
+before or alongside web searches.
+
+## How to use these documents
+
+For large documents (100+ pages), do NOT attempt to read them in
+full. Instead:
+1. Check if an index file exists (e.g., `<short-name>-index.md`
+   in this directory) and use it to find relevant page ranges.
+2. Use text search (grep, or read specific page ranges) to find
+   relevant sections.
+3. Cite findings as: "[Document short name], Section X.Y, p. NNN"
+4. Local references are higher-authority than web sources for
+   specifications, APIs, and implementation details.
+
+## Documents
+
+| Short Name | Path | Description | Pages | Key Topics |
+|------------|------|-------------|-------|------------|
+
+*No documents registered yet. Add rows as you acquire reference
+materials for this project.*
+
+## Quick lookup by topic
+
+| Topic | Check first | Then |
+|-------|------------|------|
+
+*Populate this table as documents are added. Map commonly-researched
+topics to the most relevant reference document so researchers can
+find the right source quickly.*
+
+## Adding new references
+
+When adding reference documents:
+- Use a short, citable name
+- Provide the filesystem path (relative to project root)
+- Briefly describe what the document covers
+- Note approximate page count
+- List key topics so researchers know when to consult it
+- For documents over 100 pages, consider generating an index file
+  (see project-context/<short-name>-index.md pattern)
+- Update the Quick Lookup table if the document covers a
+  commonly-researched topic