ALL MEMOS
Download .docx
Memory Annotator — 2026-05-17
_Files reviewed: 165_
TL;DR
Memory contains many stale files, including old nightly reports and historical snapshots that should be archived. Critical conflicts exist in UI design guidance and AI service routing rules that require immediate resolution. Several files related to job applications and technical incidents are redundant and should be merged to create single sources of truth.
Stale memos
- file: upcoming_manifestation_app_2026-05-09.md · reason: The target due date of 2026-05-09 / 2026-05-10 has passed.
- file: precompact-*.md files · reason: These are numerous historical snapshots from April and early May, likely no longer relevant to the current state.
- file: nightly-report-*.md files before 2026-05-10 · reason: These older reports use a verbose, outdated format and track issues that may no longer be relevant.
- file: feedback_prism_hierarchy_and_gems_theme_20260514.md · reason: This UI theme has been explicitly superseded for new surfaces by the pattern in 'feedback_chat_first_ui_pattern_20260515.md'.
Conflicts
- files: ['feedback_prism_hierarchy_and_gems_theme_20260514.md', 'feedback_chat_first_ui_pattern_20260515.md'] · issue: One file designates the 'GEMS theme' (cyan HUD) as canonical, while the other designates a 'Cool blue' theme and explicitly forbids the HUD look.
- files: ['feedback_cache_ai_assets_on_s3_20260509.md'] · issue: The file contains an internal contradiction: the 'Provider preference order (image)' table does not match the 'Routing rule' text description of which tier to use for which use-case.
- files: ['MEMORY.md', 'feedback_newsletters_are_daily_20260511.md'] · issue: 'MEMORY.md' lists newsletters with 'Weekly' in their names, directly contradicting the rule in 'feedback_newsletters_are_daily_20260511.md' which states all newsletters are daily and the 'weekly' suffix is legacy.
- files: ['feedback_application_demographics_20260514.md', 'feedback_visa_status_green_card_20260514.md'] · issue: Both files define answers for the same work authorization questions, creating redundant sources of truth.
Merge candidates
- keep: feedback_application_demographics_20260514.md · merge_in: ['feedback_visa_status_green_card_20260514.md', 'feedback_direct_company_only_20260514.md'] · reason: All three files concern job application rules and auto-fill data; they should be consolidated into a single file.
- keep: feedback_ses_cold_start_latency.md · merge_in: ['feedback_no_duplicate_ses_send_20260503.md'] · reason: Both files describe the same boto3/SES latency incident from 2026-05-03 and should be combined.
- keep: a new summary file, e.g., 'nightly-reports-archive-apr-may-2026.md' · merge_in: ['nightly-report-2026-04-24.md', 'nightly-report-2026-04-25.md', 'nightly-report-2026-04-26.md', 'nightly-report-2026-04-27.md', 'nightly-report-2026-05-01.md', 'nightly-report-2026-05-02.md', 'nightly-report-2026-05-03.md', 'nightly-report-2026-05-04.md', 'nightly-report-2026-05-05.md', 'nightly-report-2026-05-07.md', 'nightly-report-2026-05-09.md'] · reason: The numerous verbose nightly reports from before the format change on 2026-05-10 could be consolidated into a single archive.