Skip to content

docs: fix drift in Consolidation & Decay - #309

Draft
jack-arturo wants to merge 1 commit into
mainfrom
docs/audit-core-concepts-consolidation-20260817
Draft

docs: fix drift in Consolidation & Decay#309
jack-arturo wants to merge 1 commit into
mainfrom
docs/audit-core-concepts-consolidation-20260817

Conversation

@jack-arturo

Copy link
Copy Markdown
Member

First audit of this page. Corrected against automem@42ba8b6.

Claim Current state Fix Evidence
Source-note deep links pinned to ebcf5f16 with line anchors #L100 (class), #L1091 (scheduler), #L270-L363, #L365-L463, #L464-L605, #L606, #L978-L1004, and runtime_helpers.py#L59-L80 At current HEAD the symbols live elsewhere: MemoryConsolidator L121, ConsolidationScheduler L1118, calculate_relevance_score L227-L283, discover_creative_associations L334-L456, cluster_similar_memories L457-L618, apply_controlled_forgetting L619, identity block L978-L1002, apply_scheduler_overrides L78-L100 Repinned every source-note link to 42ba8b6 and corrected the line numbers consolidation.py#L121, #L1118
SUMMARIZES link query: MATCH (meta:MetaPattern), (m:Memory {id: $member_id}) Nodes are created as :Memory:MetaMemory with type: 'MetaPattern' as a property, not a label; the link query matches (meta:MetaMemory {id: $meta_id}) — a :MetaPattern label match would return nothing Fixed the Cypher and clarified label vs. type property consolidation.py#L931-L957
"MetaMemory Node Properties" table lists label, dominant_type, temporal_span_days, created_at The persisted node stores exactly id, content, type, confidence (0.8), cluster_size, timestamp, relevance_score (0.9); dominant_type/temporal span are computed for the summary string only Rewrote the table to the fields actually written by the CREATE, with a note that the others are not persisted consolidation.py#L926-L938
"hard-coded in consolidation.py at automem@0720da2" Stale SHA reference in prose (the size >= 5 gate is still current) Repinned to 42ba8b6 consolidation.py#L926

Verified against: automem@42ba8b61b7d0b24ecaeb7feb4ceef59f09fc7cd0

Spot-checked and confirmed accurate (left unchanged): the creative-task connection rules and confidence values (CONTRADICTS/explains/shares_theme/parallel_context), the MemoryConsolidator constructor's nonzero raw defaults vs. 0.0 deployed thresholds, the identity-interval default logic, and RECALL_EXCLUDED_TYPES=MetaPattern.

Questions

None.

Unverified

None.

Follow-ups

None.

Draft because the MetaMemory properties fix and label clarification adjust explanatory prose and a code sample.


Generated by Claude Code

Correct code-anchored claims against automem@42ba8b6:
- Repin all source-note deep links from ebcf5f16 to 42ba8b6 and fix line numbers (MemoryConsolidator L121, ConsolidationScheduler L1118, decay L227-L283, creative L334-L456, cluster L457-L618, forget L619, identity L978-L1002, apply_scheduler_overrides L78-L100)
- SUMMARIZES link query matches the MetaMemory label, not a non-existent MetaPattern label; nodes are created as :Memory:MetaMemory with type='MetaPattern' as a property (consolidation.py L931-L957)
- Rewrite MetaMemory Node Properties table to the fields actually persisted (id, content, type, confidence, cluster_size, timestamp, relevance_score); dominant_type/temporal span are not stored (consolidation.py L926-L938)
- Repin stale automem@0720da2 prose reference to 42ba8b6

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015PuVebr9vp2BdLnQfXo3AC
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying automem-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: e3a9855
Status: ✅  Deploy successful!
Preview URL: https://7681ec50.automem-website.pages.dev
Branch Preview URL: https://docs-audit-core-concepts-con-f6ni.automem-website.pages.dev

View logs

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.

2 participants