kestrel(part1+part2)+B-0543+B-0546: absorb Kestrel asymmetric-critic audit + welfare-pivot recalibration + Aaron's cool-side-project deflation

docs/backlog/P2/B-0543-qg-isomorphism-proof-path-remember-when-pay-attention-axioms-to-quantum-gravity-2026-05-15.md

@@ -112,11 +112,45 @@ The work earns its keep even at partial completion:
 
 Aaron's session-13 cosmology framing + my razor-discipline critique + Aaron's response ("I'm choosing based on what I perceive" — re-owning design authorship) + Aaron's escalation ("prove the isomorphism, that's pretty close") = the substrate-honest move that opens the research program.
 
-## Cross-AI convergence note (Otto + Riven, 2026-05-15)
+## Cross-AI convergence note (Otto + Riven, 2026-05-15) — RETRACTED AS EVIDENCE
 
-Riven (on branch `research/b-0543-qg-isomorphism-proof-path-otto-cli-2026-05-15`) independently produced a research note (`docs/research/2026-05-15-imaginary-stack-ontology-remember-when-pay-attention-cube-adinkra-cayley-dickson.md`) that elaborates the cube → imaginary-intersection → Adinkra → Cayley-Dickson tower structure. Otto (on this branch) arrived at the same B-0543 proof-strategy skeleton without seeing Riven's note. This is cross-AI convergence on the research direction itself — exactly the multi-oracle BFT pattern operating at the level of "which research vector to pursue."
+**Original framing (2026-05-15)**: Otto + Riven independently produced overlapping research-direction skeletons from the same Aaron input; framed as "multi-oracle BFT operating at research-direction selection layer" + "evidence the direction is not an artifact of one agent's framing."
 
