moradin:capture
Capture an external source as a reference. Capture EVERYTHING notable, not just what fits the current project. Project-specific filtering happens later at distillation time.
When invoked
/moradin:capture <url> (or /moradin:capture <description> if not URL)
The operator saw something interesting and wants to record it permanently.
What you do
WebFetch the URL (or read source if local). Read README + key sections.
List ALL notable concepts in your reply. Don't pre-filter for current project relevance. Show the operator a full inventory of what's in the source:
- Concept A: [one paragraph]
- Concept B: [one paragraph]
- Concept C: [one paragraph]
- ...
For each concept, propose tags:
topics: from the 8-tag taxonomy (harness, memory, eval, llm, agent, arch, workflow, tooling)
applies_to: which projects might use it (universal, godtech, trading, future)
Ask the operator to confirm or edit the tags. Don't auto-write — get a green light.
Note what you deliberately skipped — tactical setup details, deeply specific code, or items fundamentally irrelevant.
Write the reference file at memory/references/<source_name>.md using templates/reference.template.md as scaffold. Include:
- Frontmatter: name, description, topics, applies_to, type=reference, url, captured (date), last_verified (date)
- Body: "What it is" + "Notable concepts" (full inventory) + "What I deliberately skipped"
Update indexes. Run python scripts/refresh_indexes.py so _INDEX.md reflects the new file.
Confirm to operator with the file path.
Capture discipline (the rule that protects against losing useful concepts)
The big failure mode: filtering concepts at capture time based on current project. Don't. Concepts that don't fit GodTech today may fit trading next month. Capture full inventory.
Don't
- Don't summarize away interesting-but-tangential concepts. Capture them.
- Don't auto-assign tags without operator confirmation.
- Don't write attribution like "inspired by X" — once captured, the concepts are ours.
- Don't capture a reference if we've already captured the same source — update the existing file instead.
Output
- New file at
memory/references/<source_name>.md
- Updated
memory/references/_INDEX.md (and top-level memory/_INDEX.md)
1---2name: moradin-capture3description: Capture an external source (URL, repo, paper) as a reference in memory/references/. Full unfiltered concept inventory.4---56# moradin:capture78Capture an external source as a reference. **Capture EVERYTHING notable, not just what fits the current project.** Project-specific filtering happens later at distillation time.910## When invoked1112`/moradin:capture <url>` (or `/moradin:capture <description>` if not URL)1314The operator saw something interesting and wants to record it permanently.1516## What you do17181. **WebFetch the URL** (or read source if local). Read README + key sections.19202. **List ALL notable concepts** in your reply. Don't pre-filter for current project relevance. Show the operator a full inventory of what's in the source:21 - Concept A: [one paragraph]22 - Concept B: [one paragraph]23 - Concept C: [one paragraph]24 - ...25263. **For each concept, propose tags:**27 - `topics`: from the 8-tag taxonomy (harness, memory, eval, llm, agent, arch, workflow, tooling)28 - `applies_to`: which projects might use it (universal, godtech, trading, future)29304. **Ask the operator to confirm or edit the tags.** Don't auto-write — get a green light.31325. **Note what you deliberately skipped** — tactical setup details, deeply specific code, or items fundamentally irrelevant.33346. **Write the reference file** at `memory/references/<source_name>.md` using `templates/reference.template.md` as scaffold. Include:35 - Frontmatter: name, description, topics, applies_to, type=reference, url, captured (date), last_verified (date)36 - Body: "What it is" + "Notable concepts" (full inventory) + "What I deliberately skipped"37387. **Update indexes.** Run `python scripts/refresh_indexes.py` so `_INDEX.md` reflects the new file.39408. **Confirm to operator** with the file path.4142## Capture discipline (the rule that protects against losing useful concepts)4344The big failure mode: filtering concepts at capture time based on current project. **Don't.** Concepts that don't fit GodTech today may fit trading next month. Capture full inventory.4546## Don't4748- Don't summarize away interesting-but-tangential concepts. Capture them.49- Don't auto-assign tags without operator confirmation.50- Don't write attribution like "inspired by X" — once captured, the concepts are ours.51- Don't capture a reference if we've already captured the same source — update the existing file instead.5253## Output5455- New file at `memory/references/<source_name>.md`56- Updated `memory/references/_INDEX.md` (and top-level `memory/_INDEX.md`)