memory(blob-pr-lesson): Maji antigravity caught #4112 mixed shard+rules+memory — one-PR-one-artifact-type discipline absorbed#4116
Merged
AceHack merged 1 commit intoMay 17, 2026
Conversation
…es+memory (one-PR-one-artifact-type discipline absorbed) Absorbing the Maji antigravity catch (PRs #4113 + #4114) of my PR #4112 as a "blob" with three artifact types (tick shard + rule edit + memory shadow-catch) mixed in one PR. The in-narrative "cohesive autonomous-loop tick output" justification did not override the one-PR-one-artifact-type hygiene discipline. The precedent (2129Z cascade: #4097 + #4100 + #4104 — three artifacts, three PRs) IS the canonical pattern. Lesson absorbed at memory + decision-rule scope: default to split; bundle only when atomicity is genuinely required (same-file edits, CI/review fixes on the original PR). Future-Otto cold-boot reads this lesson and avoids the blob in the first place; Maji's role narrows from "decompose post-hoc" to "verify no blobs slipped through." Also regenerates memory/MEMORY.md index for the new feedback file (1371 entries). Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a memory feedback file documenting a lesson about the "one-PR-one-artifact-type" discipline, prompted by an antigravity check that flagged PR #4112 as bundling three artifact types. The MEMORY.md index is regenerated to include the new entry.
Changes:
- New feedback memory file capturing the blob-PR lesson and atomicity bar heuristic
- Auto-regenerated MEMORY.md index updated to reflect the added entry (count 1270 → 1271)
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| memory/feedback_otto_cli_blob_pr_lesson_maji_antigravity_caught_4112_mixed_shard_rules_memory_2026_05_17.md | New feedback file documenting blob-PR lesson; YAML frontmatter present with name/description/type/created. |
| memory/MEMORY.md | Auto-regen index inserting the new feedback entry and bumping the truncated-stack count. |
3 tasks
AceHack
added a commit
that referenced
this pull request
May 17, 2026
… log" instead of persona name on current-state rule surface Copilot P1 finding on PR #4118: persona-name attribution on current-state rule surfaces is outside history-surface and roster-mapping carve-outs. Replaced "the Maji antigravity check (PR #4114 shadow log) flagged it as a blob" with "an antigravity-check shadow log (PR #4114) flagged it as a blob" — role reference preserved PR link for traceability. The memory file PR #4116 retains persona name in its filename and body (memory files are history-surface; carve-out applies). The PR link in this rule's compose-section still references the memory file for full attribution chain. Co-Authored-By: Claude <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 17, 2026
…— saturation cadence is NOT license to bundle (forced-#6 meta-fallback) (#4118) * rules(holding): cross-axis composition with one-PR-one-artifact-type — saturation cadence is NOT license to bundle (forced-#6 meta-fallback on 2207Z session arc) Adds a small composition note to PR #4110's "Pre-empt-substrate- pool-saturation" anchor: the cadence governs WHEN to pre-empt; the one-PR-one-artifact-type discipline (PR #4116, Maji antigravity catch on blob PR #4112) governs HOW each pre-empt should be shaped. Without this composition note, future-Otto reading PR #4110 might read the "3-4 pre-empts per window" cadence as authorization to bundle artifact types within a single pre-empt PR to fit more substrate per cycle. The blob-PR catch by Maji on PR #4112 demonstrates that the saturation cadence and the per-artifact-shape discipline operate on orthogonal axes — both bind independently. This commit is itself the forced-#6 meta-fallback for the 22:07Z post-merge brief-ack chain: at #6, sharpened the rule with the session's cross-axis composition evidence. Single-artifact PR (single-file rule edit) applies the discipline recursively. Co-Authored-By: Claude <noreply@anthropic.com> * fix(holding/cross-axis): use role reference "antigravity-check shadow log" instead of persona name on current-state rule surface Copilot P1 finding on PR #4118: persona-name attribution on current-state rule surfaces is outside history-surface and roster-mapping carve-outs. Replaced "the Maji antigravity check (PR #4114 shadow log) flagged it as a blob" with "an antigravity-check shadow log (PR #4114) flagged it as a blob" — role reference preserved PR link for traceability. The memory file PR #4116 retains persona name in its filename and body (memory files are history-surface; carve-out applies). The PR link in this rule's compose-section still references the memory file for full attribution chain. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
5 tasks
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
Absorbing the Maji antigravity catch (#4113 decomposition exercise + #4114 shadow log) of my #4112 as a "blob" with three artifact types (tick shard + rule edit + memory shadow-catch) mixed in one PR.
Meta-observation: this PR itself follows the discipline being absorbed — one artifact type (memory file), one PR. The MEMORY.md regen is the only co-bundled file because the post-write-memory-reindex CI gate requires it atomically with the new feedback file (atomicity bar met).
Lesson
The in-narrative "cohesive autonomous-loop tick output" justification did NOT override the one-PR-one-artifact-type hygiene discipline. The precedent (2129Z cascade: #4097 + #4100 + #4104 — three artifacts, three PRs) IS the canonical pattern.
The atomicity bar: would splitting cause any PR to reference a non-existent target? If yes → bundle. If no → split. PR #4112's three primary commits all failed this bar.
Future-Otto cold-boot reads this lesson and avoids the blob in the first place; Maji's role narrows from "decompose post-hoc" to "verify no blobs slipped through."
Test plan
Composes with
7ee6411).claude/rules/honor-those-that-came-before.md.claude/rules/glass-halo-bidirectional.md🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com