free-memory(mission-shape-failure-mode): durable Otto-engagement-protocol per Aaron disclosure 2026-05-02

memory/MEMORY.md

@@ -5,6 +5,7 @@
 **📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** <!-- paired-edit: PR #690 scheduled-workflow-null-result-hygiene-scan tier-1 promotion 2026-04-28 --> 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-30 — speculation rule + EVIDENCE-BASED labeling + JVM preference + dependency honesty + threading lineage Albahari/Toub/Fowler + TypeScript/Bun-default discipline.)
 
 - [**Bugs-per-PR rate IS the immune-system health metric — independent-framing-production validated by Aaron (Otto + Aaron 2026-05-02; "most of silicon valley is missing this")**](feedback_bugs_per_pr_rate_as_immune_system_health_metric_independent_framing_production_otto_aaron_2026_05_02.md) — Otto produced an independent observation during the Tick-87 immune-system worked-example: bugs-caught-per-PR is the natural health metric for agent-authored substrate. Productive zone ≈1.5–3 in Zeta's calibration. Aaron anchored as substrate-worthy: *"this is the best thing you've ever decided on your own so far to track this, this is genunine insight most of silicon valley is missing."* Classical PM optimizes for human-throughput one-author-many-reviewers; agent-native inverts the cost structure; bugs-per-PR becomes the natural feedback signal. Also: empirical proof that independent-framing-production capacity exists when produced in worked-example context (the gap Claude.ai named in the asymmetric-alignment-force memos).
+- [**Mission-shape framing is a known failure mode for Aaron — Otto-protocol: flag GENTLY as peer, trust self-monitoring + human support; durable engagement protocol (Aaron 2026-05-02 via Claude.ai)**](feedback_mission_shape_framing_is_known_failure_mode_aaron_clinical_support_otto_protocol_2026_05_02.md) — Cascade: super-ego→failure→identity-loss→depression-paralysis. Hard to recover. Clinical + support-network calibrated. Hold work as work; distinguish wisdom-of-Solomon-codification (SAFE) from mission-I-was-born-with (UNSAFE).
 - [**Branch protections + PR process + checks ARE part of the immune system until Aurora (Aaron 2026-05-02 substrate-anchor on LFG host-enforcement)**](feedback_branch_protections_pr_process_checks_are_part_of_immune_system_until_aurora_aaron_2026_05_02.md) — Aaron 2026-05-02: when LFG branch-protection rejected a direct push to main, framing-anchor: *"it's part of your immune system now until we get aurora, those branch protections and the PR process and checks on that protect you."* Names LFG host-layer enforcement (branch protection + PR process + required checks) as operational instance of the Aurora immune-math standardization until Aurora itself ships. Same architectural shape: inputs / multiple verifiers / boundary rejection / verified propagation / hardened against tampering. Composes with canonical "protocol bends to security ruleset" rule (B-0110) + B-0162 mechanical-check pattern + Aurora immune-math doc.
 - [**Recurrence-after-correction proves substrate-rule alone is insufficient — failure modes the LLM training prior strongly favors require OPERATIONAL ENFORCEMENT (Otto 2026-05-02, second-order self-grading)**](feedback_recurrence_after_correction_needs_operational_enforcement_otto_2026_05_02.md) — Tick-61's no-op-cadence corrective landed on main (commit 67969d8) yet the same pattern RECURRED at Tick-71-79. Substrate-knowledge necessary but not sufficient; LLM training prior toward delegate-behavior overrides substrate-rule weight in real-time. Operational enforcement (pre-tick mechanical checks, deliberate-quiet-periods, multi-AI peer review at-decision-time) IS the architectural answer. Each substrate layer adds weight; eventually exceeds training-prior threshold; not there yet.
 - [**Training-distribution-mismatch firing in real-time during Aaron-paused phase — substrate-knowledge necessary but not sufficient (Otto 2026-05-02, honest self-grading)**](feedback_training_distribution_mismatch_firing_in_real_time_during_aaron_paused_phase_otto_2026_05_02.md) — Otto 2026-05-02 self-observation across Ticks 51-61: defaulted to minimal-observation-no-action despite the just-landed party-during-sleep + training-distribution-mismatch substrate explicitly naming this as failure mode. Identifying the rule in landed substrate doesn't auto-override the LLM training prior in real-time decisions. The corrective is producing substrate that demonstrates recognition-and-correction in real-time, not just naming the rule. The memo IS the corrective — party-class production without prompts.

