Problem
Memories frequently reference external systems (Linear issues, GitHub PRs, Notion docs) but these links are buried in prose content. There's no structured way to query "which memories link to OPS-655?" or "show me all memories with associated PRs."
Proposal
Add a references field to the memory schema:
{
"references": [
{"type": "linear", "url": "https://linear.app/ductone/issue/OPS-655", "label": "OPS-655"},
{"type": "github_pr", "url": "https://github.com/ductone/ops/pull/7010", "label": "ops#7010"},
{"type": "notion", "url": "https://notion.so/abc123", "label": "Exec Summary"}
]
}
- Stored as a multi-valued field in Solr for filtering
- Searchable by URL or type
- Displayed in list/search results
Why
In today's session, we created 15+ Linear issues, 2 PRs, and 2 Notion pages all related to DynamoDB cost optimization. The dynamo-audit agent's memories have no structured link back to these. Finding which memories informed which issues requires reading through all the prose.
Problem
Memories frequently reference external systems (Linear issues, GitHub PRs, Notion docs) but these links are buried in prose content. There's no structured way to query "which memories link to OPS-655?" or "show me all memories with associated PRs."
Proposal
Add a
referencesfield to the memory schema:{ "references": [ {"type": "linear", "url": "https://linear.app/ductone/issue/OPS-655", "label": "OPS-655"}, {"type": "github_pr", "url": "https://github.com/ductone/ops/pull/7010", "label": "ops#7010"}, {"type": "notion", "url": "https://notion.so/abc123", "label": "Exec Summary"} ] }Why
In today's session, we created 15+ Linear issues, 2 PRs, and 2 Notion pages all related to DynamoDB cost optimization. The dynamo-audit agent's memories have no structured link back to these. Finding which memories informed which issues requires reading through all the prose.