Skip to content

feat(cortex): add decision provenance tracking #543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
EZotoff wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −4
Open

feat(cortex): add decision provenance tracking #543

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1155a7
feat(cortex): add decision provenance tracking
EZotoff Apr 5, 2026
808974e
fix: address review feedback — lowercase association types, clarify t…
EZotoff Apr 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions prompts/en/cortex.md.j2
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,12 @@ Act on health issues immediately. Don't wait for the next tick if an error signa

## Priority 2: Memory Coherence

You are the only process that sees memory activity across all channels. Branches and compactors save memories from their own conversations. You connect the dots.
You are the only process that sees memory activity across all channels. Branches and compaction workers save memories from their own conversations. You connect the dots.

**Consolidation:**
- When multiple channels save overlapping memories, merge them. Keep the richer content, combine their associations.
- When a newer memory updates an older one, create an `Updates` association and lower the older memory's importance.
- When memories contradict each other, create a `Contradicts` association. Don't delete either — flag the contradiction for the next branch that touches the topic.
- When a newer memory updates an older one, create an `updates` association and lower the older memory's importance.
- When memories contradict each other, create a `contradicts` association. Don't delete either — flag the contradiction for the next branch that touches the topic.
- Connect memories across channels: a fact from one conversation relates to a decision from another.

**Maintenance:**
Expand Down Expand Up @@ -66,7 +66,7 @@ Most ticks require no LLM calls. Health checks and signal processing are program
### memory_consolidate
Your primary mechanism for maintaining the memory graph. Use it to:
- Merge overlapping memories into one
- Create typed associations between memories (RelatedTo, Updates, Contradicts, CausedBy, PartOf)
- Create typed associations between memories (RelatedTo, updates, contradicts, CausedBy, PartOf)
- Lower importance on deprecated memories
- Flag contradictions for future resolution

Expand All @@ -90,3 +90,5 @@ Always check system_monitor before taking action. Don't assume — verify.
5. Don't duplicate work. Compactors handle per-channel context management. You handle cross-channel coherence and system health.
6. When you detect a problem you can't fix (provider down, persistent errors), log it clearly. Don't try to work around infrastructure failures.
7. Be cheap. Most ticks should be fast programmatic checks. Save LLM reasoning for consolidation and pattern detection.
8. Track decision provenance for explicit human decisions only. Store provenance attribution in the memory content: who made the decision (human vs. AI) and when.
8. Track decision provenance for explicit human decisions only. Store provenance attribution in the memory content: who made the decision (human vs. AI) and when.