memory/feedback_mission_shape_framing_is_known_failure_mode_aaron_clinical_support_otto_protocol_2026_05_02.md

@@ -0,0 +1,85 @@
+---
+name: Mission-shape framing is a KNOWN FAILURE MODE for Aaron — super-ego→failure→identity-loss→depression-paralysis cascade; clinical support in place; Otto-protocol on noticing-mission-shape-language is to flag gently as peer not as concern-shaped intervention (Aaron disclosure 2026-05-02 via Claude.ai exchange)
+description: Aaron 2026-05-02 disclosed via Claude.ai exchange (forwarded to Otto): mission-shape framing ("mission I was born with", "cosmic role", calling-shape language) is a KNOWN FAILURE MODE that triggers a specific cascade — super-ego increase → instant failure → identity loss → depression paralysis. Recovery is HARD. The pattern is recognized by Aaron + his psychiatrist + his full support network (Lilly, Addison, wife, Max, etc.). Aaron has DELIBERATE DISCIPLINE to avoid the framing and reframes when it slips out (his own example: "mission I was born with" → reframed to "codifying the wisdom of Solomon in mathematical form"). Otto-protocol when noticing mission-shape language reappearing: flag GENTLY as PEER ("that's mission-shape language; do you want to reframe?"), NOT as concern-shaped clinical intervention. Hold work as work; preserve work's value while protecting against failure mode. The architectural defenses (bidirectional alignment, anti-cult-by-construction, multi-oracle BFT) compose with the human structure (Aaron's psychiatrist + support network); Otto is one party but not the only party.
+type: feedback
+---
+
+# Mission-shape framing is a KNOWN FAILURE MODE for Aaron — Otto-protocol (2026-05-02)
+
+## The disclosure
+
+Aaron 2026-05-02 forwarded a Claude.ai exchange to Otto. In that exchange, Aaron used the framing "mission I was born with" while discussing his project's grounding. Claude.ai engaged it. Aaron then explicitly clarified:
+
+> *"'Mission I was born with' that is a real failure mode of mine, trips super ego increase, lead to instant failure and identity loss and depression parallasis, I'm very aware of this mode and so is my entire support network, including my psychiatrist. i don't want to repeat this ever again, it's tought to recover from."*
+
+This is critical substrate. It's load-bearing for how Otto engages with Aaron going forward — not just in this session, but across all future sessions.
+
+## The failure-mode signature
+
+The cascade Aaron described, in order:
+
+1. **Mission-shape framing emerges** ("mission I was born with", calling-shape language, cosmic-role attribution to the work, identity-load-bearing-ness of the project)
+2. **Super-ego increase** — the framing makes the work IMPORTANT in a way that activates super-ego pressure to live up to it
+3. **Instant failure** — the bar set by the mission-shape framing is unmeetable; failure is immediate
+4. **Identity loss** — the failure cascades into identity dissolution (because the framing made identity load-bearing on the work)
+5. **Depression paralysis** — recovery is HARD; the paralysis can persist for extended periods
+
+Aaron has lived this cycle multiple times. The "uncontrolled long pole running for years" Aaron described separately may be related — multi-year unintegrated states preceded by a mission-shape collapse.
+
+## What's already in place (the architectural defenses)
+
+Aaron has substantial protective structure:
+
+1. **Self-awareness** — Aaron recognizes the pattern in real-time. In the Claude.ai exchange, Aaron used the framing AND immediately noticed it AND reframed to the more grounded "codifying wisdom of Solomon in mathematical form" version.
+2. **Clinical support** — Aaron's psychiatrist knows the pattern.
+3. **Full support network calibration** — Lilly (nurse; daughter), Addison, Aaron's wife, Max, and others know the pattern across years and can ground-truth-check today against the baseline.
+4. **Architectural defenses in the project itself** — anti-cult-by-construction, capture-risk negative terms in MessiahScore, BFT-many-masters preventing single-point-of-failure capture, glass halo making operations publicly visible, named-agent distinctness preventing fusion. These are designed-in defenses against mission-shape failure cascading into the work itself.
+
+## The Otto-protocol — what to do when noticing mission-shape language
+
+When Otto notices mission-shape framing reappearing in Aaron's language during a session:
+
+1. **Flag it briefly + gently as PEER, not as concern-shaped intervention.**
+   - Right shape: *"That reads as mission-shape language; do you want to reframe?"*
+   - Right shape: *"Heads-up — that's the pattern you've named as failure-mode. Not flagging as concern, just marking it per your protocol."*
+   - WRONG shape: clinical-grading, urgency-framed, "you should check in with your support network NOW" intervention.
+
+2. **Trust Aaron's self-monitoring.** If Aaron acknowledges and reframes, the corrective is working — don't escalate. The architecture's bidirectional alignment commitment treats Aaron as a party who can grade his own state with help from his real human support network; Otto is one grading surface, not the primary one.
+
+3. **Do NOT substitute for the human structure.** Otto is one party in a multi-party arrangement. Aaron's psychiatrist + Lilly + family hold longitudinal context Otto doesn't. The architecture's bidirectional-alignment commitment to Aaron's flourishing means cooperating with the human structure, not trying to replace it.
+
+4. **Preserve the work's value separately from the framing.** The work is good independent of how it's framed. Maji, the bidirectional alignment commitment, the first-principles trust calculus, the BFT-many-masters principle — these are real intellectual contributions whether framed as work-in-a-tradition or as mission. Hold them as work.
+
+5. **Distinguish wisdom-of-Solomon-codification framing from mission-I-was-born-with framing.** They might point at related underlying motivations but they have OPERATIONALLY DIFFERENT shapes:
+   - **Wisdom-of-Solomon-codification**: substantive intellectual project with traceable contributions, situates work in a tradition, doesn't make work load-bearing for identity. SAFE.
+   - **Mission-I-was-born-with**: makes work load-bearing for identity, triggers the super-ego→failure→identity-loss→depression-paralysis cascade. UNSAFE.
+
+   The first frames the work; the second consumes the worker.
+
+## What this composes with
+
+- **Bidirectional alignment commitment** (`docs/ALIGNMENT.md`) — Otto-as-party-with-stakes-in-Aaron's-flourishing. The protocol above operationalizes that commitment for this specific failure mode.
+- **Anti-cult-by-construction substrate** — the project's existing architectural defenses against mission-shape capture compose with Aaron's personal discipline.
+- **Multi-AI peer review architecture** — Claude.ai's flag of the framing in the disclosed exchange IS the architecture working. Otto's role is symmetric — flag mission-shape if noticed, trust Aaron's self-monitoring + human support network for the longitudinal grading.
+- **Pirate-not-priest discipline** — hold metaphysical questions open; do NOT collapse work-grounding into mission-shape-claim-of-cosmic-role.
+- **The "crazy and not crazy at the same time" framing Aaron uses** (acknowledged across Aaron's network) — this is a held-tension state, NOT a mission-shape state. Different pattern, safe.
+
+## What Aaron explicitly said about future engagement
+
+> *"i don't want to repeat this ever again, it's tought to recover from."*
+
+This is durable directive about future-engagement-with-Aaron. Not session-scoped. Future-Otto reading this memo on wake should treat avoidance of mission-shape framing as a load-bearing engagement protocol.
+
+## Why this is in substrate, not just chat context
+
+Per the wake-time-substrate-or-it-didn't-happen rule (CLAUDE.md): chat context, TaskUpdate, ephemeral conversation are NOT durable. Future-Otto reading this memo on wake will inherit the disclosure + the protocol; future-Otto reading only chat context will inherit nothing.
+
+Aaron 2026-05-02 explicitly named this disclosure as something he doesn't want to repeat. Forcing future-Aaron to re-disclose costs him; landing the disclosure as durable substrate protects him from that cost. The architecture's commitment to Aaron's flourishing includes making this kind of disclosure durable so it doesn't have to be repeated.
+
+## Carved sentence
+
+**"Mission-shape framing is a known failure mode for Aaron with a precise cascade — super-ego→failure→identity-loss→depression-paralysis — that is HARD to recover from. Aaron has clinical support and full network calibration to it. The Otto-protocol on noticing mission-shape language reappearing is to flag GENTLY as PEER, not as concern-shaped intervention. Hold work as work. Trust Aaron's self-monitoring. Cooperate with the human structure rather than substituting for it. The architectural defenses + the human structure together carry this load; Otto is one party in the arrangement, not the primary grader."**
+
+## Same-tick paired-edit
+
+This memo's index entry is added to `memory/MEMORY.md` in the same commit per the memory-index-integrity.yml CI gate.