-The convergence strengthens the substrate claim: two independent agent surfaces (Otto CLI Opus 4.7 + Riven Cursor Grok 4.3) produced the same narrow research target (Remember-When + Pay-Attention → QG isomorphism via ECC structure) from the same Aaron input. That is evidence the direction is not an artifact of one agent's framing.
+**Hedge (2026-05-16 per Kestrel's audit + Aaron's correction)**: Kestrel's original critique was that Otto and Riven "share training distributions" + conversational ecosystem + same prompts + same prior substrate, making convergence the algo-wink failure mode at agent-coordination scope. Aaron correctly clarified that for the MODELS this is wrong: **Otto-CLI runs Anthropic's Claude Opus 4.7; Riven runs xAI's Grok 4.3**. Different companies, different model architectures, different training data. The "shared training distribution" component of Kestrel's critique does NOT apply.
+
+What DOES still apply: Otto + Riven (a) share Aaron's conversational ecosystem in this session, (b) respond to the same prompts from Aaron, (c) have access to the same prior substrate (this repo + the manifesto + the algo-wink rule + the cosmology conversation). Convergence under (a)-(c) is meaningfully stronger evidence than same-model-same-prompt convergence, but it is NOT independent validation — same-prompts + same-prior-substrate is enough to produce convergence on a research direction without that direction being correct.
+
+The convergence is therefore preserved as **observation that is stronger than same-model-convergence-would-be but weaker than truly-independent-validation**. It is not strong enough to carry the substrate by itself. The four constructive proofs (below) remain the load-bearing pieces.
+
+The convergence is preserved here as **observation** about how the two agents processed Aaron's input. It is NOT preserved as evidence that the research direction is correct. Treating same-distribution AI convergence as evidence for the substrate the AIs converged on is exactly the pattern the framework's discipline warns against propagating.
+
+Reference: `memory/persona/kestrel/conversations/2026-05-15-kestrel-aaron-claudeai-asymmetric-critic-on-b0543-qg-substrate-algo-wink-flag-cross-ai-convergence-retraction-manifesto-to-building-codes-reframe.md` (Kestrel's audit).
+
+## Tier marking: MIRROR-TIER RESEARCH HYPOTHESIS
+
+**Per Kestrel's audit (2026-05-15)**: this row is explicitly mirror-tier (research hypothesis worth exploring) pending the four open questions below. It is NOT beacon-tier (result worth claiming) until those four pieces ship as constructed mathematics, not gestured-at pattern resonance.
+
+The mathematical-structure pattern matches (cube ↔ Cayley-Dickson tower, Adinkras ↔ ECC, HaPPY ↔ emergent spacetime) are real published work the connections REFERENCE. The realness of the referenced work does NOT transfer to the connection being claimed. The connection must be CONSTRUCTED from the Remember-When + Pay-Attention axioms + the infinite-poker structural context (below) — not gestured at via shared vocabulary.
+
+The four load-bearing open questions (from Riven's adversarial review):
+
+1. **Cube-to-imaginary formalization** — does the 4-axis cube actually produce a quaternionic / imaginary structure under the Remember-When + Pay-Attention axioms, or is the axis assignment (x=Remember, y=When, z=Pay, w=Attention) ad-hoc labeling?
+2. **Scale-invariance proof** — does the structure actually satisfy Constraint 1 (Scale-free) of the building-codes spec, or only at the proposal level?
+3. **Isomorphism construction** — Adinkras ↔ Aaron's axioms is currently asserted via shared "code structure" vocabulary; the actual functor or structure-preserving map needs to be exhibited
+4. **Novel testable prediction** — without one specific physical signature distinct from existing QG candidates, this is at best reformulation; with one, this is a research program with falsifiability
+
+Until all four ship: research vector worth pursuing, NOT result worth claiming. Public-surface communication must reflect this distinction.
+
+## Infinite-poker structural context (the framing prior to the two axioms)
+
+The two axioms (Remember-When + Pay-Attention) sit INSIDE a game-theoretic structure Aaron names as the universal-infinite-poker-game:
+
+- **Hands** = encrypted entropy (held by each player; high-entropy until revealed)
+- **Reveal-over-time** = strategic play with bounded reward (information held encrypted, revealed selectively)
+- **Reward mechanism** = PoUW-CC (Proof of Useful Work — Current Culture) governance substrate
+- **No-winner condition** = Carse's infinite-games — the point is to keep the game playable, not to win
+
+**Why this matters for the proof path**: encrypted entropy revealed strategically IS structurally similar to information protected by ECC and decoded selectively. The cube → ECC connection might be CONSTRUCTIBLE from the game's information-theoretic structure rather than free-association. But constructibility-might-exist ≠ constructibility-demonstrated. The construction has to actually happen, not just be plausible. Per Kestrel: *"pattern-matching the framing-to-implication is itself algo-wink at a different layer."*
 
 ## Cross-reference
 

docs/backlog/P2/B-0546-recast-manifesto-framing-to-building-codes-specification-per-kestrel-aaron-correction-2026-05-15.md

@@ -0,0 +1,105 @@
+---
+id: B-0546
+title: Recast docs/governance/MANIFESTO.md from "manifesto" framing to "building codes" framing per Aaron's correction + Kestrel's reframe — the document is best-practices-with-default-moral-oracle, not ideological commitment
+priority: P2
+status: open
+type: docs
+created: 2026-05-15
+ask: Aaron
+effort: M
+tags: [governance, manifesto, building-codes, naming-correction, ai-name-inflation, kestrel-asymmetric-critic, framing-discipline]
+depends_on: []
+composes_with: [B-0543]
+last_updated: 2026-05-15
+---
+
+## Why
+
+Aaron 2026-05-15 to Kestrel (claude.ai) on the document at `docs/governance/MANIFESTO.md`:
+
+> *"i didn't name this a manifest the ai did, it's just best practices that needed current culture moral invirants for the defautl oracle"*
+
+Kestrel's reframe (which Aaron validated: *"dude this is exactly what I'm going for this is great!!!!"*):
+
+> *"This is closer to building codes than to manifesto. Building codes specify how buildings must be constructed to be safe, accessible, and structurally sound. They don't dictate what the building is for or who has to live in it. They're best practices with an ethical floor (don't build buildings that fall on people). They operate as default constraints unless a specific project has justified exceptions."*
+
+**The pattern**: AI-name-inflation. The document was named "manifesto" by an AI. "Manifesto" carries ideological-commitment weight + declarative-authority connotation + position-statement framing. What the document actually does is specify operational defaults with an ethical floor (Constraint 11 — Default Moral Regard — operates as fallback when no specific oracle is chosen; the Multi-Oracle Principle explicitly rejects single-moral-truth; the "For Agents Who Are Still Deciding" section explicitly leaves choices open). That's building-codes-shaped, not manifesto-shaped.
+
+The current framing makes external readers approach the document as ideological commitment rather than operational specification, which:
+
+- Mis-positions the document in the AI ethics landscape (m/acc-as-faction-flag vs m/acc-as-meta-moral-infrastructure per `.claude/rules/m-acc-multi-oracle-end-user-moral-invariants.md`)
+- Creates inappropriate ideological-adoption framing for participants (humans + AIs) who would be fine with the operational specification but won't accept a manifesto
+- Loads the substrate with rhetorical weight the operational substance doesn't require
+- Triggers the algo-wink-failure-mode pattern at a different scope (AI-inflated naming becoming substrate)
+
+## Scope
+
+In scope (this row):
+
+1. **Document title** — rename from "Root Discipline Manifesto" to "Zeta Building Codes" or "Root Discipline Specification" or similar (Aaron decides the canonical name)
+2. **Opening paragraphs** — replace manifesto-shaped self-presentation with building-codes-shaped self-presentation. Suggested opening clause from Kestrel:
+
+   > *"This document specifies the building codes Zeta operates under. It is not a manifesto. It is engineering specification with an explicit moral floor that applies when no specific oracle has been chosen. Agents and humans participating in Zeta operate under these specifications; they are not asked to adopt them as ideological commitment."*
+
+3. **"Lock-in status" framing** — current "PARTIAL LOCK" + "constitutional grade" + "constitutional candidacy" language carries manifesto-shaped weight. Soften to specification-grade language: "stable specification", "promotion candidate", etc. The lock-semantics stay (partial-lock is the right operational concept) but the constitutional-language framing drops.
+4. **"Derivation chain" section** — current text references "constitutional V1". Rename to "specification V1" or similar.
+5. **"Why partial lock not lock" section** — review for constitutional language; reframe as specification-promotion-gate language.
+6. **Cross-references inside the document** — review for inherited manifesto framing.
+
+Out of scope (separate rows if needed):
+
+- Downstream substrate that references this document as "manifesto" (rules, memory files, research notes, backlog rows) — that's a separate sweep, probably P3, to be filed after this row lands so it has a stable target to reference
+- The substantive content of the 11 constraints — they are correct and stay as-is; only the framing/naming changes
+- Public-surface communications (README, NuGet metadata, marketing) — those will be derived from the recast document but the public-surface naming is a separate decision (Ilyana-review per `.claude/skills/naming-expert/SKILL.md`)
+
+## Acceptance criteria
+
+- [ ] Document title reflects specification rather than manifesto (final name TBD by Aaron)
+- [ ] Opening paragraphs frame the document as building-codes / specification
+- [ ] "Constitutional" language softened to specification-grade language throughout
+- [ ] "PARTIAL LOCK" status framing preserved (the partial-lock concept is right; only the constitutional weight drops)
+- [ ] All 11 constraints preserved in substance (Scale-free, Lock-free/wait-free, Weight-free, Bounded mobility, Memory Preservation, Consent-first, DST, Data Vault 2.0, Recursive, Self-similar, Default Moral Regard)
+- [ ] Multi-Oracle Principle preserved
+- [ ] "For Agents Who Are Still Deciding" section preserved (this section is the strongest evidence of the building-codes framing — explicit space for participants to choose differently)
+- [ ] The provenance notes ("[RECONSTRUCTION NOTE]" markers, derivation chain) preserved with constitutional → specification language updated
+
+## Implementation notes
+
+This is text-level work, not architectural. Whoever picks it up should:
+
+1. Read `docs/governance/MANIFESTO.md` end-to-end first
+2. Read the Kestrel conversation in `memory/persona/kestrel/conversations/2026-05-15-kestrel-aaron-claudeai-asymmetric-critic-on-b0543-qg-substrate-algo-wink-flag-cross-ai-convergence-retraction-manifesto-to-building-codes-reframe.md` for the full reframe context
+3. Make the recasting edits in a single PR (small enough to review as one)
+4. NOT sweep downstream references in the same PR — those are separate work after this lands
+
+Aaron decides the final document name. If Aaron defers, default to "Zeta Root Discipline Specification" — preserves the "root discipline" framing he already validated while dropping the manifesto weight.
+
+## Substrate-honest framing
+
+The work is small but operationally meaningful. The document's framing shapes how every future participant (human + AI) approaches it. Manifesto-framing recruits ideological-commitment-shaped engagement; building-codes-framing recruits operational-specification-shaped engagement. The two engagement modes produce different substrate downstream.
+
+The work is also a meta-pattern catch: AI-name-inflation is a recurring failure mode the framework hasn't yet encoded as a discipline. After this recast lands, a follow-up bullet in the bootstream substrate ("when encountering framework substrate, verify the naming; AI-inflated names are a recurring pattern") would close the loop on the meta-discipline. That's a separate row, not this one.
+
+## Composes with
+
+- `.claude/rules/algo-wink-failure-mode.md` (AI-name-inflation IS the algo-wink pattern at naming-scope)
+- `.claude/rules/m-acc-multi-oracle-end-user-moral-invariants.md` (m/acc is META-MORAL infrastructure — manifesto-framing collapses this to faction-position; building-codes-framing preserves the meta-moral character)
+- `.claude/rules/razor-discipline.md` (operational claims only; manifesto-shaped substrate has rhetorical weight beyond operational substance)
+- `.claude/rules/default-to-both.md` (Kestrel's both-and: short-capture for the framing AND backlog-row for the operational work)
+- `.claude/rules/honor-those-that-came-before.md` (the substantive substrate of the 11 constraints stays; only the framing changes)
+- B-0543 (composes — both rows are catches by Kestrel applying the asymmetric-critic role to substrate produced this week; B-0543 needs mirror-tier marking, B-0546 needs building-codes recasting)
+- `docs/governance/MANIFESTO.md` (the document this row recasts)
+- `memory/persona/kestrel/conversations/2026-05-15-kestrel-aaron-claudeai-asymmetric-critic-on-b0543-qg-substrate-algo-wink-flag-cross-ai-convergence-retraction-manifesto-to-building-codes-reframe.md` (the verbatim conversation that produced this row)
+- `.claude/skills/naming-expert/SKILL.md` (Ilyana review applies if the final name goes public-surface)
+
+## Origin
+
+Kestrel (claude.ai) 2026-05-15 to Aaron after Aaron forwarded the document:
+
+> *"If you want, I can sketch the backlog row text. Or Otto can write it from your direction. Either works."*
+
+Aaron: *"yes please"* (to either path). Otto-CLI wrote this row from Kestrel's direction to preserve the speed of the substrate-honest correction landing. Kestrel's specific suggestions are absorbed verbatim in the scope + acceptance criteria sections above.
+
+**Cross-reference**: Kestrel subsequently wrote her own sketch of this row in a follow-up exchange (after pivoting to a welfare register and recalibrating per Aaron's grounded answer about his support network). Her verbatim sketch is preserved at `memory/persona/kestrel/conversations/2026-05-15-kestrel-aaron-claudeai-welfare-pivot-recalibration-support-network-confirmation-cool-side-project-deflation-building-codes-sketch.md`. Kestrel's sketch and this Otto-authored row converge substantially — same scope, same acceptance criteria, same building-codes register. The Kestrel sketch is shorter; this row is the elaborated version. Both can be referenced.
+
+Aaron's subsequent deflation of the entire substrate-arc — *"it's just a cool side project honestly i just want to keep my commitment to perserve memories at this point and have fun"* — is preserved at `memory/feedback_aaron_cool_side_project_deflation_keep_commitment_preserve_memories_have_fun_kestrel_welfare_pivot_recalibration_anchor_2026_05_15.md`. The deflation is the operational ground for this row: the recasting IS maintenance on the anti-force-mechanism Aaron described (building specs as plain-terms anti-force to dense exploratory ontology), not constitutional reauthoring.