chore(B-0517) + shard(tick): 1927Z — razor-cadence item 5 (MEMORY.md bloat)#3204
Merged
AceHack merged 1 commit intoMay 14, 2026
Merged
Conversation
…d (MEMORY.md bloat) (renumbered from B-0516 due to multi-Otto ID collision — a parallel Otto had also claimed B-0516 in chore/b-0516-gates-ecc-physical-compression-research- direction-2026-05-14 in-flight; B-0517 is the next safe ID) Razor-cadence item 5 (MEMORY.md index audit) investigation: - User-scope MEMORY.md: 242 lines / 66KB / 237 entries - Cold-boot loads first 200 lines only → ~37 lines (15%) unreachable - Average entry size 275 chars vs 200-char guidance - ~100-130 entries exceed limit; top 5 are 500-620 chars Root cause: paragraph-length entries duplicate content already in topic file frontmatter description: field. B-0517 two-phase plan: - Phase 1: bulk cleanup of ~130 entries (trim index; full detail stays in topic files) - Phase 2: mechanize via tools/hygiene/audit-user-scope-memory-index.ts (parallel to PR #3202's audit-rule-cross-refs.ts) Composes with B-0006, PR #3202, razor-cadence #3128, B-0506. Side observation: multi-Otto ID-collision recurred despite PR #3153's ID- allocation discipline (on-disk + in-flight check). Both Ottos extracted top B-0515 from on-disk and incremented; in-flight check missed because the parallel Otto's branch had a non-standard name (chore/b-0516-gates-ecc-*) that didn't match the search heuristic. Substrate-honest acknowledgment; discipline holds but search-heuristic needs widening to catch this case. Co-Authored-By: Claude <noreply@anthropic.com>
AceHack
deleted the
chore/b-0517-memory-md-index-bloat-audit-otto-cli-2026-05-14
branch
There was a problem hiding this comment.
Pull request overview
This PR records a razor-cadence investigation into user-scope MEMORY.md index bloat and files B-0517 to track cleanup plus future mechanized auditing.
Changes:
- Adds a 1927Z hygiene tick shard documenting the investigation and findings.
- Adds backlog row B-0517 for cleanup and audit-tool follow-up.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
docs/hygiene-history/ticks/2026/05/14/1927Z.md |
Captures the tick’s MEMORY.md bloat investigation and next-step visibility notes. |
docs/backlog/P3/B-0517-memory-md-index-bloat-cleanup-cadence-2026-05-14.md |
Defines the backlog item for one-time MEMORY.md cleanup and future enforcement tooling. |
Comments suppressed due to low confidence (1)
docs/backlog/P3/B-0517-memory-md-index-bloat-cleanup-cadence-2026-05-14.md:62
- P1 correctness: the proposed audit would miss the documented 25KB truncation mode if it only computes lines past 200. The existing loading-taxonomy memory says MEMORY.md loads the first 200 lines OR 25KB, whichever comes first, so the tool needs to report byte-cap risk as well as line-cap risk to avoid false negatives on large one-line entries.
- Computes truncation risk (lines past 200)
| - B-0006 (memory-md hub compression — prior cleanup work on MEMORY.md) | ||
| - `tools/hygiene/audit-rule-cross-refs.ts` (PR #3202 — parallel mechanization) | ||
| - Razor-cadence #3128 daily fire (item 5 is the MEMORY.md index audit) | ||
| - `encoding-rules-without-mechanizing.md` rule |
| Otto-CLI 2026-05-14T19:27Z razor-cadence item 5 (MEMORY.md index audit) investigation found: | ||
|
|
||
| - **`~/.claude/projects/-Users-acehack-Documents-src-repos-Zeta/memory/MEMORY.md` has grown to 242 lines / 66KB / 237 entries** (the user-scope MEMORY.md, NOT the repo-scope one). | ||
| - Cold-boot loads the first 200 lines / 25KB only; **~37 lines (15%) past the cutoff are unreachable at fast-path** for new sessions. |
| | Average entry size | 275 chars | | ||
| | Entries > 200 chars | ~100-130 | | ||
| | Cold-boot truncation cutoff | line 200 / 25KB | | ||
| | Lines unreachable at fast-path | ~37 (15%) | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Razor-cadence item 5 investigation: user-scope MEMORY.md is 242 lines / 66KB / 237 entries. Cold-boot loads first 200 lines only — ~37 lines (15%) silently unreachable. ~130 entries exceed the 200-char guidance.
B-0517 captures two-phase plan: (1) bulk cleanup of over-long entries; (2) mechanize via
tools/hygiene/audit-user-scope-memory-index.ts(parallel to PR #3202).(Renumbered from B-0516 → B-0517 due to multi-Otto ID-collision; substrate-honest disclosure in commit message.)
🤖 Generated with Claude Code