Skip to content

Route research reports to recall KB with auto-distillation#39

Open
wpfleger96 wants to merge 2 commits into
mainfrom
feat/research-artifact-lifecycle
Open

Route research reports to recall KB with auto-distillation#39
wpfleger96 wants to merge 2 commits into
mainfrom
feat/research-artifact-lifecycle

Conversation

@wpfleger96
Copy link
Copy Markdown
Owner

This PR routes /research skill output into the recall knowledge base instead of the invoking repo's working directory, eliminating untracked file accumulation and enabling cross-repo discovery.

Previously, every research run wrote a research-report_*.md file to $PWD, leaving reports siloed across whichever repo the skill was invoked from with no centralized search path. Running the same topic twice produced a second file with no deduplication.

  • Change Phase 4 in SKILL.md to write via mcp__recall__write_note to research/{topic-slug}.md; falls back to CWD write when recall MCP isn't connected
  • Add Phase 5 that automatically distills each report into a thin references/research/{topic-slug}.md reference note (Bottom Line + 4-6 atomic observations + wikilink to the full report) — atomic layer for search_notes retrieval, full report for provenance
  • Add mcp__recall__write_note, mcp__recall__edit_note, mcp__recall__search_notes, mcp__recall__read_note to allowed-tools and a Repo slug context variable
  • Add YAML frontmatter (type: research, source_repo, confidence) to the report-format.md template; companion research taxonomy type added directly to the recall repo

wpfleger96 and others added 2 commits May 15, 2026 13:25
Research reports accumulated as untracked git files across every repo
they were invoked from, creating persistent git status noise with no
centralized discovery path.

Reports now go to recall's new `research/` taxonomy type via
`mcp__recall__write_note` (CWD fallback when recall isn't connected).
Phase 5 automatically distills each report into a thin atomic
`references/research/` note with wikilink back to the full report —
two-layer architecture matching the parent-child RAG pattern where
atomic notes serve retrieval and full reports preserve provenance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant