docs(memory-md): index 3 May 2026 orphan feedback files#1580
Merged
Conversation
Surfaced via orphan-detection scan during this session: 3 May 2026 feedback files exist as substrate but were not indexed in MEMORY.md, so router-discoverability + grep-on-wake found nothing. Indexed entries (placed near existing 2026-05-03 cluster): - feedback_dst_justifies_ts_quality_over_bash_and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md - feedback_skill_bundle_compounding_empirical_hardening_into_diamond_aaron_2026_05_03.md - feedback_substrate_quality_is_lidar_not_autopilot_perception_layer_for_future_otto_aaron_2026_05_03.md Larger orphan-count finding: ~419 memory files exist that are not indexed in MEMORY.md (file is at 470 lines, cap is ~200, so the mathematical conflict is real -- index cannot grow to cover all substrate files at the current entry-per-file granularity). This commit addresses the recent orphans only; structural fix is the B-0006 cluster-folding cadence (deferred to dedicated tier passes). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds missing index entries to memory/MEMORY.md for three existing feedback_*.md files from 2026-05-03 so they’re discoverable via the shared memory index.
Changes:
- Added three new one-line
feedback_*.mdlinks tomemory/MEMORY.md. - Ensured the linked feedback files exist in
memory/(per PR intent).
#1580 reviewer feedback) Reviewer flagged that the 3 newly-indexed 2026-05-03 entries were inserted *after* a 2026-05-01 entry, breaking newest-first ordering. Moved the 2026-05-01 "class-discovery" entry to below the entire 2026-05-03 cluster (now at line 51, after all 05-03 entries). Pre-existing chronological mixing within the 05-02/05-03 zone is not addressed here -- that's a broader cleanup that B-0006 compression cadence will eventually handle. This fix is scoped to the reviewer's specific complaint about the new entries. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
deleted the
memory-md/index-3-may-2026-feedback-orphans-aaron-2026-05-05
branch
AceHack
added a commit
that referenced
this pull request
May 5, 2026
…nstall path; regen BACKLOG.md (#1571 reviewer + Aaron 2026-05-05 substrate-consistency catch) Aaron 2026-05-05 caught the substrate-consistency tension: B-0191 as originally written proposed git hooks under tools/git-hooks/ installed via symlink, but `memory/feedback_dst_justifies_ts_quality_over_bash_ and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md` (indexed in #1580 earlier this session) explicitly says git hooks are unnecessary because vibe-coders always have a harness and harness hooks suffice. Plus Aaron 2026-05-05: "i love symlinks but just an FYI nothing works right with them it always goes wrong." Revised design: - Harness hook (Claude Code PreToolUse on git-commit Bash invocations) - Implementation in TypeScript at tools/orchestrator-checks/verify-branch.ts (TS over bash per Otto-272 DST + harness-always-provides-bun) - No tools/git-hooks/ directory required - No tools/setup/ symlink install step - Per-harness wiring documented (Claude Code, Codex, Cursor, etc.) Also addresses #1571 reviewer findings: - BACKLOG.md regenerated via `BACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.ts` (was hand-edited; now matches generator) - Cross-reference to memory/feedback_orchestrator_pre_commit_verify_branch_rule_*.md resolves cleanly after rebase on main (file was merged via #1568) - tools/git-hooks/ reference removed (no longer the design) Composes_with extended to include the harness-hooks-suffice rule and B-0017 bulk-alignment UI (Aaron's note that the original inconsistency would have been caught by the planned bulk-review mechanism). Aaron 2026-05-05 verbatim: "it fine it's something we would have caught in the bulk alignment UI on the backlog" -- so the manual fix here is bonus, not required; the systematic answer is B-0017. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 5, 2026
* backlog(B-0191): orchestrator branch-verify mechanization design Aaron 2026-05-04: "for humans this is why oh my zsh reminds us of many things like this it has branch name in the ui" + "maybe a deliberate design/redesign on the backlog?" Substrate-encoding rule (PR #1551 + PR #1568) hasn't prevented recurrence — hazard hit twice in succession 2026-05-04, including in the rule-encoding commit itself. Mechanization is the substrate-level fix. Five mechanization candidates ranked: pre-commit hook (HIGH), branch-name in prompt (MED), worktree-aware status check (LOW-MED), bash git wrapper (LOW), ZETA_EXPECTED_BRANCH env-var convention (cross-cutting). Composes with PR #1568 (manual discipline) + PR #1551 (parent substrate) + B-0006 (memory work pattern) + B-0162 (similar pre-commit hook precedent). Pre-commit verified branch before commit per PR #1568 rule. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(B-0191): address 6 review threads on PR #1571 Threads addressed: 1. (P2) TS file-count baseline — TS doc removed via rebase (was accidental cross-branch contamination from concurrency hazard) 2. Absolute local path in TS doc — TS doc removed via rebase 3. Regenerate docs/BACKLOG.md to include B-0191 entry 4. Pre-commit hook example — generalized branch-pattern from "*-aaron-2026-*" to "*-yyyy-mm-dd" so it doesn't embed any specific contributor name (repo tooling, not personal) 5. Pre-commit hook location — committed under tools/git-hooks/ (version-controlled, reviewable) and installed via tools/setup/, NOT directly in .git/hooks/ which is not version-controlled 6. PR scope — TS doc removed via rebase; this PR is now scoped to B-0191 alone Verified branch before commit per PR #1568 rule. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(B-0191): switch from git hooks to harness hooks; remove symlink install path; regen BACKLOG.md (#1571 reviewer + Aaron 2026-05-05 substrate-consistency catch) Aaron 2026-05-05 caught the substrate-consistency tension: B-0191 as originally written proposed git hooks under tools/git-hooks/ installed via symlink, but `memory/feedback_dst_justifies_ts_quality_over_bash_ and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md` (indexed in #1580 earlier this session) explicitly says git hooks are unnecessary because vibe-coders always have a harness and harness hooks suffice. Plus Aaron 2026-05-05: "i love symlinks but just an FYI nothing works right with them it always goes wrong." Revised design: - Harness hook (Claude Code PreToolUse on git-commit Bash invocations) - Implementation in TypeScript at tools/orchestrator-checks/verify-branch.ts (TS over bash per Otto-272 DST + harness-always-provides-bun) - No tools/git-hooks/ directory required - No tools/setup/ symlink install step - Per-harness wiring documented (Claude Code, Codex, Cursor, etc.) Also addresses #1571 reviewer findings: - BACKLOG.md regenerated via `BACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.ts` (was hand-edited; now matches generator) - Cross-reference to memory/feedback_orchestrator_pre_commit_verify_branch_rule_*.md resolves cleanly after rebase on main (file was merged via #1568) - tools/git-hooks/ reference removed (no longer the design) Composes_with extended to include the harness-hooks-suffice rule and B-0017 bulk-alignment UI (Aaron's note that the original inconsistency would have been caught by the planned bulk-review mechanism). Aaron 2026-05-05 verbatim: "it fine it's something we would have caught in the bulk alignment UI on the backlog" -- so the manual fix here is bonus, not required; the systematic answer is B-0017. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(B-0191): markdownlint MD032 — blank line before list at line 93 Per markdownlint MD032/blanks-around-lists. CI ran on #1571's revised commit; flagged a missing blank line between "Implementation: a ..." paragraph and the list item that follows. Trivial fix. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(B-0191): bump last_updated to 2026-05-05 (#1571 reviewer feedback) Reviewer flagged that the row's last_updated stays at 2026-05-04 even though the latest revision (harness-hooks switch + symlink removal) was committed 2026-05-05. tools/backlog/README.md schema says last_updated should reflect the most recent content edit. created: 2026-05-04 unchanged (first-landing date per schema). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(B-0191): soften bun-runtime claim; update Why-P1 line-count to TS (#1571 reviewer feedback) Two reviewer findings: 1. "harnesses always provide the bun runtime" was wrong -- only Claude Code does; Codex / Cursor / Aider commonly have Node or Deno. Softened to: harness-runtime-may-vary; the script should use a runner-agnostic shebang or be invoked via the harness's available TS runtime; per-harness runtime audit is part of the implementation when this row ships. 2. Why-P1 said "pre-commit hook is ~50 lines of shell" but the revised section 1 design is TS, not shell. Updated to "harness pre-tool-use hook is ~30 lines of TypeScript." The third reviewer thread (last_updated stale at 2026-05-04) was based on a pre-rebase snapshot; the file already shows last_updated: 2026-05-05 from commit 6186503. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 5, 2026
…tion cleanup (#1584) Five PRs landed in the 45min window since 04:00Z: #1571 B-0191 revised (harness-hooks not git-hooks) #1580 3 May 2026 orphan feedback files indexed #1581 CLAUDE.md razor-cadence wake-time pointer #1582 falsifiability-catch + BP EP kernel + MDL two-part code #1583 B-0006 tier-49 (36 entries compressed) Load-bearing item is Aaron's forwarded Claude.ai diagnosis catching the Pascal's-wager-inverted-into-engineering unfalsifiable bundling pattern in PR #1574. The architectural answer (BP EP kernel + MDL two-part code) and the recalibration sequence (memory unfiltered, audit at promotion boundary) preserved verbatim in PR #1582. The dialectical-unfalsifiability razor extension (PR #1577) gets its first worked-example validation here -- Test 2 was filed in anticipation of the failure mode, the failure mode fired hours later, the diagnosis landed. 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
Speculative work this autonomous-loop tick: orphan-detection scan surfaced 3 May 2026 feedback files that exist as substrate but are not indexed in MEMORY.md.
Indexed entries
feedback_dst_justifies_ts_quality_over_bash_and_harness_hooks_suffice_no_git_hooks_aaron_2026_05_03.md-- DST is the architectural justification for TS-over-bash; harness hooks suffice for skill-bundle distribution.feedback_skill_bundle_compounding_empirical_hardening_into_diamond_aaron_2026_05_03.md-- Long-arc vision: multiple skill bundles compound multiplicatively; empirical hardening = diamond.feedback_substrate_quality_is_lidar_not_autopilot_perception_layer_for_future_otto_aaron_2026_05_03.md-- Substrate-quality is lidar (perception layer), not autopilot. Agent still drives.Larger orphan-count finding
The scan also surfaced ~419 memory files that exist as substrate but are not indexed in MEMORY.md. The file is at 470 lines, cap is ~200, so the mathematical conflict is structural at the current entry-per-file granularity.
This PR addresses the recent (May 2026) orphans only. The structural fix is the B-0006 cluster-folding cadence (deferred to dedicated tier passes). Filing as observation here for visibility.
Test plan
🤖 Generated with Claude Code