Conversation
…ies shortened) Reviewer on #1289 flagged the consent-driven UX entry as too verbose for an index line. memory/README.md + system-prompt convention say entries should be terse one-liners (~150 chars). My recent additions were 800-1200+ chars each — significantly over. Trimmed 5 entries I added in this session: 1. Consent-driven UX (was 1229 chars → 372 chars) 2. Same-tick-update-recursion (was 1058 chars → 271 chars) 3. architectural-intent-guesses dir (was 903 chars → 261 chars) 4. Guess-then-verify protocol (was 1267 chars → 274 chars) 5. Alignment-frontier (was 842 chars → 320 chars) Strategy: keep the title (with attribution) + a one-line hook capturing the load-bearing essence. Detail belongs in the linked memory file body. Older entries on this surface (Verify-then-claim 1189 chars, Skill design 896 chars) are also over the convention but predate this session; deferring those to a separate hygiene PR rather than scope-creep this fix. Lesson: even index entries need substrate-quality discipline. The ~150-char convention exists because MEMORY.md is loaded as fast-path context — verbose entries crowd out signal-to-noise at exactly the layer where future-Otto reads first. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
4 tasks
AceHack
deleted the
fix/memory-md-entries-too-verbose-trim-recent-additions-otto-2026-05-03
branch
This was referenced May 3, 2026
There was a problem hiding this comment.
Pull request overview
This PR trims several recently-added entries in memory/MEMORY.md to better fit the repo’s convention that the index remains a terse, newest-first fast-path into the underlying memory files.
Changes:
- Shortened 5 verbose
MEMORY.mdindex entries into more compact one-liners. - Kept links intact while moving detail into the referenced memory-file bodies (per the stated strategy).
Member
Author
|
Both findings addressed:
Auto-merge armed on #1294. Resolving. |
AceHack
added a commit
that referenced
this pull request
May 3, 2026
…1292 follow-up) Reviewer P2 nit on #1292: "Architect-models-are-UX-weak is calibration-class" reads as a fragment/term-of-art. Rewritten as a complete sentence: "Architect-trained models being UX-weak is itself a calibration-class inference failure to track." Reviewer's other nit (verbatim quotes still inline) was stale — the trimmed entry has no verbatim quotes, so the finding doesn't apply to current state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 3, 2026
…tries shortened) + cross-disciplinary rebased (#1293) Reviewer caught Otto's verbose-entry pattern. #1292 trimmed 5 entries from 800-1267 chars to 261-372 chars per ~150-char convention. #1291 cross-disciplinary entry similarly trimmed via rebase + amend. Pattern lesson: even index entries need substrate-quality discipline. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 3, 2026
…1292 follow-up) Reviewer P2 nit on #1292: "Architect-models-are-UX-weak is calibration-class" reads as a fragment/term-of-art. Rewritten as a complete sentence: "Architect-trained models being UX-weak is itself a calibration-class inference failure to track." Reviewer's other nit (verbatim quotes still inline) was stale — the trimmed entry has no verbatim quotes, so the finding doesn't apply to current state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 3, 2026
…1292 follow-up) Reviewer P2 nit on #1292: "Architect-models-are-UX-weak is calibration-class" reads as a fragment/term-of-art. Rewritten as a complete sentence: "Architect-trained models being UX-weak is itself a calibration-class inference failure to track." Reviewer's other nit (verbatim quotes still inline) was stale — the trimmed entry has no verbatim quotes, so the finding doesn't apply to current state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 3, 2026
…1292 follow-up) (#1294) Reviewer P2 nit on #1292: "Architect-models-are-UX-weak is calibration-class" reads as a fragment/term-of-art. Rewritten as a complete sentence: "Architect-trained models being UX-weak is itself a calibration-class inference failure to track." Reviewer's other nit (verbatim quotes still inline) was stale — the trimmed entry has no verbatim quotes, so the finding doesn't apply to current state. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Reviewer on #1289 (P2 nit) flagged the consent-driven UX entry as too verbose for an index line. memory/README.md + system-prompt convention require entries to be terse one-liners (~150 chars).
What was wrong
My recent additions were 800-1200+ chars each. Specifically:
Strategy
Keep title + attribution + one-line hook capturing load-bearing essence. Detail belongs in the linked memory file body, not the index.
Out of scope
Older entries (Verify-then-claim 1189 chars, Skill design 896 chars) also exceed the convention but predate this session. Defer to a separate hygiene PR rather than scope-creep this fix.
Lesson
Even index entries need substrate-quality discipline. MEMORY.md is loaded as fast-path context — verbose entries crowd out signal-to-noise at exactly the layer where future-Otto reads first.
🤖 Generated with Claude Code