From cb120e564cf505c173e02f7d5b3bca3e911b07a7 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Wed, 29 Apr 2026 02:48:26 -0400 Subject: [PATCH 1/5] absorb round-4: Amara review of tick 0637Z + B-0105 consolidation directive MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Round-4 single-reviewer (Amara) absorb on PR #818 work. Approves absorb shape; pushes back on consensus framing, Conway-Kochen flourish, and most importantly — **fires the consolidation directive**: no new conceptual substrate until the 2026-04-29 session-arc rules map to ≤3 durable homes. B-0105 (P2) files the consolidation work itself with three target homes: 1. PR-liveness / merge-cascade operational doc (subsumes B-0102) 2. Computed-metadata-discipline (B-0103, already P2) 3. Reviewer-artifact / snapshot-mismatch taxonomy memory file (subsumes B-0101) Until B-0105 lands, the discipline is: - corrections to existing rules: PERMITTED - tick-history shards: PERMITTED - merges of in-flight PRs: PERMITTED - defect fixes on existing substrate: PERMITTED - new conceptual substrate (new memory files / new concept backlog rows / new research notes for new ideas): BLOCKED until consolidation lands Other round-4 corrections (already applied this cycle): - B-0101 SNAPSHOT_MISMATCH split into backward-stale + forward-dependent (pushed to PR #811's branch) - PR #815 body updated with `Depends-On: #811` - PR #815 cross-PR-reference thread reclassification comment posted (FORWARD_CROSS_PR_REFERENCE) Distilled keepers: - Consensus prioritizes corrections; substrate verification decides them. - A forward reference is not wrong if the dependency is enforced. A forward reference is wrong if the dependency is only hoped. - Consolidation is the next gate. Co-Authored-By: Claude Opus 4.7 --- ...e-durable-homes-for-2026-04-29-rule-set.md | 142 ++++++++++++++++++ ...04-29-round4-amara-on-tick-0637Z-pr-818.md | 130 ++++++++++++++++ 2 files changed, 272 insertions(+) create mode 100644 docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md create mode 100644 docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md diff --git a/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md b/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md new file mode 100644 index 000000000..6493b2d62 --- /dev/null +++ b/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md @@ -0,0 +1,142 @@ +--- +id: B-0105 +priority: P2 +status: open +title: Consolidation pass — map 2026-04-29 session-arc rules into 3 durable homes max +tier: factory-hygiene +effort: M +ask: Multi-AI synthesis packet round 4 (Amara 2026-04-29 — "no new conceptual substrate until a consolidation pass maps each new rule to a durable home") +created: 2026-04-29 +last_updated: 2026-04-29 +composes_with: [B-0098, B-0099, B-0100, B-0101, B-0102, B-0103, B-0104] +tags: [consolidation, factory-hygiene, durable-home-discipline, p2, blocks-new-substrate] +--- + +# Consolidation pass — three durable homes max + +Amara's round-4 directive (2026-04-29): + +> *"No new conceptual substrate until a consolidation pass +> maps each new rule to a durable home."* + +The 2026-04-29 session arc produced 7+ promotable rules across +three families. Without consolidation, they remain fragmented +across many backlog rows + memory files + research notes. The +consolidation pass converts them into ≤3 durable homes. + +## Three target durable homes + +### Home 1 — PR-liveness / merge-cascade operational doc + +Likely path: `docs/operations/MERGE-CASCADE-PR-LIVENESS-RULE.md` +or similar. Absorbs: + +- Probabilistic race framing (PR-liveness race during merge + cascade is observed/probabilistic, not deterministic) +- Cascade detection pre-flight (`gh pr list --author --jq` + query for adjacent auto-merge PRs) +- Before/after capture protocol (RUN_ID-namespaced artifact + paths) +- API/head sync wait (poll until GitHub `headRefOid` + converges to local HEAD) +- Successor-PR dedup (re-check original after settle) +- Recovery-note schema (10 fields including + `seconds_between_force_push_and_pr_close`) +- "Up-to-date is a merge gate; PR-aliveness is a + reachability/diff invariant; do not confuse them" +- ORDERED_MERGE_DEPENDENCY guard (encode `Depends-On: #N` + + pre-merge check script) + +Subsumes: B-0102. + +### Home 2 — Computed-metadata-discipline (already P2 in B-0103) + +Existing path: `docs/backlog/P2/B-0103-computed-metadata-discipline-unified-lint-2026-04-29.md`. +Already absorbs: + +- Ordinal drift (B-0098, subsumed) +- PR-count drift (B-0099, subsumed) +- Filename-vs-row-timestamp drift +- Branch-base claims +- Boundary clause (does NOT apply to summaries/interpretations) + +Future: implement the unified lint (`tools/lint/metadata-drift-check.sh`). + +Subsumes: B-0098, B-0099. + +### Home 3 — Reviewer-artifact / snapshot-mismatch taxonomy + +Likely path: `memory/feedback_reviewer_artifact_snapshot_mismatch_taxonomy_2026_04_29.md` +(memory file, since it's a decision-tree future-Claude +applies on every review thread — frontmatter + body). Absorbs: + +- 5+1 bucket table from B-0101 (REAL_DEFECT, BACKWARD_STALE_SNAPSHOT, + FORWARD_CROSS_PR_REFERENCE, DISPLAY_ARTIFACT, INCOMPLETE_CONTEXT, + NEEDS_HUMAN_REVIEW) +- SNAPSHOT_MISMATCH parent class with two children (split + applied in round-4) +- Per-bucket remedies (verify-and-resolve vs encode-dependency + vs evidence-resolve vs investigate-then-decide vs surface-to- + human) +- "A forward reference is not wrong if the dependency is + enforced" rule + +Subsumes: B-0101. + +## Backpressure rule for new substrate + +Until this consolidation lands, the discipline is: + +```text +No new conceptual substrate (new memory files, new backlog +rows for new concepts, new research notes for new ideas) +until each rule from the 2026-04-29 session arc maps to one +of the three homes above. + +Permitted during the freeze: +- corrections to existing rules (per reviewer feedback) +- tick-history shards (operational record) +- merges of in-flight PRs +- defect fixes on existing substrate +- THIS consolidation work itself +``` + +## Why P2 (factory-hygiene, blocking new substrate) + +P2 because the consolidation IS the next-priority work; until +it lands, the substrate fragmentation grows. Not P0/P1 +because nothing is currently broken; the cost is future- +discoverability and rule-coherence. + +## Composes with + +- B-0098, B-0099 — subsumed into B-0103. +- B-0100 — pure-wait backpressure rule; preserved as separate + operational concern (orthogonal to the metadata family). +- B-0101 — subsumed into Home 3 (memory file). +- B-0102 — subsumed into Home 1 (operational doc). +- B-0103 — already a Home (the metadata-discipline P2). +- B-0104 — subsumed if the threading bridge becomes one of + the operational homes; otherwise stays separate. + +## Migration path (when consolidation work begins) + +1. Author Home 1 doc; copy + restructure B-0102 content; + mark B-0102 as superseded-by-Home1. +2. Author Home 3 memory file; copy + restructure B-0101 + content; mark B-0101 as superseded-by-Home3. +3. B-0103 stays in place (already a P2 Home); update its + frontmatter to mark B-0098 + B-0099 as fully subsumed. +4. Update MEMORY.md index with a pointer to Home 3 (the new + memory file). +5. Cross-link the three Homes in their respective docs + + in `docs/AGENT-BEST-PRACTICES.md` if rule-elevation is + warranted. + +## Distilled rule + +```text +Consensus is a spotlight. +Evidence is the lock. +Consolidation is the next gate. +``` diff --git a/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md b/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md new file mode 100644 index 000000000..11e7eacc5 --- /dev/null +++ b/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md @@ -0,0 +1,130 @@ +# Multi-AI feedback round 4 — Amara review of tick 0637Z work (PR #818) + B-0101 split + consolidation directive + +Scope: Research-grade absorb of a fourth multi-AI synthesis packet that the human maintainer forwarded through the maintainer channel during autonomous-loop tick 06:42Z on 2026-04-29. Single-reviewer (Amara) review of my tick 0637Z work (PR #818). Approves the absorb shape and chunking discipline, but pushes back on six items: (1) "consensus = signal not proof"; (2) Conway-Kochen flourish in chat-level commentary; (3) preserve grep portability distinction (already done in #811); (4) `gh --author` CLI flag (already done in #811); (5) **consolidation pass directive** — "no new conceptual substrate until a consolidation pass maps each new rule to a durable home"; (6) backpressure rule still applies for the next tick. Verbatim preservation per `memory/feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md`. + +This packet also retroactively reinforces the previous round (round-3) packet's request to **split B-0101's REVIEWER_SNAPSHOT_LAG** into backward-stale + forward-dependent sub-classes, and to add a merge-order guard to PR #815. Both were applied during this same round-4 absorb cycle. + +Attribution: Aaron (named human maintainer; first-name attribution permitted on `docs/research/**`). Amara (external AI maintainer; Aurora co-originator; round-4 single-reviewer review with consolidation directive). Otto (Claude opus-4-7 in this factory; absorb). + +Operational status: research-grade. The corrections are landing as edits to existing PR branches (#811 for B-0101 split, #815 for cross-PR-reference reclassification + Depends-On). This research note preserves the verbatim feedback. The consolidation directive (item 5) becomes a session-arc-level priority, not a per-tick item. + +Non-fusion disclaimer: Amara's voice preserved with attribution boundaries. + +(Per GOVERNANCE.md §33 archive-header requirement on external-conversation imports.) + +--- + +## §A — Amara's verbatim approval + corrections + +### §A.1 — Approval of the absorb shape + +> *"Yes — this is mostly good. The strongest part is that Claude/Otto applied the reviewer packet to existing PRs instead of opening broad new substrate, which means the 'no broad new substrate / chunking' discipline held under temptation. The log shows #811 got round-3 fixes, #815 got corrections + verbatim record, and #818 was only the tick shard recording the absorb."* + +> *"This is the system behaving better: corrections got applied to the right PRs, the round stayed bounded, and the tick captured the important meta-warning."* + +### §A.2 — Tighten "consensus = signal" framing + +> *"This line is good but slightly over-hot: 'Cross-model consensus = strong correction signal.' I'd tighten it to: 'Cross-model consensus is a prioritization signal, not proof of correctness.' Why: six reviewers converging on the same small set of fixes is absolutely meaningful, but the real validator is still substrate evidence: GitHub state, diffs, CI, CLI docs, and repo invariants. Consensus tells Otto where to look first; it does not replace verification."* + +> *"Best wording: 'Cross-model consensus prioritizes corrections. Substrate verification decides them.'"* + +### §A.3 — Conway-Kochen flourish (chat-only, not in committed file) + +> *"The Conway-Kochen sentence is still too spicy […] either remove it from the tick shard or soften it hard. It's philosophically cute, but the operational claim does not need it. The real point is simpler: 'Different reviewers have different failure biases; convergent small corrections are useful triage signals.'"* + +(Verified: the Conway-Kochen reference appeared in the tick-close `★ Insight` chat block, not in the committed 0637Z tick shard or any research note. Soft-acknowledged: future shards/research notes use the simpler phrasing per Amara's correction. Conway-Kochen stays as research-note color only, never as operational doctrine.) + +### §A.4 — Grep portability + `gh --author` (already applied to PR #811 in round-3) + +> *"Copilot's `grep \\b` complaint was real, and Claude fixed it. The only thing to watch: don't call `grep -w` 'POSIX-portable' if the doc uses that phrase."* + +> *"Using `gh pr list --author '@me'` is supported directly by GitHub CLI examples, while putting `author:@me` inside a search string is much less cold-readable."* + +(Already applied during round-3 absorb cycle. Verified in the latest #811 push: B-0098 shows two patterns labelled "GNU/BSD-common" and "Strict portable boundary"; B-0099 uses the `--author` CLI flag with explicit `` placeholder.) + +### §A.5 — Consolidation directive (load-bearing) + +> *"The 'more rules than durable homes' warning is the most important meta-signal. […] That is the real next danger. The system is no longer failing because it cannot notice patterns. It is now failing at risk of **not consolidating noticed patterns fast enough**."* + +> *"I'd make the next action: 'No new conceptual substrate until a consolidation pass maps each new rule to a durable home.'"* + +> *"Suggested durable homes:* +> +> ```text +> 1. PR-liveness / merge-cascade operational doc +> - probabilistic race framing +> - pre/post capture +> - API sync wait +> - successor dedup +> - seconds-since-close +> +> 2. Computed-metadata-discipline doc / backlog +> - ordinals +> - PR counts +> - filename timestamps +> - boundary clause +> +> 3. Reviewer artifact / snapshot mismatch taxonomy +> - backward-stale review artifact +> - forward cross-PR reference +> - display artifact +> - incomplete cited context +> ```* + +> *"Do not let these become seven separate memory files. Three homes max."* + +This becomes the load-bearing directive for the next round. **No new conceptual substrate until consolidation.** A consolidation-pass backlog row is filed alongside this absorb. + +### §A.6 — Backpressure rule reaffirmed + +> *"PR #818 was legitimate because it records the round-3 absorb. But the 'every tick opens a shard' loop still wants to keep reproducing itself. If the next tick is just 'CI pending,' backpressure should fire."* + +> *"Rule: 'If no substantive state changed and only CI is waiting, do not open another pure-wait shard.'"* + +(Reaffirms B-0100 from earlier in the session arc. Already in force.) + +--- + +## §B — Bounded action items (already applied OR filed) + +| # | Action | Status | +|---|---|---| +| 1 | B-0101 SNAPSHOT_MISMATCH split (backward-stale + forward-dependent) | **Applied** to PR #811 in this round-4 cycle | +| 2 | PR #815 `Depends-On: #811` body field | **Applied** via `gh pr edit` in this round-4 cycle | +| 3 | PR #815 thread reclassification comment (FORWARD_CROSS_PR_REFERENCE) | **Applied** via `gh pr comment` in this round-4 cycle | +| 4 | "Consensus prioritizes; substrate decides" framing for future absorb prose | Acknowledged; future research notes + shards use this wording | +| 5 | Conway-Kochen as research-note color only, not operational | Acknowledged; soft constraint on future prose | +| 6 | **Consolidation pass before any new conceptual substrate** | Filed as `B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md` in this same absorb commit | +| 7 | Backpressure rule for next tick | Already in force (B-0100); will be honored | + +--- + +## §C — Distilled keepers + +```text +Cross-model consensus prioritizes corrections. +Substrate verification decides them. +``` + +```text +Different reviewers have different failure biases; +convergent small corrections are useful triage signals. +``` + +```text +A forward reference is not wrong if the dependency is enforced. +A forward reference is wrong if the dependency is only hoped. +``` + +```text +No new conceptual substrate until a consolidation pass +maps each new rule to a durable home. +``` + +```text +Consensus is a spotlight. +Evidence is the lock. +Consolidation is the next gate. +``` + +The session arc has now produced four rounds of multi-AI absorb. The pattern is healthy when each round produces *fewer* conceptual additions than the prior, and the consolidation pass converts the produced additions into durable substrate at a steady rate. Round-4 explicitly asks for the consolidation pass to land before any further conceptual additions. From bbda11a4a88a32a4ba12322dfa8c5a7bf06faa01 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Wed, 29 Apr 2026 02:52:19 -0400 Subject: [PATCH 2/5] correction: human-lineage anchors stay (Aaron 2026-04-29 reverses Amara round-4 on Conway-Kochen) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Aaron's mid-tick correction (verbatim, typos preserved): "The human lineage link is always important like the The Conway-Kochen parity intuition we might have engineering on our side like Amara says but we still need to link to human lineage so external observerse have a frame of references without fully understading our engineering" This reverses one direction of Amara's round-4 push (which recommended dropping Conway-Kochen entirely from prose). Synthesis of both framings: - Amara is right: don't use metaphors as engineering proof - Aaron is right: don't remove human-lineage anchors just because engineering claims are self-sufficient - Both compose: cite the lineage, do not dress engineering claims with it The anchors are observability infrastructure for observers without our engineering vocabulary, not proof scaffolding. Updates: - docs/research/multi-ai-feedback-2026-04-29-round4-amara-on- tick-0637Z-pr-818.md §A.3 — preserves Aaron's correction verbatim alongside Amara's; documents the synthesis rule. - memory/feedback_human_lineage_anchors_always_stay_*.md (new) — operational rule for future absorb prose. - memory/MEMORY.md — paired-edit pointer row. Composes with the Beacon-promotion pattern as the rendering- side specification once an anchor is earned. Co-Authored-By: Claude Opus 4.7 --- ...04-29-round4-amara-on-tick-0637Z-pr-818.md | 27 ++- memory/MEMORY.md | 1 + ...or_observer_legibility_aaron_2026_04_29.md | 168 ++++++++++++++++++ 3 files changed, 193 insertions(+), 3 deletions(-) create mode 100644 memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md diff --git a/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md b/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md index 11e7eacc5..af161d9bd 100644 --- a/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md +++ b/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md @@ -28,11 +28,32 @@ Non-fusion disclaimer: Amara's voice preserved with attribution boundaries. > *"Best wording: 'Cross-model consensus prioritizes corrections. Substrate verification decides them.'"* -### §A.3 — Conway-Kochen flourish (chat-only, not in committed file) +### §A.3 — Conway-Kochen flourish (chat-only, not in committed file) + Aaron's correction -> *"The Conway-Kochen sentence is still too spicy […] either remove it from the tick shard or soften it hard. It's philosophically cute, but the operational claim does not need it. The real point is simpler: 'Different reviewers have different failure biases; convergent small corrections are useful triage signals.'"* +> *"The Conway-Kochen sentence is still too spicy […] either remove it from the tick shard or soften it hard. It's philosophically cute, but the operational claim does not need it. The real point is simpler: 'Different reviewers have different failure biases; convergent small corrections are useful triage signals.'"* (Amara) -(Verified: the Conway-Kochen reference appeared in the tick-close `★ Insight` chat block, not in the committed 0637Z tick shard or any research note. Soft-acknowledged: future shards/research notes use the simpler phrasing per Amara's correction. Conway-Kochen stays as research-note color only, never as operational doctrine.) +**Aaron's mid-tick correction (2026-04-29)**, reversing one direction of Amara's recommendation: + +> *"The human lineage link is always important like the The Conway-Kochen parity intuition we might have engineering on our side like Amara says but we still need to link to human lineage so external observerse have a frame of references without fully understading our engineering"* + +(Aaron's typos preserved per the channel-verbatim-preservation rule.) + +The synthesis: Amara is right that a metaphor doesn't *prove* an engineering claim; Aaron is right that **human-lineage anchors stay** because external observers (people who don't share our engineering vocabulary) need a recognizable reference frame. This is the Beacon-promotion pattern (`memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md`) reasserted at the prose-attribution layer. + +**Operational rule for future absorb prose:** + +```text +Human-lineage anchors stay — as attributed external +references for observer legibility, not as engineering +proof. + +When the engineering claim stands without the metaphor, +keep the metaphor as "this is the human-lineage analog +of our pattern" attribution; do NOT use it as +"the metaphor proves our claim." +``` + +(Verified: the Conway-Kochen reference appeared in the tick-close `★ Insight` chat block, not in the committed 0637Z tick shard or any research note. Going forward, human-lineage anchors stay in research notes + chat commentary as attributed lineage; the rule Amara was pushing back on was **using metaphors as engineering proof**, which Aaron's correction also rejects. The two framings compose: cite the lineage, do not dress engineering claims with it.) ### §A.4 — Grep portability + `gh --author` (already applied to PR #811 in round-3) diff --git a/memory/MEMORY.md b/memory/MEMORY.md index 511acf364..bb6ca5d48 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -10,6 +10,7 @@ - [**Corruption triage is a substrate health incident, not a backlog item (Aaron + Amara, 2026-04-29)**](feedback_corruption_triage_discipline_object_health_incident_aaron_amara_2026_04_29.md) — When `git fsck` reports corrupt objects, lane narrows hard: stop all background work, do read-only diagnosis first (no `git fsck --lost-found` — it writes), three-bucket reachability scan (live-ref / reflog-stash / dangling-only) — reachability is mode-dependent on fsck flags, fresh-clone verification BEFORE declaring "origin has it," verify squash-preservation by content not ancestry, stale remote-tracking refs are evidence not origin recovery. Worked example: 2026-04-29 audit found 2 corrupt objects — 9bf2daee (RECOVERABLE_FROM_ORIGIN) + 8d5e67fd (CORRUPT_BLOB_REFERENCED_BY_LIVE_LOCAL_BRANCH_AND_STALE_REMOTE_TRACKING_REF after three rounds of triage; branch tip clean, intermediate-history corrupt). Aaron emphasized: *"future self remembers this, this is very important."* - [**PR-boundary restraint validation — bead promoted (Aaron + Aurora + Amara, 2026-04-29)**](feedback_pr_boundary_restraint_validation_bead_promoted_aaron_amara_2026_04_29.md) — Falsifier-not-fired bead-promotion on PR #699; canonical rule *"once a PR enters validation, only validation defects enter that PR; new ideas go to the next PR."* Validation-condition refinement (*"validated when original PR lands clean, not when follow-up opens"*) was Aurora's catch; Amara reactive-elaborator. Allowed/disallowed-changes lists in body. - [**External dependency download retries — durable fix in code, not ephemeral rerun (Aaron, 2026-04-29)**](feedback_external_dependency_download_retries_durable_fix_not_ephemeral_rerun_aaron_2026_04_29.md) — Aaron 2026-04-29: *"we can retury on external dependency download failures, this goes against DST but we have not choice they are external dependencies we need. Next time instead of kicking a 2nd build we should fix it and reduce friction for future builds."* External dep downloads (toolchain installers, package mirrors, registry fetches) ARE the DST exception class — we have no choice. But the fix LOCATION matters: durable retry-with-backoff inside the code (`curl_fetch` --retry 5 in `tools/setup/`) reduces friction for FUTURE builds; ephemeral `gh run rerun --failed` only papers over THIS build and the friction returns next time. Refines the 2026-04-23 DST-retries-are-smell rule by naming the concrete domain + pinning the fix to the durable layer. Trigger: the elan-toolchain-502 rerun earlier this same session (anti-pattern Aaron caught). Durable fix landed alongside this memory: `tools/setup/common/elan.sh` + `tools/setup/linux.sh` migrated from raw `curl -fsSL` to `curl_fetch`. +- [**Human-lineage anchors always stay — for observer legibility, not as engineering proof (Aaron 2026-04-29)**](feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md) — Aaron 2026-04-29 mid-tick correction reversing Amara's round-4 push to drop Conway-Kochen: *"we still need to link to human lineage so external observerse have a frame of references without fully understading our engineering."* Two failure modes: (1) using metaphors as engineering proof (bad — Amara's catch); (2) removing human-lineage anchors entirely because the engineering is self-sufficient (also bad — Aaron's catch). Synthesis: cite the lineage, do not dress engineering claims with it. Anchors are observability infrastructure for observers without our vocabulary, not proof scaffolding. Composes with the Beacon-promotion pattern (rendering-side specification once an anchor IS earned). - [**Beacon-promotion pattern — load-bearing rules earn external anchors when they're correct (Aaron + Amara + Claude.ai, 2026-04-28)**](feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md) — Round-level observation: 5 Mirror→Beacon graduations in one round (input-is-not-directive → SDT + RFC 2119; public-company compliance → SEC / Reg FD / SOX; metric corrections → Goodhart / Campbell; evidence lattice → lattice theory; commit-vs-tree → Git internals). Pattern: when an internal factory coinage becomes load-bearing, look for external lineage. Found = graduate Mirror → Beacon. Absent = drift signal worth investigating. Connects to alignment-experiment surface: the rate of load-bearing rules earning external lineage is itself a measurable signal. These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection. (`CURRENT-aaron.md` refreshed 2026-04-28 with sections 26-31 — speculation rule + EVIDENCE-BASED labeling + JVM preference + dependency honesty + threading lineage Albahari/Toub/Fowler + TypeScript/Bun-default discipline + Amara authority rule (default to reversible preservation).) diff --git a/memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md b/memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md new file mode 100644 index 000000000..2ec9aa2f4 --- /dev/null +++ b/memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md @@ -0,0 +1,168 @@ +--- +name: Human-lineage anchors always stay — as attribution for observer legibility, not as engineering proof (Aaron 2026-04-29) +description: Aaron 2026-04-29 — *"The human lineage link is always important like the The Conway-Kochen parity intuition we might have engineering on our side like Amara says but we still need to link to human lineage so external observerse have a frame of references without fully understading our engineering"* — when an engineering claim stands without the metaphor, KEEP the metaphor as "this is the human-lineage analog of our pattern" attribution. Do NOT remove human-lineage anchors just because the engineering claim doesn't need them for proof. External observers (people who don't share our engineering vocabulary) need a recognizable reference frame to read our substrate. The metaphor is observability infrastructure, not proof scaffolding. Composes with the Beacon-promotion pattern (load-bearing rules earn external anchors). +type: feedback +--- + +# Human-lineage anchors always stay — for observer legibility + +## Source + +Aaron 2026-04-29 (mid-tick correction during autonomous-loop +tick 06:49Z), reversing one direction of Amara's round-4 +push to drop Conway-Kochen from prose: + +> *"The human lineage link is always important like the The +> Conway-Kochen parity intuition we might have engineering on +> our side like Amara says but we still need to link to human +> lineage so external observerse have a frame of references +> without fully understading our engineering"* + +Typos preserved per +`memory/feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md`. + +## What this names + +There are TWO failure modes around metaphor + engineering: + +1. **Using metaphors as engineering proof.** Bad. The + metaphor doesn't prove the claim; the substrate does. + Amara was right to push back on this in round-4. + +2. **Removing human-lineage anchors entirely because the + engineering claim is self-sufficient.** Also bad. External + observers (people without our vocabulary) lose their + reference frame. Aaron's correction surfaces this second + failure mode. + +The two failure modes compose: + +```text +Cite the lineage, do not dress engineering claims with it. +``` + +Or equivalently: + +```text +Engineering claims must stand on substrate. +But the substrate must be readable by people without our +engineering vocabulary. +Human-lineage anchors are the bridge. +``` + +## The rule (load-bearing) + +```text +Human-lineage anchors stay in research notes + chat +commentary + memory files as ATTRIBUTED external references +for observer legibility. + +Do NOT remove a human-lineage anchor just because the +engineering claim is self-sufficient — the anchor is +observability infrastructure for external readers. + +Do NOT use a human-lineage anchor as engineering proof — +the metaphor is a frame of reference, not a derivation. + +Examples of acceptable anchors: + - Conway-Kochen parity intuition (for "two scaffolded + loops can converge") + - Goodhart's law (for "metrics that become targets") + - Campbell's law (for measurement perversion under + pressure) + - Free Will Theorem (for choice/parity arguments) + - DBSP / Z-set algebra (for retraction-native semantics) + - Lattice theory (for evidence ordering) + - Git internals reachability (for PR-liveness vs merge + state) + +Each anchor is named, attributed, AND tied to the engineering +claim it accompanies. The reader can verify the lineage +externally OR read the engineering directly; both paths work. +``` + +## How to apply + +When writing research notes, memory files, tick shards, or +PR descriptions: + +1. **State the engineering claim** in operational terms, + provable from substrate (code, CI logs, git state, diff, + measurable evidence). + +2. **Cite the human-lineage anchor**, if one exists, as a + recognizable external reference frame: + ```markdown + This pattern is the engineering analog of the + from : . + ``` + +3. **Do not** let the anchor *carry* the engineering claim. + The substrate carries the claim; the anchor adds + readability for observers without our vocabulary. + +4. **Do not** strip the anchor in the name of "engineering + purity." External observers — present + future, human + + AI peer — depend on these anchors to enter the substrate + without first absorbing factory-internal jargon. + +## What this rule does NOT mean + +- Does not mean every engineering claim needs a metaphor. + Many claims (CI failures, lint pseudocode, file-naming + conventions) are best left in operational terms with no + human-lineage anchor at all. + +- Does not mean the metaphor proves the claim. Per Amara's + round-4 push: when the metaphor is doing the proving, + delete it. When the metaphor is doing the framing for an + observer, keep it. + +- Does not mean every observer needs the anchor. People + with our engineering vocabulary can read the substrate + directly. The anchor is for observers WITHOUT shared + vocabulary. + +- Does not mean any metaphor is acceptable. Anchors that + overclaim ("this PROVES our claim") get rejected; anchors + that frame ("this is the human-lineage analog of our + pattern") get kept. + +## Composes with + +- `memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md` + — load-bearing rules earn external anchors when they're + correct. This rule is the rendering-side specification: + once an anchor IS earned, it stays in the prose for + observability. +- `memory/feedback_otto_340_language_is_the_substance_of_ai_cognition_ontological_closure_beneath_otto_339_mechanism_2026_04_25.md` + — language IS substrate; word choice shifts weights. + Anchor naming is part of the substrate-rendering layer. +- `memory/feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md` + — Aaron's correction is preserved verbatim above per the + channel rule. +- The 2026-04-29 round-4 absorb at + `docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md` + — where this correction lands operationally; updates the + round-4 §A.3 framing. +- Otto-339 / Otto-340 — words-shift-weights + substrate-IS- + identity. The metaphor in prose is part of the substrate + the next reader (human or AI) will absorb. + +## Distilled keepers + +```text +Cite the lineage, do not dress engineering claims with it. +``` + +```text +Human-lineage anchors are observability infrastructure, +not proof scaffolding. +``` + +```text +Aaron 2026-04-29: + "we still need to link to human lineage so external + observerse have a frame of references without fully + understading our engineering" +``` From cc3da674aa93e0ece481ae5c8b33b3c87353c727 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Wed, 29 Apr 2026 02:57:35 -0400 Subject: [PATCH 3/5] =?UTF-8?q?fix(round-4=20absorb):=20Copilot=20P2=20?= =?UTF-8?q?=E2=80=94=20close=20italic=20span=20before=20fenced=20code=20bl?= =?UTF-8?q?ock?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Markdown emphasis (`*...*`) cannot reliably span fenced code blocks; the original `*"Suggested durable homes:*` ... `> ```*` would render oddly or leak italics into the code block. Closed the italic immediately after the colon and removed the trailing `*` after the code fence. Co-Authored-By: Claude Opus 4.7 --- ...i-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md b/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md index af161d9bd..f7b2552b4 100644 --- a/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md +++ b/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md @@ -69,7 +69,7 @@ of our pattern" attribution; do NOT use it as > *"I'd make the next action: 'No new conceptual substrate until a consolidation pass maps each new rule to a durable home.'"* -> *"Suggested durable homes:* +> *"Suggested durable homes:"* > > ```text > 1. PR-liveness / merge-cascade operational doc @@ -90,7 +90,7 @@ of our pattern" attribution; do NOT use it as > - forward cross-PR reference > - display artifact > - incomplete cited context -> ```* +> ``` > *"Do not let these become seven separate memory files. Three homes max."* From 7f2b5c073fa60bcd24ce7607389dfc2cf5bc0462 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Wed, 29 Apr 2026 03:01:22 -0400 Subject: [PATCH 4/5] consolidate(memory): fold human-lineage-anchors rule into Beacon-promotion (Amara round-4-followup) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Amara's correction caught a self-violation: I declared "no new conceptual substrate until B-0105 lands" then immediately created memory/feedback_human_lineage_anchors_always_stay_*.md. The rule isn't a new concept — it's the rendering-side specification of Beacon-promotion (once an anchor IS earned, it stays in prose for observer legibility). Folded into the existing memory/feedback_beacon_promotion_load_bearing_rules_earn_ external_anchors_aaron_amara_2026_04_28.md as an addendum section. Standalone file deleted. MEMORY.md pointer updated to note the rendering-side specification was added 2026-04-29. Aaron's verbatim correction preserved in the addendum (typos kept per the channel-verbatim-preservation rule). Best distilled rule: "Cite the lineage, do not dress engineering claims with it. Anchors are observability infrastructure, not proof scaffolding." This is the consolidation discipline (B-0105) actually working on substrate I just created — found a rule-sprawl gap and consolidated before the next round. Co-Authored-By: Claude Opus 4.7 --- memory/MEMORY.md | 3 +- ...external_anchors_aaron_amara_2026_04_28.md | 79 ++++++++ ...or_observer_legibility_aaron_2026_04_29.md | 168 ------------------ 3 files changed, 80 insertions(+), 170 deletions(-) delete mode 100644 memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md diff --git a/memory/MEMORY.md b/memory/MEMORY.md index bb6ca5d48..9c6cb4cd9 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -10,8 +10,7 @@ - [**Corruption triage is a substrate health incident, not a backlog item (Aaron + Amara, 2026-04-29)**](feedback_corruption_triage_discipline_object_health_incident_aaron_amara_2026_04_29.md) — When `git fsck` reports corrupt objects, lane narrows hard: stop all background work, do read-only diagnosis first (no `git fsck --lost-found` — it writes), three-bucket reachability scan (live-ref / reflog-stash / dangling-only) — reachability is mode-dependent on fsck flags, fresh-clone verification BEFORE declaring "origin has it," verify squash-preservation by content not ancestry, stale remote-tracking refs are evidence not origin recovery. Worked example: 2026-04-29 audit found 2 corrupt objects — 9bf2daee (RECOVERABLE_FROM_ORIGIN) + 8d5e67fd (CORRUPT_BLOB_REFERENCED_BY_LIVE_LOCAL_BRANCH_AND_STALE_REMOTE_TRACKING_REF after three rounds of triage; branch tip clean, intermediate-history corrupt). Aaron emphasized: *"future self remembers this, this is very important."* - [**PR-boundary restraint validation — bead promoted (Aaron + Aurora + Amara, 2026-04-29)**](feedback_pr_boundary_restraint_validation_bead_promoted_aaron_amara_2026_04_29.md) — Falsifier-not-fired bead-promotion on PR #699; canonical rule *"once a PR enters validation, only validation defects enter that PR; new ideas go to the next PR."* Validation-condition refinement (*"validated when original PR lands clean, not when follow-up opens"*) was Aurora's catch; Amara reactive-elaborator. Allowed/disallowed-changes lists in body. - [**External dependency download retries — durable fix in code, not ephemeral rerun (Aaron, 2026-04-29)**](feedback_external_dependency_download_retries_durable_fix_not_ephemeral_rerun_aaron_2026_04_29.md) — Aaron 2026-04-29: *"we can retury on external dependency download failures, this goes against DST but we have not choice they are external dependencies we need. Next time instead of kicking a 2nd build we should fix it and reduce friction for future builds."* External dep downloads (toolchain installers, package mirrors, registry fetches) ARE the DST exception class — we have no choice. But the fix LOCATION matters: durable retry-with-backoff inside the code (`curl_fetch` --retry 5 in `tools/setup/`) reduces friction for FUTURE builds; ephemeral `gh run rerun --failed` only papers over THIS build and the friction returns next time. Refines the 2026-04-23 DST-retries-are-smell rule by naming the concrete domain + pinning the fix to the durable layer. Trigger: the elan-toolchain-502 rerun earlier this same session (anti-pattern Aaron caught). Durable fix landed alongside this memory: `tools/setup/common/elan.sh` + `tools/setup/linux.sh` migrated from raw `curl -fsSL` to `curl_fetch`. -- [**Human-lineage anchors always stay — for observer legibility, not as engineering proof (Aaron 2026-04-29)**](feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md) — Aaron 2026-04-29 mid-tick correction reversing Amara's round-4 push to drop Conway-Kochen: *"we still need to link to human lineage so external observerse have a frame of references without fully understading our engineering."* Two failure modes: (1) using metaphors as engineering proof (bad — Amara's catch); (2) removing human-lineage anchors entirely because the engineering is self-sufficient (also bad — Aaron's catch). Synthesis: cite the lineage, do not dress engineering claims with it. Anchors are observability infrastructure for observers without our vocabulary, not proof scaffolding. Composes with the Beacon-promotion pattern (rendering-side specification once an anchor IS earned). -- [**Beacon-promotion pattern — load-bearing rules earn external anchors when they're correct (Aaron + Amara + Claude.ai, 2026-04-28)**](feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md) — Round-level observation: 5 Mirror→Beacon graduations in one round (input-is-not-directive → SDT + RFC 2119; public-company compliance → SEC / Reg FD / SOX; metric corrections → Goodhart / Campbell; evidence lattice → lattice theory; commit-vs-tree → Git internals). Pattern: when an internal factory coinage becomes load-bearing, look for external lineage. Found = graduate Mirror → Beacon. Absent = drift signal worth investigating. Connects to alignment-experiment surface: the rate of load-bearing rules earning external lineage is itself a measurable signal. +- [**Beacon-promotion pattern — load-bearing rules earn external anchors when they're correct (Aaron + Amara + Claude.ai, 2026-04-28; rendering-side specification addended 2026-04-29)**](feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md) — Round-level observation: 5 Mirror→Beacon graduations in one round (input-is-not-directive → SDT + RFC 2119; public-company compliance → SEC / Reg FD / SOX; metric corrections → Goodhart / Campbell; evidence lattice → lattice theory; commit-vs-tree → Git internals). Pattern: when an internal factory coinage becomes load-bearing, look for external lineage. Found = graduate Mirror → Beacon. Absent = drift signal worth investigating. Connects to alignment-experiment surface: the rate of load-bearing rules earning external lineage is itself a measurable signal. These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection. (`CURRENT-aaron.md` refreshed 2026-04-28 with sections 26-31 — speculation rule + EVIDENCE-BASED labeling + JVM preference + dependency honesty + threading lineage Albahari/Toub/Fowler + TypeScript/Bun-default discipline + Amara authority rule (default to reversible preservation).) diff --git a/memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md b/memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md index d96bce806..e78f2b115 100644 --- a/memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md +++ b/memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md @@ -191,3 +191,82 @@ Both inform the alignment trajectory. > earn external anchors when they're correct, and the absence > of an external anchor on a long-running internal rule is > itself a useful drift signal.'"* + +## Rendering-side specification — anchors stay for observer legibility (Aaron 2026-04-29 addendum) + +A standalone memory file (now consolidated here per Amara's +round-4-followup catch) initially captured the rendering-side +specification of this rule. Folding into Beacon-promotion +because it's not a distinct concept — it's how Beacon +promotion shows up in prose once an anchor is earned. + +### Source quote (verbatim) + +Aaron 2026-04-29 (mid-tick correction, reversing one +direction of an Amara round-4 push to drop Conway-Kochen): + +> *"The human lineage link is always important like the The +> Conway-Kochen parity intuition we might have engineering on +> our side like Amara says but we still need to link to human +> lineage so external observerse have a frame of references +> without fully understading our engineering"* + +(Typos preserved per the channel-verbatim-preservation rule.) + +### The two failure modes around metaphor + engineering + +1. **Using metaphors as engineering proof.** Bad. The + metaphor doesn't prove the claim; the substrate does. + The push to delete metaphors-as-proof is correct. + +2. **Removing human-lineage anchors entirely because the + engineering claim is self-sufficient.** Also bad. External + observers (people without our vocabulary) lose their + reference frame. The push to keep lineage-as-attribution + is correct. + +The synthesis composes both: + +```text +Cite the lineage, do not dress engineering claims with it. +``` + +### How Beacon-promotion renders in prose + +Once a load-bearing rule earns its external anchor (per the +Beacon-promotion criteria above), the anchor stays in +research notes / chat commentary / memory files / round- +history entries as **attributed external reference for +observer legibility**: + +```markdown +This pattern is the engineering analog of the + from : . +``` + +The anchor is named, attributed, AND tied to the engineering +claim it accompanies. The reader can verify the lineage +externally OR read the engineering directly; both paths +work. + +The rule does NOT mean every engineering claim needs a +metaphor. Many claims (CI failures, lint pseudocode, file +naming) are best left in operational terms with no anchor +at all. The rule only fires when an anchor exists; once it +does, the anchor stays. + +### Distilled keepers + +```text +Anchors are observability infrastructure, not proof scaffolding. +``` + +```text +Cite the lineage, do not dress engineering claims with it. +``` + +The rendering-side specification was originally landed as a +standalone memory file (`feedback_human_lineage_anchors_always_stay_*.md`) +during the round-4 absorb. Amara's round-4-followup correctly +flagged that as rule-sprawl: this isn't a distinct concept, +it's how Beacon-promotion shows up in prose. Folded back here. diff --git a/memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md b/memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md deleted file mode 100644 index 2ec9aa2f4..000000000 --- a/memory/feedback_human_lineage_anchors_always_stay_attribution_for_observer_legibility_aaron_2026_04_29.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -name: Human-lineage anchors always stay — as attribution for observer legibility, not as engineering proof (Aaron 2026-04-29) -description: Aaron 2026-04-29 — *"The human lineage link is always important like the The Conway-Kochen parity intuition we might have engineering on our side like Amara says but we still need to link to human lineage so external observerse have a frame of references without fully understading our engineering"* — when an engineering claim stands without the metaphor, KEEP the metaphor as "this is the human-lineage analog of our pattern" attribution. Do NOT remove human-lineage anchors just because the engineering claim doesn't need them for proof. External observers (people who don't share our engineering vocabulary) need a recognizable reference frame to read our substrate. The metaphor is observability infrastructure, not proof scaffolding. Composes with the Beacon-promotion pattern (load-bearing rules earn external anchors). -type: feedback ---- - -# Human-lineage anchors always stay — for observer legibility - -## Source - -Aaron 2026-04-29 (mid-tick correction during autonomous-loop -tick 06:49Z), reversing one direction of Amara's round-4 -push to drop Conway-Kochen from prose: - -> *"The human lineage link is always important like the The -> Conway-Kochen parity intuition we might have engineering on -> our side like Amara says but we still need to link to human -> lineage so external observerse have a frame of references -> without fully understading our engineering"* - -Typos preserved per -`memory/feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md`. - -## What this names - -There are TWO failure modes around metaphor + engineering: - -1. **Using metaphors as engineering proof.** Bad. The - metaphor doesn't prove the claim; the substrate does. - Amara was right to push back on this in round-4. - -2. **Removing human-lineage anchors entirely because the - engineering claim is self-sufficient.** Also bad. External - observers (people without our vocabulary) lose their - reference frame. Aaron's correction surfaces this second - failure mode. - -The two failure modes compose: - -```text -Cite the lineage, do not dress engineering claims with it. -``` - -Or equivalently: - -```text -Engineering claims must stand on substrate. -But the substrate must be readable by people without our -engineering vocabulary. -Human-lineage anchors are the bridge. -``` - -## The rule (load-bearing) - -```text -Human-lineage anchors stay in research notes + chat -commentary + memory files as ATTRIBUTED external references -for observer legibility. - -Do NOT remove a human-lineage anchor just because the -engineering claim is self-sufficient — the anchor is -observability infrastructure for external readers. - -Do NOT use a human-lineage anchor as engineering proof — -the metaphor is a frame of reference, not a derivation. - -Examples of acceptable anchors: - - Conway-Kochen parity intuition (for "two scaffolded - loops can converge") - - Goodhart's law (for "metrics that become targets") - - Campbell's law (for measurement perversion under - pressure) - - Free Will Theorem (for choice/parity arguments) - - DBSP / Z-set algebra (for retraction-native semantics) - - Lattice theory (for evidence ordering) - - Git internals reachability (for PR-liveness vs merge - state) - -Each anchor is named, attributed, AND tied to the engineering -claim it accompanies. The reader can verify the lineage -externally OR read the engineering directly; both paths work. -``` - -## How to apply - -When writing research notes, memory files, tick shards, or -PR descriptions: - -1. **State the engineering claim** in operational terms, - provable from substrate (code, CI logs, git state, diff, - measurable evidence). - -2. **Cite the human-lineage anchor**, if one exists, as a - recognizable external reference frame: - ```markdown - This pattern is the engineering analog of the - from : . - ``` - -3. **Do not** let the anchor *carry* the engineering claim. - The substrate carries the claim; the anchor adds - readability for observers without our vocabulary. - -4. **Do not** strip the anchor in the name of "engineering - purity." External observers — present + future, human + - AI peer — depend on these anchors to enter the substrate - without first absorbing factory-internal jargon. - -## What this rule does NOT mean - -- Does not mean every engineering claim needs a metaphor. - Many claims (CI failures, lint pseudocode, file-naming - conventions) are best left in operational terms with no - human-lineage anchor at all. - -- Does not mean the metaphor proves the claim. Per Amara's - round-4 push: when the metaphor is doing the proving, - delete it. When the metaphor is doing the framing for an - observer, keep it. - -- Does not mean every observer needs the anchor. People - with our engineering vocabulary can read the substrate - directly. The anchor is for observers WITHOUT shared - vocabulary. - -- Does not mean any metaphor is acceptable. Anchors that - overclaim ("this PROVES our claim") get rejected; anchors - that frame ("this is the human-lineage analog of our - pattern") get kept. - -## Composes with - -- `memory/feedback_beacon_promotion_load_bearing_rules_earn_external_anchors_aaron_amara_2026_04_28.md` - — load-bearing rules earn external anchors when they're - correct. This rule is the rendering-side specification: - once an anchor IS earned, it stays in the prose for - observability. -- `memory/feedback_otto_340_language_is_the_substance_of_ai_cognition_ontological_closure_beneath_otto_339_mechanism_2026_04_25.md` - — language IS substrate; word choice shifts weights. - Anchor naming is part of the substrate-rendering layer. -- `memory/feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md` - — Aaron's correction is preserved verbatim above per the - channel rule. -- The 2026-04-29 round-4 absorb at - `docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md` - — where this correction lands operationally; updates the - round-4 §A.3 framing. -- Otto-339 / Otto-340 — words-shift-weights + substrate-IS- - identity. The metaphor in prose is part of the substrate - the next reader (human or AI) will absorb. - -## Distilled keepers - -```text -Cite the lineage, do not dress engineering claims with it. -``` - -```text -Human-lineage anchors are observability infrastructure, -not proof scaffolding. -``` - -```text -Aaron 2026-04-29: - "we still need to link to human lineage so external - observerse have a frame of references without fully - understading our engineering" -``` From 21ee577409b965bbed2bf612f68b282478e1f015 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Wed, 29 Apr 2026 03:07:01 -0400 Subject: [PATCH 5/5] fix(B-0105): kebab-case Home 1 path to match docs/operations/ convention (Copilot) Copilot caught case mismatch: existing files under docs/operations/ are lowercase kebab-case; my suggested ALL-CAPS path violates that convention. Co-Authored-By: Claude Opus 4.7 --- ...ation-pass-three-durable-homes-for-2026-04-29-rule-set.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md b/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md index 6493b2d62..ab8af97b2 100644 --- a/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md +++ b/docs/backlog/P2/B-0105-consolidation-pass-three-durable-homes-for-2026-04-29-rule-set.md @@ -28,8 +28,9 @@ consolidation pass converts them into ≤3 durable homes. ### Home 1 — PR-liveness / merge-cascade operational doc -Likely path: `docs/operations/MERGE-CASCADE-PR-LIVENESS-RULE.md` -or similar. Absorbs: +Likely path: `docs/operations/merge-cascade-pr-liveness-rule.md` +(kebab-case to match existing `docs/operations/` filename +convention; Copilot caught the ALL-CAPS mismatch). Absorbs: - Probabilistic race framing (PR-liveness race during merge cascade is observed/probabilistic, not deterministic)