Memory Annotator — 2026-05-22

_Files reviewed: 175_

TL;DR

The memory base contains several durable rules but is cluttered with numerous stale nightly reports and low-level snapshots from April and early May. Key conflicts exist, including an outdated newsletter schedule in the main index file and contradictory routing rules for AI image generation. Consolidation is recommended for job application rules and UI themes, and the many stale report files should be archived to improve clarity.

Stale memos

file: MEMORY.md · reason: Lists newsletters as "Weekly" which conflicts with the "daily" rule in "feedback_newsletters_are_daily_20260511.md".
file: nightly-report-2026-04-24.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-04-25.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-04-26.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-04-27.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-01.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-02.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-03.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-04.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-05.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-07.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: nightly-report-2026-05-09.md · reason: Superseded by a new, more structured report format starting 2026-05-10 and contains outdated system status.
file: precompact-.md · reason: All 58 precompact-.md files are low-level, voluminous system snapshots with unclear current value and should be archived.

Conflicts

files: ['MEMORY.md', 'feedback_newsletters_are_daily_20260511.md'] · issue: MEMORY.md lists "Scheduled Newsletters" as "Weekly", while "feedback_newsletters_are_daily_20260511.md" explicitly states all newsletters are "daily".
files: ['feedback_chat_first_ui_pattern_20260515.md', 'feedback_prism_hierarchy_and_gems_theme_20260514.md'] · issue: The newer "chat-first" UI pattern supersedes the "GEMS" theme for jarvis.livegroweveryday.com apps, but the GEMS file doesn't reflect this limited scope.
files: ['feedback_cache_ai_assets_on_s3_20260509.md'] · issue: Internal conflict: The image generation "Routing rule" section misaligns provider names with tiers defined in the table (e.g., says "Tier C (Gemini)" when Tier C is Bedrock).

Merge candidates

keep: feedback_application_demographics_20260514.md · merge_in: ['feedback_visa_status_green_card_20260514.md'] · reason: Both files define auto-fill data for job applications and should be a single, consolidated profile.
keep: feedback_ses_cold_start_latency.md · merge_in: ['feedback_no_duplicate_ses_send_20260503.md'] · reason: Both files describe the same boto3 latency incident and its consequences, and should be one memory.
keep: feedback_chat_first_ui_pattern_20260515.md · merge_in: ['feedback_prism_hierarchy_and_gems_theme_20260514.md'] · reason: Consolidates all UI/UX theme guidance into one file, clarifying the scope and priority of each theme.