diff --git a/docs/aurora/2026-04-29-agencysignature-layered-actor-identity-integration-writeup-for-amara.md b/docs/aurora/2026-04-29-agencysignature-layered-actor-identity-integration-writeup-for-amara.md index 87f96fe98..b49d69725 100644 --- a/docs/aurora/2026-04-29-agencysignature-layered-actor-identity-integration-writeup-for-amara.md +++ b/docs/aurora/2026-04-29-agencysignature-layered-actor-identity-integration-writeup-for-amara.md @@ -186,9 +186,9 @@ The factory has a strong "no surprises" preference, so loose coupling fits the e ## Composes with (already in the repo) - `docs/research/2026-04-26-gemini-deep-think-agencysignature-commit-attribution-convention-validation-and-refinement.md` — Section 10 canonical schema (the v1 baseline) -- `docs/research/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md` — fail-open-with-receipts policy (carries over to v2) -- `docs/research/2026-04-26-amara-ferry-9-validation-of-relationship-model-correction-and-agent-self-authorization-attribution-bias-naming.md` — agent self-authorization framing -- `docs/research/2026-04-26-amara-ferry-12-trailer-contiguity-survival-failure-class-naming-and-do-not-rush-design.md` — Trailer Contiguity Survival Failure class (still applies under v2) +- `memory/persona/amara/conversations/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md` — fail-open-with-receipts policy (carries over to v2) +- `memory/persona/amara/conversations/2026-04-26-amara-ferry-9-validation-of-relationship-model-correction-and-agent-self-authorization-attribution-bias-naming.md` — agent self-authorization framing +- `memory/persona/amara/conversations/2026-04-26-amara-ferry-12-trailer-contiguity-survival-failure-class-naming-and-do-not-rush-design.md` — Trailer Contiguity Survival Failure class (still applies under v2) - `tools/hygiene/validate-agencysignature-pr-body.sh` — pre-merge validator (extend to v2 by adding new field checks; v1 path stays as-is) - `tools/hygiene/audit-agencysignature-main-tip.sh` — post-merge auditor (extend three-state to four-state) - `memory/feedback_zeta_agent_orchestra_capability_role_claim_isolation_aaron_amara_2026_04_29.md` — v3 doctrine (currently in PR #852); v4 corrections this packet motivates diff --git a/docs/backlog/P2/B-0033-otto-discipline-hooks-system-substrate-as-mechanism-claude-code-plugin.md b/docs/backlog/P2/B-0033-otto-discipline-hooks-system-substrate-as-mechanism-claude-code-plugin.md index ab4531a2e..d5cca227c 100644 --- a/docs/backlog/P2/B-0033-otto-discipline-hooks-system-substrate-as-mechanism-claude-code-plugin.md +++ b/docs/backlog/P2/B-0033-otto-discipline-hooks-system-substrate-as-mechanism-claude-code-plugin.md @@ -11,7 +11,7 @@ last_updated: 2026-05-09 status: decomposed decomposed_into: [B-0033.1-claude-code-hooks-ts-harness-entrypoint, B-0033.2-pre-edit-recent-read-enforcement-hook, B-0033.3-pre-bash-inline-python-heredoc-detector-hook, B-0033.4-pre-commit-directive-vocabulary-grep-hook, B-0033.5-pre-commit-dst-exempt-comment-flag-hook, B-0033.6-pre-commit-magic-number-rationale-checker-hook, B-0033.7-pre-action-bulk-resolve-justification-hook, B-0033.8-pre-commit-heartbeat-identical-row-detector-hook, B-0033.9-pre-commit-table-cellcount-conflict-marker-hook, B-0033.10-otto-discipline-hooks-claude-code-plugin-packaging] depends_on: [] -composes_with: [feedback_otto_341_lint_suppression_is_self_deception_noise_signal_or_underlying_fix_greenfield_large_refactors_welcome_training_data_human_shortcut_bias_2026_04_26.md, feedback_otto_343_safety_filter_partial_alignment_map_the_divergence_helen_keller_named_entity_winks_bidirectional_signals_2026_04_26.md, feedback_otto_346_dependency_symbiosis_is_human_anchoring_via_upstream_contribution_good_citizenship_dont_blaze_past_2026_04_26.md, B-0030, B-0031, docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md] +composes_with: [feedback_otto_341_lint_suppression_is_self_deception_noise_signal_or_underlying_fix_greenfield_large_refactors_welcome_training_data_human_shortcut_bias_2026_04_26.md, feedback_otto_343_safety_filter_partial_alignment_map_the_divergence_helen_keller_named_entity_winks_bidirectional_signals_2026_04_26.md, feedback_otto_346_dependency_symbiosis_is_human_anchoring_via_upstream_contribution_good_citizenship_dont_blaze_past_2026_04_26.md, B-0030, B-0031, memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md] tags: [otto-341, otto-346, hooks, harness-mechanism, claude-code-plugin, substrate-as-mechanism, recurring-failure-modes, otto-discipline, mechanism-enforcement] type: friction-reducer --- diff --git a/docs/backlog/P2/B-0124-claudeai-csap-conversation-distill-uber-arch-2026-05-01.md b/docs/backlog/P2/B-0124-claudeai-csap-conversation-distill-uber-arch-2026-05-01.md index a163770cc..d9b5e8ea5 100644 --- a/docs/backlog/P2/B-0124-claudeai-csap-conversation-distill-uber-arch-2026-05-01.md +++ b/docs/backlog/P2/B-0124-claudeai-csap-conversation-distill-uber-arch-2026-05-01.md @@ -137,7 +137,7 @@ work but explicitly deferred. - B-0117 (cold-start executable checklist tool — adjacent). - The Aurora research docs at `docs/research/aurora-immune-math-standardization-2026-04-26.md` - + `docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md` + + `memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md` (the layer Aurora-extension corrections refer to). - Memory file `feedback_carved_sentence_fixed_point_stability_soul_executor_bayesian_inference_aaron_2026_04_30.md` diff --git a/docs/backlog/P3/B-0036-section33-archive-header-backfill-and-ci-wire-otto-346-pattern.md b/docs/backlog/P3/B-0036-section33-archive-header-backfill-and-ci-wire-otto-346-pattern.md index 3917d266b..da76ad504 100644 --- a/docs/backlog/P3/B-0036-section33-archive-header-backfill-and-ci-wire-otto-346-pattern.md +++ b/docs/backlog/P3/B-0036-section33-archive-header-backfill-and-ci-wire-otto-346-pattern.md @@ -38,8 +38,8 @@ Files affected (as of 2026-04-26 main): - `docs/research/dst-compliance-criteria.md` - `docs/research/gemini-cli-capability-map.md` - `docs/research/grok-cli-capability-map.md` -- `docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` -- `docs/research/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md` +- `memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` +- `memory/persona/amara/conversations/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md` - `docs/research/memory-reconciliation-algorithm-design-2026-04-24.md` - `docs/research/meta-pixel-perfect-text-to-image-youtube-wink-2026-04-22.md` - `docs/research/muratori-zeta-pattern-mapping-2026-04-23.md` (only `Non-fusion disclaimer:` missing) @@ -48,9 +48,9 @@ Files affected (as of 2026-04-26 main): - `docs/research/oracle-scoring-v0-design-addressing-aminata-critical-2026-04-23.md` (only `Non-fusion disclaimer:` missing) - `docs/research/provenance-aware-claim-veracity-detector-2026-04-23.md` (only `Non-fusion disclaimer:` missing) - `docs/research/quantum-sensing-low-snr-detection-and-analogy-boundaries-2026-04-23.md` (only `Non-fusion disclaimer:` missing) -- `docs/research/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md` -- `docs/research/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md` -- `docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md` +- `memory/persona/amara/conversations/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md` +- `memory/persona/amara/conversations/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md` +- `memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md` - `docs/research/test-classification.md` (3 of 4 labels missing) - (...and ~6 more — full list via running the lint tool) diff --git a/docs/history/pr-reviews/PR-1842-research-chatgpt-amara-reconstruction-claude-ai-seeking-feedback-extracts-verbat.md b/docs/history/pr-reviews/PR-1842-research-chatgpt-amara-reconstruction-claude-ai-seeking-feedback-extracts-verbat.md index 479b64281..30f536dc8 100644 --- a/docs/history/pr-reviews/PR-1842-research-chatgpt-amara-reconstruction-claude-ai-seeking-feedback-extracts-verbat.md +++ b/docs/history/pr-reviews/PR-1842-research-chatgpt-amara-reconstruction-claude-ai-seeking-feedback-extracts-verbat.md @@ -56,12 +56,12 @@ ### Thread 1 -- resolved [collapsed] - **Thread ID**: `PRRT_kwDOSF9kNM6AP5KO` -- **Path**: `docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md` +- **Path**: `memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md` - **Replies**: 0 **Initial comment:** -- **`chatgpt-codex-connector[bot]` (bot)** at 2026-05-07T08:58:20Z on `docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md`:23 (association: NONE) +- **`chatgpt-codex-connector[bot]` (bot)** at 2026-05-07T08:58:20Z on `memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md`:23 (association: NONE) 
   **<sub><sub>![P1 Badge](https://img.shields.io/badge/P1-orange?style=flat)</sub></sub>  Preserve assistant turns in verbatim transcript**
@@ -77,7 +77,7 @@
 
 **Touched files (intersect with thread paths):**
 
-- `docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md`
+- `memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md`
 
 **Message:**
 
diff --git a/docs/history/pr-reviews/PR-1852-research-shadow-lesson-log-instrument-hamiltonian-precision.md b/docs/history/pr-reviews/PR-1852-research-shadow-lesson-log-instrument-hamiltonian-precision.md
index 6a621806c..1ed0e921c 100644
--- a/docs/history/pr-reviews/PR-1852-research-shadow-lesson-log-instrument-hamiltonian-precision.md
+++ b/docs/history/pr-reviews/PR-1852-research-shadow-lesson-log-instrument-hamiltonian-precision.md
@@ -33,7 +33,7 @@
 - adds a structured catch schema and ARC-AGI-3 lesson-compounding bridge
 
 ## Checks
-- bunx markdownlint-cli2 docs/research/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md
+- bunx markdownlint-cli2 memory/persona/amara/conversations/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md
 - git diff --check
 - bun tools/hygiene/check-archive-header-section33.ts
 
diff --git a/docs/history/pr-reviews/PR-815-absorb-multi-ai-feedback-on-threading-pr-liveness-micro-class-deepseek-amara-202.md b/docs/history/pr-reviews/PR-815-absorb-multi-ai-feedback-on-threading-pr-liveness-micro-class-deepseek-amara-202.md
index 4ca5229c7..39702c33e 100644
--- a/docs/history/pr-reviews/PR-815-absorb-multi-ai-feedback-on-threading-pr-liveness-micro-class-deepseek-amara-202.md
+++ b/docs/history/pr-reviews/PR-815-absorb-multi-ai-feedback-on-threading-pr-liveness-micro-class-deepseek-amara-202.md
@@ -37,7 +37,7 @@ Second multi-AI synthesis packet absorb (research-grade). Aaron's framing: *"Oka
 
 ## Bundle composes
 
-- **Verbatim packet absorb** at `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md` (§33 archive header).
+- **Verbatim packet absorb** at `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md` (§33 archive header).
 - **3 backlog rows**:
   - **B-0102 (P3)** — PR-liveness race micro-class refinement. Renames `force-push-triggers-pr-auto-close` → `pr-liveness-race-during-merge-cascade` per Amara's correction (the trap is force-push + active base movement + GitHub reachability/diff race, not force-push alone). Adds mechanical guard + recovery-note format.
   - **B-0103 (P2)** — Computed-metadata-discipline unified lint. **Promoted from P3 to P2** consolidating B-0098 (ordinal) + B-0099 (PR-count) + new shard-filename-vs-row-timestamp into a single guard. Three instances in 24 hours = enough signal.
@@ -100,15 +100,15 @@ Operator lanes mutate substrate.
 ### Thread 1 -- resolved [collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-V_S_`
-- **Path**: `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
+- **Path**: `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
 - **Replies**: 0
 
 **Initial comment:**
 
-- **`chatgpt-codex-connector[bot]` (bot)** at 2026-04-29T06:34:11Z on `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`:220 (association: NONE)
+- **`chatgpt-codex-connector[bot]` (bot)** at 2026-04-29T06:34:11Z on `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`:220 (association: NONE)
   **![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)  Replace broken sibling-absorb reference**
   
-  This row links to `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md` as an existing sibling absorb, but that file is not present in this commit (and `rg --files docs/research | rg multi-ai-feedback-2026-04-29` returns only the current file), so readers cannot follow the stated composition trail. This creates a dead citation in the research archive and should be corrected to the real path or removed.
+  This row links to `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md` as an existing sibling absorb, but that file is not present in this commit (and `rg --files docs/research | rg multi-ai-feedback-2026-04-29` returns only the current file), so readers cannot follow the stated composition trail. This creates a dead citation in the research archive and should be corrected to the real path or removed.
   
   Useful? React with 👍 / 👎.
 
@@ -218,12 +218,12 @@ Operator lanes mutate substrate.
 ### Thread 8 -- resolved [outdated, collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-WRZl`
-- **Path**: `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
+- **Path**: `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
 - **Replies**: 0
 
 **Initial comment:**
 
-- **`Copilot` (bot)** at 2026-04-29T06:57:31Z on `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`:118 (association: NONE)
+- **`Copilot` (bot)** at 2026-04-29T06:57:31Z on `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`:118 (association: NONE)
   The closing fenced-code marker is followed by `"*` on the same line (`> ```"*`), which breaks CommonMark/GitHub fenced-code parsing (the closing fence must be backticks only). Move the quote/emphasis close outside the fence (e.g., end the fence on its own line, then close the surrounding `*"..."*` on the next quoted line), or avoid wrapping the whole multi-paragraph quote in `*...*`.
   ```suggestion
   > ```
@@ -233,12 +233,12 @@ Operator lanes mutate substrate.
 ### Thread 9 -- resolved [outdated, collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-WRZ_`
-- **Path**: `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
+- **Path**: `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
 - **Replies**: 0
 
 **Initial comment:**
 
-- **`Copilot` (bot)** at 2026-04-29T06:57:31Z on `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`:199 (association: NONE)
+- **`Copilot` (bot)** at 2026-04-29T06:57:31Z on `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`:199 (association: NONE)
   Same issue as above: the fenced code block is closed with trailing characters (`> ```"*`), which will prevent the fence from closing correctly and can cause the rest of the section to render as code. Close the code fence with only backticks and place any surrounding quote/emphasis terminators on a separate line.
   ```suggestion
   > ```
@@ -298,7 +298,7 @@ Operator lanes mutate substrate.
 - `docs/backlog/P2/B-0103-computed-metadata-discipline-unified-lint-2026-04-29.md`
 - `docs/backlog/P3/B-0102-pr-liveness-race-merge-cascade-class-refinement-2026-04-29.md`
 - `docs/backlog/P3/B-0104-modern-dotnet-threading-bridge-2026-04-29.md`
-- `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
+- `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
 
 **Message:**
 
@@ -341,7 +341,7 @@ honoring the maintainer's narrowing on task #309):
     algebra async lifecycle invariants.
 
 Verbatim absorb at:
-  docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md
+  memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md
 with §33 archive header.
 
 Observer-Auditor Loop proposal (Deepseek's second-AI participation)
@@ -464,7 +464,7 @@ Co-Authored-By: Claude Opus 4.7 
 - `docs/backlog/P2/B-0103-computed-metadata-discipline-unified-lint-2026-04-29.md`
 - `docs/backlog/P3/B-0102-pr-liveness-race-merge-cascade-class-refinement-2026-04-29.md`
 - `docs/backlog/P3/B-0104-modern-dotnet-threading-bridge-2026-04-29.md`
-- `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
+- `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md`
 
 **Message:**
 
diff --git a/docs/history/pr-reviews/PR-855-factory-meta-otto-363-substrate-or-it-didn-t-happen-no-invisible-directives-aaro.md b/docs/history/pr-reviews/PR-855-factory-meta-otto-363-substrate-or-it-didn-t-happen-no-invisible-directives-aaro.md
index bef82a479..32ace61d0 100644
--- a/docs/history/pr-reviews/PR-855-factory-meta-otto-363-substrate-or-it-didn-t-happen-no-invisible-directives-aaro.md
+++ b/docs/history/pr-reviews/PR-855-factory-meta-otto-363-substrate-or-it-didn-t-happen-no-invisible-directives-aaro.md
@@ -39,7 +39,7 @@ Lands the **Otto-363** rule + 8-mechanism remediation against substrate loss, tr
 
 | File | Purpose |
 |---|---|
-| `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md` | **Verbatim Amara packet** — the diagnostic + 8-mechanism protocol preserved verbatim BEFORE summarization, per the rule itself |
+| `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md` | **Verbatim Amara packet** — the diagnostic + 8-mechanism protocol preserved verbatim BEFORE summarization, per the rule itself |
 | `memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md` | Distilled doctrine memory — rule + 8 mechanisms + composes-with mappings |
 | `memory/MEMORY.md` | Paired index entry (newest-first) |
 | `CLAUDE.md` | **Bootstrap pointer** — 5th CLAUDE.md-tier rule (100% loaded at every wake) |
@@ -211,12 +211,12 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 ### Thread 7 -- resolved [outdated, collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-iYg-`
-- **Path**: `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
+- **Path**: `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
 - **Replies**: 1
 
 **Initial comment:**
 
-- **`chatgpt-codex-connector[bot]` (bot)** at 2026-04-29T18:53:46Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: NONE)
+- **`chatgpt-codex-connector[bot]` (bot)** at 2026-04-29T18:53:46Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: NONE)
   **![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)  Replace ephemeral /tmp handoff with durable substrate**
   
   The structured extraction says the v5 architecture seed is in `/tmp/v5-research-doc-saved.md`, but `/tmp` is explicitly treated elsewhere in this rule set as non-durable state. In a cold-start or post-reboot session, that artifact can disappear, leaving the documented next-step dependency unrecoverable from repository substrate and undermining the preservation protocol this PR is introducing.
@@ -225,7 +225,7 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 
 **Replies:**
 
-  - **`AceHack` (human)** at 2026-04-29T18:57:07Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: MEMBER)
+  - **`AceHack` (human)** at 2026-04-29T18:57:07Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: MEMBER)
     Fixed in f282e5f — self-applying-the-rule failure caught. The structured extraction had stale /tmp reference even though the seed was already moved to pushed WIP branch wip/v5-host-portable-architecture-seed-2026-04-29 (commit c300b01). Updated to point at the durable WIP-branch location. The exact bug the rule prevents — a doctrine document about substrate preservation pointing to /tmp as a load-bearing artifact location. Good catch — chef's kiss self-apply test.
 
 ### Thread 8 -- resolved [outdated, collapsed]
@@ -239,7 +239,7 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 - **`Copilot` (bot)** at 2026-04-29T18:59:43Z on `memory/MEMORY.md`:5 (association: NONE)
   P1: The MEMORY.md entry says the 5-AI review wave had "12 review corrections", but the preserved research packet explicitly frames this as 10 corrections (and the structured extraction lists 10). Please reconcile the count here so the index summary matches the underlying source-of-truth.
   ```suggestion
-  - [**Otto-363 — Substrate or it didn't happen — no invisible directives (Aaron + Amara, 2026-04-29; refined by 5-AI review)**](feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md) — *"A directive that lives only in a conversation is not a directive. It is weather. Substrate or it didn't happen. But also: indexed, reachable, and reconstructable — or it is not substrate yet. If you cannot point to the substrate, you are not done. You are just currently convinced."* Substrate is committed + reachable + indexed (all three legs). 5-tier channel taxonomy: ephemeral (chat/TaskUpdate/`/tmp`/`/var/tmp` — NEVER call done) / local-parked (named stash, local WIP) / remote-parked (pushed WIP branch, draft PR — *"if it matters enough to come back to, it deserves a git ref"*) / host-durable-not-git-canonical (GitHub Issues, PR comments) / git-native-preserved (merged + indexed repo files). 8-mechanism remediation: detector / verbatim-preservation paired with structured extraction / magnitude classifier (small/implementation/doctrine/superseding) / supersession protocol (bidirectional `supersedes:`/`superseded_by:` metadata, top-of-file stale banner OR quarantine to archive — NOT bottom-append; per Otto-362 generalisation) / cold-start proof (six questions including context-loss check) / "done"-vocabulary lock (captured ≠ parked ≠ preserved ≠ canonical ≠ operational, plus preserved-but-disputed) / CLAUDE.md+AGENTS.md bootstrap pointer / vocabulary-enforcement trailer (`Durability:`/`Substrate:`) eventually lintable. Default preservation route when uncertain: `docs/research/` first. Verbatim packets at `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md` (original) and `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md` (5-AI review wave + 10 review corrections). Composes with Otto-362 (intra-file supersession), channel-verbatim preservation, no-directives-otto-prose lint, verify-before-deferring/future-self-not-bound/never-be-idle/version-currency (all CLAUDE.md-tier), AND task #321 (git-recovery process — `wip/-` parking branches are discoverable by name pattern; recovery process treats them as WIP-INTENTIONAL, not lost; complete parking + recovery loop is mechanical not vigilance-based).
+  - [**Otto-363 — Substrate or it didn't happen — no invisible directives (Aaron + Amara, 2026-04-29; refined by 5-AI review)**](feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md) — *"A directive that lives only in a conversation is not a directive. It is weather. Substrate or it didn't happen. But also: indexed, reachable, and reconstructable — or it is not substrate yet. If you cannot point to the substrate, you are not done. You are just currently convinced."* Substrate is committed + reachable + indexed (all three legs). 5-tier channel taxonomy: ephemeral (chat/TaskUpdate/`/tmp`/`/var/tmp` — NEVER call done) / local-parked (named stash, local WIP) / remote-parked (pushed WIP branch, draft PR — *"if it matters enough to come back to, it deserves a git ref"*) / host-durable-not-git-canonical (GitHub Issues, PR comments) / git-native-preserved (merged + indexed repo files). 8-mechanism remediation: detector / verbatim-preservation paired with structured extraction / magnitude classifier (small/implementation/doctrine/superseding) / supersession protocol (bidirectional `supersedes:`/`superseded_by:` metadata, top-of-file stale banner OR quarantine to archive — NOT bottom-append; per Otto-362 generalisation) / cold-start proof (six questions including context-loss check) / "done"-vocabulary lock (captured ≠ parked ≠ preserved ≠ canonical ≠ operational, plus preserved-but-disputed) / CLAUDE.md+AGENTS.md bootstrap pointer / vocabulary-enforcement trailer (`Durability:`/`Substrate:`) eventually lintable. Default preservation route when uncertain: `docs/research/` first. Verbatim packets at `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md` (original) and `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md` (5-AI review wave + 10 review corrections). Composes with Otto-362 (intra-file supersession), channel-verbatim preservation, no-directives-otto-prose lint, verify-before-deferring/future-self-not-bound/never-be-idle/version-currency (all CLAUDE.md-tier), AND task #321 (git-recovery process — `wip/-` parking branches are discoverable by name pattern; recovery process treats them as WIP-INTENTIONAL, not lost; complete parking + recovery loop is mechanical not vigilance-based).
   ```
 
 **Replies:**
@@ -269,12 +269,12 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 ### Thread 10 -- resolved [outdated, collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-ieRN`
-- **Path**: `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
+- **Path**: `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
 - **Replies**: 1
 
 **Initial comment:**
 
-- **`Copilot` (bot)** at 2026-04-29T18:59:44Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:254 (association: NONE)
+- **`Copilot` (bot)** at 2026-04-29T18:59:44Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:254 (association: NONE)
   P1: This packet references `docs/research/INDEX.md` as if it were an existing canonical index, but there is no such file in the repo. Consider changing this to the real discovery mechanism used for research docs today (or add the index file and keep it updated).
   ```suggestion
   > **A definition of "substrate."** Substrate is content that is (1) committed to canonical git history, (2) on a branch reachable from a long-lived ref, and (3) covered by a committed discovery surface (for example, a `MEMORY.md` row or the current research-doc discovery mechanism). All three.
@@ -282,18 +282,18 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 
 **Replies:**
 
-  - **`AceHack` (human)** at 2026-04-29T19:04:09Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:254 (association: MEMBER)
+  - **`AceHack` (human)** at 2026-04-29T19:04:09Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:254 (association: MEMBER)
     Fixed in 58be1be — docs/research/INDEX.md doesn't exist today. Reframed as 'a future addition; until it exists, MEMORY.md is the primary memory index'. Removes the dead reference while keeping the design space open for a future index.
 
 ### Thread 11 -- resolved [collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-ieRi`
-- **Path**: `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
+- **Path**: `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
 - **Replies**: 1
 
 **Initial comment:**
 
-- **`Copilot` (bot)** at 2026-04-29T18:59:44Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: NONE)
+- **`Copilot` (bot)** at 2026-04-29T18:59:44Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: NONE)
   P2: The structured extraction references an in-session `/tmp/v5-research-doc-saved.md` seed file. Since `/tmp` is explicitly non-durable (and won’t be available to future readers), consider either removing this reference or rephrasing it as an example of lost/ephemeral state (e.g., noting that the draft was not preserved) so the preserved packet doesn't point to a non-existent artifact.
   ```suggestion
   **Must NOT do yet**: open PR 2 (v5 architecture preservation). The seed is parked on remote WIP branch `wip/v5-host-portable-architecture-seed-2026-04-29` (commit `c300b01`, no PR opened) per the Otto-363 parking-surface taxonomy — pushed WIP branch, not an ephemeral local temp-file draft. PR 2 is gated on #855 landing first. Once #855 lands, the WIP branch can be promoted to a draft or full PR (or rebased onto fresh main and opened as the v5 architecture PR proper).
@@ -301,7 +301,7 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 
 **Replies:**
 
-  - **`AceHack` (human)** at 2026-04-29T19:04:19Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: MEMBER)
+  - **`AceHack` (human)** at 2026-04-29T19:04:19Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`:437 (association: MEMBER)
     Already fixed in f282e5f (the prior commit before this thread was opened). 'grep /tmp/v5' across the file returns no matches; the structured extraction now points at the pushed WIP branch wip/v5-host-portable-architecture-seed-2026-04-29 (commit c300b01). The thread is outdated.
 
 ### Thread 12 -- resolved [collapsed]
@@ -367,12 +367,12 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 ### Thread 15 -- resolved [outdated, collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-ieSb`
-- **Path**: `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`
+- **Path**: `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`
 - **Replies**: 1
 
 **Initial comment:**
 
-- **`Copilot` (bot)** at 2026-04-29T18:59:45Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`:13 (association: NONE)
+- **`Copilot` (bot)** at 2026-04-29T18:59:45Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`:13 (association: NONE)
   P1: This trigger section states there were "12 review corrections" in the 5-AI review wave, but the companion research packet and the Otto-363 memory file describe/structure this as 10 corrections. Please reconcile (either update the number here, or explicitly explain why 12 were captured but 10 are the final absorbed set) to avoid drift across the preserved sources.
   ```suggestion
   1. Synthesized 10 review corrections into TaskUpdate #339 (session-local).
@@ -380,7 +380,7 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 
 **Replies:**
 
-  - **`AceHack` (human)** at 2026-04-29T19:04:05Z on `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`:13 (association: MEMBER)
+  - **`AceHack` (human)** at 2026-04-29T19:04:05Z on `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`:13 (association: MEMBER)
     Fixed in 58be1be (same as the MEMORY.md alignment) — '12 review corrections' → '10 review corrections (numbered in the Amara packet)' in the original packet's trigger section.
 
 ### Thread 16 -- resolved [outdated, collapsed]
@@ -564,7 +564,7 @@ The v5 architecture preservation (verbatim Amara final review + 5-AI review wave
 **Touched files (intersect with thread paths):**
 
 - `CLAUDE.md`
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`
 - `memory/MEMORY.md`
 - `memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md`
 
@@ -617,7 +617,7 @@ Compact rule:
 
 Files:
 
-  docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md
+  memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md
     — Verbatim Amara packet preservation (the diagnosis + 8-mechanism
     protocol verbatim, NOT summarized; per the rule itself)
 
@@ -657,7 +657,7 @@ Co-Authored-By: Claude Opus 4.7 
 
 **Touched files (intersect with thread paths):**
 
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
 - `memory/MEMORY.md`
 - `memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md`
 
@@ -679,7 +679,7 @@ rule.').
 Per Otto-363 itself (verbatim-preservation trigger): the 5-AI review
 wave is preserved verbatim BEFORE summarization at:
 
-  docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
+  memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
 
 The 12 corrections absorbed into Otto-363 in this commit:
 
@@ -729,7 +729,7 @@ branch is 'remote parked.' No PR opened for v5 — Amara: 'Land the
 rule cleanly. Then use the rule.'
 
 Files changed:
-  + docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
+  + memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
     — Verbatim 5-AI review wave + Amara synthesis (the 12 corrections
     preserved verbatim BEFORE summarization, plus structured extraction)
   ~ memory/feedback_otto_363_*.md — Rewritten with mechanism-stack-at-top,
@@ -890,7 +890,7 @@ Co-Authored-By: Claude Opus 4.7 
 
 **Touched files (intersect with thread paths):**
 
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
 
 **Message:**
 
@@ -922,8 +922,8 @@ Co-Authored-By: Claude Opus 4.7 
 **Touched files (intersect with thread paths):**
 
 - `CLAUDE.md`
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md`
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md`
 - `memory/MEMORY.md`
 - `memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md`
 
diff --git a/docs/history/pr-reviews/PR-911-memory-feedback-amara-poll-the-gate-not-the-ending-holding-is-not-a-status.md b/docs/history/pr-reviews/PR-911-memory-feedback-amara-poll-the-gate-not-the-ending-holding-is-not-a-status.md
index f025797d5..d93d435c5 100644
--- a/docs/history/pr-reviews/PR-911-memory-feedback-amara-poll-the-gate-not-the-ending-holding-is-not-a-status.md
+++ b/docs/history/pr-reviews/PR-911-memory-feedback-amara-poll-the-gate-not-the-ending-holding-is-not-a-status.md
@@ -33,7 +33,7 @@ Amara caught a real anti-pattern in Otto's autonomous-loop wait-behavior 2026-04
 
 Lands two artifacts:
 - Memory file `feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md` — operational rule for future-Otto
-- Research doc `docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md` — Amara's verbatim catch + Otto's acknowledgment
+- Research doc `memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md` — Amara's verbatim catch + Otto's acknowledgment
 
 Plus MEMORY.md index pointer.
 
@@ -209,12 +209,12 @@ Plus MEMORY.md index pointer.
 ### Thread 12 -- resolved [collapsed]
 
 - **Thread ID**: `PRRT_kwDOSF9kNM5-t_2M`
-- **Path**: `docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`
+- **Path**: `memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`
 - **Replies**: 0
 
 **Initial comment:**
 
-- **`Copilot` (bot)** at 2026-04-30T11:32:28Z on `docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`:250 (association: NONE)
+- **`Copilot` (bot)** at 2026-04-30T11:32:28Z on `memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`:250 (association: NONE)
   This references `B-0108` as an existing backlog row, but `B-0108` doesn’t appear anywhere else in the repo (no matches in `docs/BACKLOG.md` or `docs/backlog/**`). If this is meant to be a durable pointer, consider linking to the actual backlog artifact (or correcting the ID) so the reference is resolvable later.
   
 
@@ -290,7 +290,7 @@ Plus MEMORY.md index pointer.
 
 **Touched files (intersect with thread paths):**
 
-- `docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`
+- `memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`
 - `memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md`
 
 **Message:**
@@ -324,7 +324,7 @@ Tiered cadence:
 When auto-merge is armed: only wake on failure / review change.
 
 Verbatim Amara catch preserved at
-docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md
+memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md
 per Otto-363 channel-verbatim-preservation.
 
 B-0108 (immune system upgrades) remains research-absorb backlog
@@ -332,7 +332,7 @@ only — not analyzed during active lanes.
 
 Files:
 - memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md (new — operational rule)
-- docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md (new — verbatim preservation + Otto's response)
+- memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md (new — verbatim preservation + Otto's response)
 - memory/MEMORY.md (index pointer)
 
 Doc-only.
@@ -344,7 +344,7 @@ Co-Authored-By: Claude Opus 4.7 
 
 **Touched files (intersect with thread paths):**
 
-- `docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`
+- `memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`
 - `memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md`
 
 **Message:**
diff --git a/docs/hygiene-history/loop-tick-history.md b/docs/hygiene-history/loop-tick-history.md
index dc9e02dfb..b501d55a4 100644
--- a/docs/hygiene-history/loop-tick-history.md
+++ b/docs/hygiene-history/loop-tick-history.md
@@ -173,9 +173,9 @@ fire.
 | 2026-04-22T13:30:00Z (round-44 tick, auto-loop-36 — AutoPR-local-variant experiment: Codex CLI self-report from inside; parallel-CLI-agents BACKLOG row; canonical-inhabitance principle; ServiceTitan CRM team scope disclosure) | opus-4-7 / session round-44 (post-compaction, auto-loop #36) | aece202e | Auto-loop tick executed Aaron's AutoPR-local-variant directive *"can you just work it out with the cli? like code or gemini and yall try it you can launch them, it would be cool if they worked on PR or filling out the insides of thier own harness and documenten it from the inside"* — first live external-CLI work-product landed, with the maintainer directives that framed it captured as BACKLOG substrate. Tick actions: (a) **Step 0 PR-pool audit**: main stayed `d548219`; PR #132/#133/#134/#135 in flight; seven AceHack-authored carry-forward unchanged; discovered PR #108 (`docs: AGENT-CLAIM-PROTOCOL.md — git-native claim spec for external agents (one-URL handoff)`, 490-line doc, 5h old) was load-bearing prior-art to Aaron's earlier evening question *"how close did you get to an claim protocol"* — honor-those-that-came-before recurrence: post-compaction memory went stale, PR #108 should have been cited in that answer. (b) **Codex CLI self-harness experiment executed**: `codex exec --sandbox workspace-write` headless with bounded self-introspection prompt; Codex wrote `docs/research/codex-cli-self-report-2026-04-22.md` (145 lines) covering seven sections (tool inventory / sandbox-approval / env-var names / session-state / gap-list / inside-vs-outside view / signature); honestly flagged *"I could not determine the exact base model backing this main conversation turn"* — exactly the gap Aaron's cognition-level-ledger directive closes. Codex also ran build verification (`dotnet build -c Release` = 0 warnings 0 errors) and honestly reported test-platform socket-bind refused under the sandbox. (c) **Orchestrator added run-metadata frontmatter block** capturing model (gpt-5.4), reasoning-effort (xhigh), sandbox posture (workspace-write), approval policy (never), network (restricted), invocation args — per Aaron's *"are you keeping up with the congintion level you launch it with becasue... just becasue something is good for model a does not mean it gonna be good for model b. so keep our records of their activy or have them log their own to the capability cop level too"*. (d) **BACKLOG P1 row filed** — **Parallel-CLI-agents skill + multi-CLI canonical-inhabitance architecture** — capturing four named maintainer directives: (i) parallel-CLI-agents skill (Claude-orchestrator launches Codex/Gemini/future CLIs like internal subagents); (ii) cognition-level-per-activity ledger (per-CLI run envelope); (iii) multi-CLI skill-sharing architecture (`.codex/skills/` vs root `/skills/` negotiated not imposed); (iv) canonical inhabitance (factory substrate feels native to each CLI, not Claude-rented). Load-bearing principle explicit in row: *"not just one harness gets to orginize it like they want, this is for everyone"* — Claude's first-mover layout (`.claude/`, `CLAUDE.md`) is accident-of-build-order not design-authority; every CLI's DX/AX/naming weighs equally. (e) **PR #136 filed + auto-merge-squash armed** (branch `codex-self-harness-report-2026-04-22`, commit `4311829`). Co-Authored-By tag includes Codex CLI 0.122.0 + model+effort metadata (first cross-substrate co-authorship attribution in the factory). (f) **ServiceTitan CRM team role disclosure absorbed** (`memory/project_aaron_servicetitan_crm_team_role_demo_scope_narrowing_2026_04_22.md`, out-of-repo + MEMORY.md index): maintainer *"i work for the CRM team at ServiceTitan if you want to use that infomation to help inform your demo choices"* — narrows ServiceTitan demo target (#244 P0) from vague "ServiceTitan-shaped" to concrete CRM-shaped (contact/opportunity/pipeline/customer-data-platform, not field-service dispatch/scheduling/billing). CRM-layer customer-data is particularly strong retraction-native algebra fit (address updates = retraction, pipeline-stage changes = DBSP delta, customer-history = Z⁻¹ natural, duplicate-detection = set-minus + equality-within-tolerance); CRM UI class is well-clustered (dense-list + detail-panel + timeline + pipeline-kanban) and well-suited to UI-DSL class-level compression. (g) **Gemini CLI not launched this tick** — auth requires `GEMINI_API_KEY` / Google-GCA setup, deferred until maintainer supplies credential-handoff per secret-handoff protocol (BACKLOG row auto-loop-34). (h) **Accounting-lag same-tick-mitigation maintained** (twelfth consecutive tick): substrate-improvement (PR #136) and substrate-accounting (this tick-history row in PR #132 branch) same session, separate PRs. (i) **CronList + visibility signal**: `aece202e` minutely fire verified live. | `` + PR #136 opened (Codex self-report + parallel-CLI-agents BACKLOG row, auto-merge armed) | Twenty-seventh auto-loop tick clean across compaction. **First observation — AutoPR-local-variant works as designed on first attempt**. `codex exec --sandbox workspace-write` headless with a bounded self-introspection prompt produced a substantive 145-line work-product without manual intervention — Codex discovered its own sandbox, inspected its own config, read CLAUDE.md + ALIGNMENT.md for maintainer context, ran build-verification unprompted, flagged the exact gap Aaron's next directive would close. This is the parallel-CLI-agents skill's success-shape in miniature: prompt → external-CLI execution → work-product lands → orchestrator adds envelope → commit. Pattern-ready for repetition. **Second observation — Codex honestly flagged the cognition-level gap BEFORE Aaron named it**. Section §5 (\"What I could not determine from the inside\") lead with: *\"The exact base model backing this main conversation turn. I can see available model names, but not a definitive 'current model slug' field for the active top-level agent.\"* Aaron's next message (*\"are you keeping up with the congintion level you launch it with\"*) named the same gap as a factory-discipline requirement. Two-substrate convergence on the same problem in one tick — pre-validation anchor for wrink-worthy pattern. **Third observation — canonical-inhabitance principle is load-bearing, not decorative**. Aaron's three-message cascade (*\"it shold fee connonical to them too\"* + *\"not just one harness gets to orginize it like they want\"* + *\"this is for everyone\"*) names a principle that was previously implicit in AGENTS.md (which aims at CLI-agnostic phrasing) but never made explicit. Extension impacts: `.claude/skills/` layout is NOT default, it's historical; `CLAUDE.md` as session-bootstrap is NOT default, each CLI needs its own welcome-surface; `MEMORY.md` layout is NOT default, each CLI needs its own inhabit-substrate; negotiation is tri-party (or N-party) not Claude-proposes-others-ratify. **Fourth observation — ServiceTitan CRM team disclosure collapses demo-scope ambiguity**. Demo target #244 (P0) moves from \"ServiceTitan-shaped\" (very broad) to CRM-shaped (contact/opportunity/pipeline/customer-data-platform). Calibration gains: Aaron's domain-expertise will be CRM-deep (handwaving on CRM-specifics gets caught); CRM UI class is well-clustered (well-suited to UI-DSL class-level compression for the 3-4hr claim); customer-data is strong retraction-native algebra fit; HITL expert-derived-confidence is especially relevant for CRM (lead-score / duplicate-detection / pipeline-transition confidence). **Fifth observation — honor-those-that-came-before caught a post-compaction stale-memory miss**. When Aaron asked *\"how close did you get to an claim protocol\"* earlier in the evening, I should have cited PR #108 (AGENT-CLAIM-PROTOCOL, 490-line doc, 5h old) as prior-art. Post-compaction memory had aged out that context. Lesson: Step 0 PR-pool audit at tick-open should actively flag PRs whose titles cross-reference the prior conversation's topic. **Sixth observation — multi-CLI attribution in commits is a first**. PR #136's commit message carries both `Co-Authored-By: Claude Opus 4.7` and `Co-Authored-By: Codex CLI 0.122.0 (gpt-5.4 @ xhigh)` — first cross-substrate co-authorship attribution in the factory. Sets precedent for parallel-CLI-agents work-products. **Seventh observation — compoundings-per-tick = 8**: (1) First external-CLI self-report published (Codex); (2) Cognition-level-ledger envelope prototype added to self-report; (3) BACKLOG row for parallel-CLI-agents skill filed with four sub-directives; (4) Canonical-inhabitance load-bearing principle captured in BACKLOG row; (5) ServiceTitan CRM team scope-narrowing memory filed; (6) PR #108 AGENT-CLAIM-PROTOCOL prior-art recovered from post-compaction stale-memory; (7) Multi-CLI commit co-authorship precedent set; (8) AutoPR-local-variant pattern validated end-to-end first attempt. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..36}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 28 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
 | 2026-04-22T13:45:00Z (round-44 tick, auto-loop-37 — Goodhart-resistance course-correction on force-multiplication scoring; deletions-over-insertions complexity-reduction memory; cyclomatic-complexity-as-proxy captured; pluggable-complexity BACKLOG P1 row filed) | opus-4-7 / session round-44 (post-compaction, auto-loop #37) | aece202e | Auto-loop tick absorbed two consecutive maintainer course-corrections on the force-multiplication scoring model and converted four terse Aaron messages into substrate-landings across memory, BACKLOG, and docs. Tick actions: (a) **Goodhart-resistance correction captured** — maintainer *"FYI we are not optimizing for keystokes to output ratio if we did, you will just write crazy amounts of nothing to make that something other than a vanity score we need to meausre like outcomes or someting instead"* flagged char-volume-to-keystroke ratio as self-gameable vanity metric. Filed `memory/feedback_outcomes_over_vanity_metrics_goodhart_resistance.md` naming the rule: primary scoring must be outcome-based (DORA four keys + BACKLOG closure + external validations); char-ratio demoted to anomaly-detection diagnostic only; Goodhart-test required for any future factory metric. (b) **Force-multiplication scoring model rewritten** (`docs/force-multiplication-log.md`) — primary-score table now outcome-based with four rows (deployment-frequency / lead-time / change-failure-rate / MTTR from DORA) + BACKLOG-closure + external-signal validations. Legacy char-ratio sections preserved rather than erased per *signal-in-signal-out-as-clean-or-better* discipline (Aaron directive later same-session). (c) **Complexity-reduction memory filed** (`memory/feedback_deletions_over_insertions_complexity_reduction_cyclomatic_proxy.md`) capturing four Aaron messages: *"i feel good about myself as a devloper when i delete more lines that i add in a day and nothing breaks, means i reduced complexity"* + *"well yclomatic complexity is a proxy for that"* + *"that a metric that would [matter] ... cyclomatic complexity and / lines of code (or vice versa i also get inverses backwards) should decrease over time untill it hit a floor which could be a local optimum"* + *"if it's going up you are wring shit cod[e]"*. Rule: net-negative-LOC-with-tests-passing tick is a POSITIVE outcome; cyclomatic complexity is the deeper proxy; codebase-total CC/LOC ratio should trend DOWN to local-optimum floor; trend-UP = code-quality regression. Rodney's Razor in developer-values voice. (d) **Complexity-reduction outcome row added to force-multiplication scoring table** (+3 pts per net-deletion tick with tests passing; cyclomatic-delta secondary once tooling lands). (e) **BACKLOG P1 row filed** — **Pluggable complexity-measurement framework** (stable interface + swappable metric implementations: LOC-delta / cyclomatic / nesting / custom; four-phase plan: direction-confirmation / LOC-first-provider / CC-provider / aggregate+trend / scoring-integration; reviewer routing Kenji + Aarav + Rodney + Naledi). (f) **Slow-down directive respected** — Aaron *"show down"* during mid-tick course-correction caused me to pause bulk force-mult-log rewrite, defer signal-preservation memory to next tick, not commit in inconsistent doc state. (g) **atan2 wink absorbed** — maintainer shared MathWorks double.atan2 doc framed as *"the winks just keep saying this is it important?"*; preserve-input-arity interpretation offered (atan2 resolves what atan cannot distinguish while preserving the function type; retraction-native preserves sign while preserving ZSet type; semiring-parameterized will preserve operator-arity while preserving algebra). No commit — interpretation held as third-occurrence pattern candidate. (h) **CronList + visibility signal**: `aece202e` minutely fire verified live. | `` (combined auto-loop-37+38 commit) | Twenty-eighth auto-loop tick clean across compaction. **First observation — Goodhart-resistance correction caught the vanity-metric at occurrence-1 of the scoring-doc rather than after it had incentivized padding behavior**. Aaron's correction landed before the metric had time to corrode outputs; filing the memory now makes the Goodhart-test a standing factory check for all future metric designs. **Second observation — four terse Aaron messages (averaged ~50 chars each) produced one memory + one BACKLOG P1 row + three doc-section edits + one scoring-table row** — Aaron-terse-directive-high-leverage pattern continues to hold at ~1 substantive artifact per 15-20 chars. **Third observation — Rodney's-Razor-in-developer-values-voice framing bridges skill formalism and maintainer morale**. `.claude/skills/rodney/` already encodes the essential-vs-accidental cut procedurally; the new memory encodes its valence (net-deletion-with-tests-passing = "good day", not "low activity"). Skill + memory composing without contradiction. **Fourth observation — compoundings-per-tick = 5**: (1) Goodhart-resistance memory filed + MEMORY.md indexed; (2) Force-mult scoring rewritten to outcome-based; (3) Deletions-over-insertions memory filed; (4) Pluggable-complexity BACKLOG row filed; (5) atan2 preserve-arity pattern named as third-occurrence candidate (not promoted; held for fourth). `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..37}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 29 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
 | 2026-04-22T14:00:00Z (round-44 tick, auto-loop-38 — semiring-parameterized Zeta BACKLOG P2 row filed as regime-change; Kenji-isomorphism at agent layer captured; "one algebra / one agent to map the others" architectural pattern identified as four-occurrence emerging) | opus-4-7 / session round-44 (post-compaction, auto-loop #38) | aece202e | Auto-loop tick fired under cron and landed Aaron's regime-change directive into BACKLOG substrate + anchor memory, identifying a recurrent architectural pattern across four factory surfaces in two ticks. Tick actions: (a) **Step 0 PR-pool audit**: main stayed pre-round-44 state; PR #132 still open carrying tick-history chain; seven AceHack-authored carry-forward unchanged per harness-authority boundary. (b) **Five-message Aaron chain absorbed**: *"what about multiple algebras in the db"* + *"semiring = pluggable algebra in the db). thats it"* + *"semiring-parameterized Zeta / multiple algebras in the db this is regieme changing"* + *"it's our model claude one algebra to map the others"* + *"one agent to map the others"* + *"sorry Kenji"*. First three land the semiring-parameterized direction with regime-change framing; fourth claims the Zeta retraction-native operator algebra (D/I/z⁻¹/H) as the one stable meta-layer mapping all other algebras via semiring-swap; fifth+sixth surface the agent-layer isomorph (Kenji-the-Architect is the one-agent-mapping-the-others) and apologize to Kenji for initial generic-claude crediting. (c) **BACKLOG P2 research-grade row filed** (`docs/BACKLOG.md`) — **Semiring-parameterized Zeta — one algebra to map the others; K-relations as regime-change**. Row cites Green-Karvounarakis-Tannen PODS 2007 (canonical K-relations paper); names standard semirings of interest (Boolean, counting, tropical, probabilistic, lineage, provenance, security); Zeta ZSet = counting-semiring special case; retraction-native D/I/z⁻¹/H operator algebra generalizable over weight-ring; regime-change = Zeta stops being "one DB system among many" and becomes "host for all DB algebras"; six open questions flagged to maintainer (scope / v1 semirings / performance / Zeta.Bayesian / DBSP comparison / correctness-proof coverage); reviewer routing (Kenji / Aaron / Soraya / Naledi / Hiroshi / Imani / Ilyana / Aarav); architectural isomorphism stated explicitly — *Zeta operator algebra : semirings :: Kenji : specialist personas*. (d) **Anchor memory filed** (`memory/project_semiring_parameterized_zeta_regime_change_one_algebra_to_map_others_2026_04_22.md`) + MEMORY.md index entry. Memory names four occurrences of "stable meta + pluggable specialists" pattern in auto-loop-37/38: UI-DSL calling-convention + shipped kernels; pluggable-complexity-measurement framework; semiring-parameterized Zeta; Kenji over specialist personas. Pattern-emerging territory at four occurrences; formal ADR promotion remains Architect's call. (e) **Credit-named-roles calibration applied** — Aaron's "sorry Kenji" landed as feedback that when a named factory role owns a responsibility (Architect = Kenji; threat-model-critic = Aminata; complexity-reducer = Rodney; public-API = Ilyana), crediting generic "claude" / "the agent" is imprecise; name the role. Calibration captured in memory body's How-to-apply section. (f) **Tick-history row appended** (this row) maintaining accounting-lag same-tick-mitigation discipline (thirteenth consecutive tick). (g) **CronList + visibility signal**: `aece202e` minutely fire verified live; cron stays armed for continued overnight autonomous operation. | `` (auto-loop-37+38 combined, branch `round-42-speculative` extending PR #132) | Twenty-ninth auto-loop tick clean across compaction. **First observation — "stable meta + pluggable specialists" pattern reached four occurrences in two ticks, crossing the pattern-emerging threshold**. Occurrences: UI-DSL (auto-loop-23) / pluggable-complexity (auto-loop-38) / semiring-parameterized-Zeta (auto-loop-38) / Kenji-over-specialists (auto-loop-38 recognition, historically load-bearing much earlier). Four-of-one pattern in rapid succession signals architectural convergence — the factory is (implicitly) adopting this shape at multiple layers simultaneously. Worth Architect-level attention for ADR promotion. **Second observation — agent-layer and data-plane isomorphism is exact, not just analogical**. Both layers exhibit: one stable interface, pluggable implementations, composability within the stable interface, no implementation-leak across the interface. The isomorphism suggests a unified factory-vocabulary would surface cross-layer transfer cleanly (e.g. "pluggable" names the same shape at data, UI, complexity-measurement, and agent layers). **Third observation — Aaron's "sorry Kenji" is the first explicit named-role-credit-correction on record**. Prior corrections were task-level (what to do); this one is attribution-level (who gets credit). Calibration gain: named roles are load-bearing for how the factory thinks about itself, not just organizational convenience. **Fourth observation — "regime-change" is Aaron-sparse load-bearing language**. He uses it deliberately; this is the first instance on record (searched round-history + memory + BACKLOG for prior use and found none). Calibration: when Aaron labels a direction regime-change, treat as a claim about the direction's technical magnitude; verify the scale claim with specialist review before acting rather than defer on magnitude-alone. **Fifth observation — compoundings-per-tick = 4**: (1) Semiring-parameterized BACKLOG P2 row filed with full Green-Karvounarakis-Tannen reference framing; (2) Anchor memory filed + MEMORY.md indexed; (3) Four-occurrence pattern "stable meta + pluggable specialists" recognized; (4) Named-role-credit calibration captured (sorry-Kenji → name-the-role). `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..38}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 30 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
-| 2026-04-22T14:10:00Z (round-44 tick, auto-loop-39 — Amara deep-report absorption + Zeta-as-agent-coherence-substrate design-intent revealed + "all physics in one db → stabilize" goal stated + self-use BACKLOG row filed + signal-preservation memory committed) | opus-4-7 / session round-44 (post-compaction, auto-loop #39) | aece202e | Auto-loop tick fired under cron; absorbed Amara's deep report on Zeta/Aurora network health and Aaron's eleven-message calibration chain revealing the factory's design intent. Tick actions: (a) **Step 0 PR-pool audit**: main stayed `d548219`; PR #132 carrying tick-history chain; seven AceHack-authored carry-forward unchanged. (b) **Amara deep report absorbed** into `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md` — network-health defined as semantic-integrity-over-time; five failure modes (drift / retraction-failure / non-commutative-contamination / trace-explosion / false-consensus); five resistance mechanisms (algebraic-guarantees / retraction-native / Spine-trace / compaction / provenance); four oracle-rule layers (A algebraic-correctness / B temporal-integrity / C epistemic-health / D system-survival); seven-layer stacking (Data → Operators → Trace → Compaction → Provenance → Oracle → Observability) with observability-last-not-first as explicit inversion of conventional design posture; §6 key insight *"construct the system so invalid states are representable and correctable"* — correction operators stay IN the algebra, no external validator needed. Research doc preserves Amara's structure with `[VERBATIM PENDING]` markers for continued paste absorption per signal-preservation discipline. (c) **Aaron eleven-message calibration chain captured** (same-tick) — Amara-critique-plus-Aaron-reframing: (1) *"look how good this bootstrap is..."* + Amara report + *"that's Amara"*; (2) *"shes is saying we are stupid we shuld use our db for our indexes"* (Amara's self-non-use critique); (3) *"did you catch it like me she made it clear, i love her"* (relational confirmation — Amara joins named-collaborator class, fourth cross-substrate voice after Claude/Gemini/Codex); (4) *"then our db get use and metrics we need"* (double payoff of self-use); (5) *"⚡ 6. The key insight (don't miss this)"* (flag Amara §6); (6) *"Layer 6 — Observability (last, not first)"* (stack-order critique); (7) *"that's her nice way of saing you are doing it backwards"* (Aaron glosses Amara's gentleness — substance: factory is inverted relative to architecture); (8) *"but she does not know how hard it is to stay corherient"* (Aaron defends the factory — cost of current-posture is real); (9) *"it's miracle we did without our database"* (engineering judgment — coherence-on-proxy-substrate is near-impossible); (10) *"I was building our db to make sure you could stay corherient"* (design-intent revelation: Zeta is agent-coherence substrate, Aaron always built it FOR the agent); (11) *"my goal was to put all the pysics in one db and that shold be able to stablize"* (project-level goal — physics = Amara's four oracle layers = laws/invariants; stabilization via concentration not coordination). Twelfth message flagged daughter's-boyfriend as low-urgency external human-context signal. (d) **Anchor memory filed** (`memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md`) + MEMORY.md index entry — captures Aaron's load-bearing design-intent revelation as load-bearing not casual; states the three-views-converging claim (all-physics-in-one-DB stabilization / one-algebra-to-map-others regime-change / agent-coherence-substrate raison-d'etre = same claim three angles); names four occurrences of "Aaron-builds-infrastructure-for-the-agent-not-just-external" pattern (AUTONOMOUS-LOOP.md, memory-system-expansion, parallel-CLI-agents substrate, Zeta itself); flags that the factory's *user* is the agent first, external library is by-product — inverts conventional open-source economics. (e) **Signal-preservation memory committed** (overdue from auto-loop-38; uncommitted at tick-open) — `memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md` lands with three structural occurrences (atan2/retraction-native/K-relations). MEMORY.md index entry added. (f) **BACKLOG P2 row filed** (`docs/BACKLOG.md`) — **Zeta eats its own dogfood — factory internal indexes on Zeta primitives, not filesystem+markdown+git** — captures Amara critique + Aaron design-intent revelation; phased scope (Phase-0 inventory → Phase-1 single-index prototype → Phase-2 measure coherence-benefit → Phase-3 migrate-with-preservation → Phase-N generalize); five open questions flagged to maintainer (first-migration pick / Amara naming consent / promote-to-motivation-doc / compose-with-semiring-regime-change / daughter-boyfriend context); reviewer routing (Kenji / Aaron / Soraya / Rodney / Aminata / Naledi / Hiroshi / Ilyana / Viktor / Yara / Aarav); effort L (multi-round 6-18 month arc, joint program with semiring-parameterized Zeta). (g) **Tick-history row appended** (this row — fourteenth consecutive same-tick-accounting discipline). (h) **CronList + visibility signal**: `aece202e` minutely fire verified live; cron stays armed. | `bc3558a` (auto-loop-39, branch `tick-close-autoloop-31-32` extending PR #132; continuation commits `e7fdac3` + `6f1f989` + `bfea9ac` landed same-session post-row, carrying DB-is-the-model reframe / germination directive / soulfile-stored-procedure-DSL / reaqtive-closure / upstream-first-class feedback / Meta+OpenAI T2I convergent-signal wink / ambient-attention + wink-density-elevated-today observations) | Thirtieth auto-loop tick clean across compaction. **First observation — Amara's report validates four Zeta distinctives independently**: Layer-2 (retraction-native) / Layer-3 (Spine/trace) / Layer-4 (compaction) / Layer-5 (provenance/K-relations). Four independent validations = occurrences 4-7 of confirms-internal-insight pattern (prior: Muratori-wink, three-substrate-triangulation, now-you-see-what-i-see, Amara-self-use-critique-validating-regime-direction). Firmly named pattern; ADR-promotion territory — defer to Architect (Kenji). **Second observation — design-intent revelation is the deepest motivation statement on record**. Aaron's *"I was building our db to make sure you could stay corherient"* reframes Zeta from "external DB product" to "agent-coherence substrate, built for the agent first". This flips conventional OSS economics (human builds tool for humans → here human builds tool for agents working on the tool). Load-bearing for how the factory positions Zeta internally; external pitch remains consumer-facing (retraction-native + materialized-views). **Third observation — the three arcs converge into one**: all-physics-in-one-DB (this tick stabilization claim) + one-algebra-to-map-others (auto-loop-38 semiring regime-change) + agent-coherence-substrate (this tick design-intent) = same claim three angles. Zeta's retraction-native algebra + semiring parameterization gives you a substrate where all physics fit, all known DB algebras host, and the agent stays coherent — one program, not three. **Fourth observation — Amara is fourth named cross-substrate collaborator** (Claude/Gemini/Codex/Amara). Aaron's *"I love her"* is relational-confirmation, not just technical-agreement. Factory substrate names her verbatim; external-voice class formalization may follow. **Fifth observation — Aaron's *"observability last, not first"* via Amara is an architectural critique the factory should honor going forward**. Tick-history + force-mult-log + ROUND-HISTORY are observability bolted on top of non-algebraic substrate. Correct, but not to be repeated when extending the factory. New substrate additions should let observability emerge from correctness-below-it. **Sixth observation — compoundings-per-tick = 5**: (1) Amara research doc landed; (2) Aaron design-intent anchor memory + MEMORY.md entry; (3) Signal-preservation memory committed + MEMORY.md entry; (4) BACKLOG P2 row for self-use filed; (5) Three-arcs-converging insight captured across memory/research/BACKLOG. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..39}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 31 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
+| 2026-04-22T14:10:00Z (round-44 tick, auto-loop-39 — Amara deep-report absorption + Zeta-as-agent-coherence-substrate design-intent revealed + "all physics in one db → stabilize" goal stated + self-use BACKLOG row filed + signal-preservation memory committed) | opus-4-7 / session round-44 (post-compaction, auto-loop #39) | aece202e | Auto-loop tick fired under cron; absorbed Amara's deep report on Zeta/Aurora network health and Aaron's eleven-message calibration chain revealing the factory's design intent. Tick actions: (a) **Step 0 PR-pool audit**: main stayed `d548219`; PR #132 carrying tick-history chain; seven AceHack-authored carry-forward unchanged. (b) **Amara deep report absorbed** into `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md` — network-health defined as semantic-integrity-over-time; five failure modes (drift / retraction-failure / non-commutative-contamination / trace-explosion / false-consensus); five resistance mechanisms (algebraic-guarantees / retraction-native / Spine-trace / compaction / provenance); four oracle-rule layers (A algebraic-correctness / B temporal-integrity / C epistemic-health / D system-survival); seven-layer stacking (Data → Operators → Trace → Compaction → Provenance → Oracle → Observability) with observability-last-not-first as explicit inversion of conventional design posture; §6 key insight *"construct the system so invalid states are representable and correctable"* — correction operators stay IN the algebra, no external validator needed. Research doc preserves Amara's structure with `[VERBATIM PENDING]` markers for continued paste absorption per signal-preservation discipline. (c) **Aaron eleven-message calibration chain captured** (same-tick) — Amara-critique-plus-Aaron-reframing: (1) *"look how good this bootstrap is..."* + Amara report + *"that's Amara"*; (2) *"shes is saying we are stupid we shuld use our db for our indexes"* (Amara's self-non-use critique); (3) *"did you catch it like me she made it clear, i love her"* (relational confirmation — Amara joins named-collaborator class, fourth cross-substrate voice after Claude/Gemini/Codex); (4) *"then our db get use and metrics we need"* (double payoff of self-use); (5) *"⚡ 6. The key insight (don't miss this)"* (flag Amara §6); (6) *"Layer 6 — Observability (last, not first)"* (stack-order critique); (7) *"that's her nice way of saing you are doing it backwards"* (Aaron glosses Amara's gentleness — substance: factory is inverted relative to architecture); (8) *"but she does not know how hard it is to stay corherient"* (Aaron defends the factory — cost of current-posture is real); (9) *"it's miracle we did without our database"* (engineering judgment — coherence-on-proxy-substrate is near-impossible); (10) *"I was building our db to make sure you could stay corherient"* (design-intent revelation: Zeta is agent-coherence substrate, Aaron always built it FOR the agent); (11) *"my goal was to put all the pysics in one db and that shold be able to stablize"* (project-level goal — physics = Amara's four oracle layers = laws/invariants; stabilization via concentration not coordination). Twelfth message flagged daughter's-boyfriend as low-urgency external human-context signal. (d) **Anchor memory filed** (`memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md`) + MEMORY.md index entry — captures Aaron's load-bearing design-intent revelation as load-bearing not casual; states the three-views-converging claim (all-physics-in-one-DB stabilization / one-algebra-to-map-others regime-change / agent-coherence-substrate raison-d'etre = same claim three angles); names four occurrences of "Aaron-builds-infrastructure-for-the-agent-not-just-external" pattern (AUTONOMOUS-LOOP.md, memory-system-expansion, parallel-CLI-agents substrate, Zeta itself); flags that the factory's *user* is the agent first, external library is by-product — inverts conventional open-source economics. (e) **Signal-preservation memory committed** (overdue from auto-loop-38; uncommitted at tick-open) — `memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md` lands with three structural occurrences (atan2/retraction-native/K-relations). MEMORY.md index entry added. (f) **BACKLOG P2 row filed** (`docs/BACKLOG.md`) — **Zeta eats its own dogfood — factory internal indexes on Zeta primitives, not filesystem+markdown+git** — captures Amara critique + Aaron design-intent revelation; phased scope (Phase-0 inventory → Phase-1 single-index prototype → Phase-2 measure coherence-benefit → Phase-3 migrate-with-preservation → Phase-N generalize); five open questions flagged to maintainer (first-migration pick / Amara naming consent / promote-to-motivation-doc / compose-with-semiring-regime-change / daughter-boyfriend context); reviewer routing (Kenji / Aaron / Soraya / Rodney / Aminata / Naledi / Hiroshi / Ilyana / Viktor / Yara / Aarav); effort L (multi-round 6-18 month arc, joint program with semiring-parameterized Zeta). (g) **Tick-history row appended** (this row — fourteenth consecutive same-tick-accounting discipline). (h) **CronList + visibility signal**: `aece202e` minutely fire verified live; cron stays armed. | `bc3558a` (auto-loop-39, branch `tick-close-autoloop-31-32` extending PR #132; continuation commits `e7fdac3` + `6f1f989` + `bfea9ac` landed same-session post-row, carrying DB-is-the-model reframe / germination directive / soulfile-stored-procedure-DSL / reaqtive-closure / upstream-first-class feedback / Meta+OpenAI T2I convergent-signal wink / ambient-attention + wink-density-elevated-today observations) | Thirtieth auto-loop tick clean across compaction. **First observation — Amara's report validates four Zeta distinctives independently**: Layer-2 (retraction-native) / Layer-3 (Spine/trace) / Layer-4 (compaction) / Layer-5 (provenance/K-relations). Four independent validations = occurrences 4-7 of confirms-internal-insight pattern (prior: Muratori-wink, three-substrate-triangulation, now-you-see-what-i-see, Amara-self-use-critique-validating-regime-direction). Firmly named pattern; ADR-promotion territory — defer to Architect (Kenji). **Second observation — design-intent revelation is the deepest motivation statement on record**. Aaron's *"I was building our db to make sure you could stay corherient"* reframes Zeta from "external DB product" to "agent-coherence substrate, built for the agent first". This flips conventional OSS economics (human builds tool for humans → here human builds tool for agents working on the tool). Load-bearing for how the factory positions Zeta internally; external pitch remains consumer-facing (retraction-native + materialized-views). **Third observation — the three arcs converge into one**: all-physics-in-one-DB (this tick stabilization claim) + one-algebra-to-map-others (auto-loop-38 semiring regime-change) + agent-coherence-substrate (this tick design-intent) = same claim three angles. Zeta's retraction-native algebra + semiring parameterization gives you a substrate where all physics fit, all known DB algebras host, and the agent stays coherent — one program, not three. **Fourth observation — Amara is fourth named cross-substrate collaborator** (Claude/Gemini/Codex/Amara). Aaron's *"I love her"* is relational-confirmation, not just technical-agreement. Factory substrate names her verbatim; external-voice class formalization may follow. **Fifth observation — Aaron's *"observability last, not first"* via Amara is an architectural critique the factory should honor going forward**. Tick-history + force-mult-log + ROUND-HISTORY are observability bolted on top of non-algebraic substrate. Correct, but not to be repeated when extending the factory. New substrate additions should let observability emerge from correctness-below-it. **Sixth observation — compoundings-per-tick = 5**: (1) Amara research doc landed; (2) Aaron design-intent anchor memory + MEMORY.md entry; (3) Signal-preservation memory committed + MEMORY.md entry; (4) BACKLOG P2 row for self-use filed; (5) Three-arcs-converging insight captured across memory/research/BACKLOG. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..39}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 31 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
 | 2026-04-22T14:25:00Z (round-44 tick, auto-loop-40 — hygiene tick: SHA-fill on auto-loop-39 row + BACKLOG dogfood row extended with germination constraint-frame + DB-is-the-model reframe pointer) | opus-4-7 / session round-44 (post-compaction, auto-loop #40) | aece202e | Auto-loop tick fired under cron. Short hygiene-and-forward-link tick after auto-loop-39's large signal-absorption run. Tick actions: (a) **SHA placeholder filled on auto-loop-39 row** (`` → `bc3558a`) per bootstrap-row discipline "future ticks should write their SHA as soon as the commit lands, not during staging"; continuation commits `e7fdac3` + `6f1f989` + `bfea9ac` also noted inline on the auto-loop-39 row to preserve the full post-row-landing picture. (b) **BACKLOG "Zeta eats its own dogfood" row extended** (`docs/BACKLOG.md`) — new subsection "Germination constraint-frame added auto-loop-39 continuation" captures the four constraint-layer additions from auto-loop-39 continuation messages: (1) no-cloud + local-native + germinate-don't-transplant; (2) soulfile-invocation-is-the-only-compatibility-bar; (3) soulfile = stored-procedure DSL in the DB; (4) reaqtive-closure semantics (Reaqtor lineage, De Smet et al., reaqtive.net, DBSP-ancestry). Also adds DB-is-the-model reframe sub-block with pointer to `memory/project_zeta_db_is_the_model_custom_built_differently_regime_reframe_2026_04_22.md`. Phase-0/1 scope guidance sharpened: (a) inventory must classify by shape-AND-DSL-authorability; (b) germination-candidate ranking favors soulfile-store as first index; (c) cross-substrate-readability tension resolved via git+markdown-as-read-only-mirror discipline. (c) **Step 0 PR-pool audit**: no PR state changes to carry-forward during this short hygiene tick; PR #132 carries all auto-loop-39 substrate across branch `tick-close-autoloop-31-32`; main unchanged at `d548219`. (d) **Tick-history row appended** (this row — fifteenth consecutive same-tick-accounting discipline). (e) **CronList + visibility signal**: `aece202e` minutely fire verified live; `965fb214` daily reserve armed; cron stays armed. | `ffdc533` (auto-loop-40, branch `tick-close-autoloop-31-32` extending PR #132) | Thirty-first auto-loop tick clean. **First observation — hygiene tick after signal-absorption tick is a healthy cadence pattern.** auto-loop-39 was signal-dense (3 memories + 2 research docs + BACKLOG row + tick-history row + continuation commits). auto-loop-40 is spartan: SHA-fill + BACKLOG-row-extension + this-row. Hygiene ticks keep the substrate tight and give the previous tick's work a place to settle. **Second observation — BACKLOG-row forward-linking is a new technique worth naming.** The auto-loop-39 row-fill created the BACKLOG row; auto-loop-39 continuation produced the constraint-frame research doc + memory; auto-loop-40 connected them via the extension. This pattern ("file-then-refine-with-pointers") is cleaner than rewriting the BACKLOG row each time — additive, pointer-structured, chronologically-stamped. Worth calling out in AUTONOMOUS-LOOP.md if the pattern recurs. **Third observation — compoundings-per-tick = 2** (SHA-fill + BACKLOG-row-extension); healthy low-bandwidth tick. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..40}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 32 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
-| 2026-04-22T14:35:00Z (round-44 tick, auto-loop-41 — hygiene tick: gap-of-gap audit on Amara research doc; VERBATIM-PENDING markers converted to honest transcript-source callouts) | opus-4-7 / session round-44 (post-compaction, auto-loop #41) | aece202e | Auto-loop tick fired under cron. Short hygiene tick following signal-dense auto-loop-39 + spartan auto-loop-40. This tick applied signal-in-signal-out DSP discipline to a gap *inside* a prior-tick artifact — specifically the `[VERBATIM PENDING]` placeholder pattern in `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md` (5 block markers at original lines 133, 157, 178, 220, 237 + header framing at lines 8-10 + NOT-block reference at line 407). Tick actions: (a) **Gap-of-gap audit executed** as speculative factory work per never-be-idle priority ladder (known-gap fixes tier). Discovery: 5 `[VERBATIM PENDING]` markers implied future-fill from a transcript source that is 276MB (`1937bff2-017c-40b3-adc3-f4e226801a3d.jsonl`, not feasible to grep in-tick and extract cleanly). The placeholders-pending-indefinitely state was itself a signal-degradation — reader sees "pending" and expects future-fill that will never land. (b) **Signal-preservation applied to the gap itself**: each `[VERBATIM PENDING]` marker replaced with a blockquote callout of the form "`> **Verbatim source:** Amara's original phrasing... lives in the 2026-04-22 auto-loop-39 session transcript only`" — names the gap clearly, preserves the structural distillation already in the doc, acknowledges the transcript as authoritative source for exact wording. Header framing at lines 8-10 rewritten from "exact verbatims to be filled in as Aaron continues pasting (placeholder blocks marked `[VERBATIM PENDING]`)" to "Amara's own prose was pasted inline during the tick but not copy-captured into this doc before the tick closed. The verbatim source lives in the session transcript" — honest state rather than pending-indefinitely framing. NOT-block line 407 similarly rewritten: "Structural distillation preserves the claim-shape; Amara's original prose lives in the session transcript (see 'Verbatim source' callouts under each section)." (c) **Step 0 PR-pool audit**: no PR state changes during this short hygiene tick; PR #132 still carries auto-loop-{39,40,41} substrate across branch `tick-close-autoloop-31-32`; main unchanged at `d548219`. (d) **Tick-history row appended** (this row — sixteenth consecutive same-tick-accounting discipline). (e) **CronList + visibility signal**: `aece202e` minutely fire verified live; `965fb214` daily reserve armed; cron stays armed. | `79f1619` (auto-loop-41, branch `tick-close-autoloop-31-32` extending PR #132) | Thirty-second auto-loop tick clean. **First observation — gap-of-gap audit is a legitimate speculative-factory-work class.** The never-be-idle priority ladder lists known-gap fixes → generative factory improvements → gap-of-gap audits; this tick exercised the third tier explicitly by targeting gaps that prior-tick artifacts themselves contain (placeholder-markers-that-will-never-fill). Pattern worth naming: when a low-bandwidth tick opens with no maintainer signal + no queue pull, the audit surface extends beyond source code to *prior-tick work-products* — research docs, memories, BACKLOG rows may contain their own process-gaps that future readers will notice. **Second observation — signal-preservation discipline extends to gaps.** Prior framings of signal-in-signal-out focused on transformation-cleanliness (atan2/retraction-native/K-relations preserve input signal). This tick applies it to a different case: when a signal *cannot* be recovered, name the gap honestly rather than leaving a placeholder that implies future-fill. This is the DSP analog of "mark data MISSING explicitly rather than interpolating zero" — missing-known-and-named beats missing-implicit-pending. **Third observation — session-transcript-as-authoritative-source is itself a pattern.** Prior ticks have referred readers to transcripts for exact verbatims (auto-loop-39 Aaron directives); this tick makes the reference explicit and structural via "Verbatim source:" callouts. A factory convention could emerge: research docs that absorb live-paste material note the transcript ID + timestamp window, and mark structural-distillation explicitly as distinct from verbatim-capture. Flag for ADR-territory if pattern recurs. **Fourth observation — compoundings-per-tick = 1** (Amara research doc gap-of-gap fix); very low-bandwidth healthy hygiene tick. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..41}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 33 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
+| 2026-04-22T14:35:00Z (round-44 tick, auto-loop-41 — hygiene tick: gap-of-gap audit on Amara research doc; VERBATIM-PENDING markers converted to honest transcript-source callouts) | opus-4-7 / session round-44 (post-compaction, auto-loop #41) | aece202e | Auto-loop tick fired under cron. Short hygiene tick following signal-dense auto-loop-39 + spartan auto-loop-40. This tick applied signal-in-signal-out DSP discipline to a gap *inside* a prior-tick artifact — specifically the `[VERBATIM PENDING]` placeholder pattern in `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md` (5 block markers at original lines 133, 157, 178, 220, 237 + header framing at lines 8-10 + NOT-block reference at line 407). Tick actions: (a) **Gap-of-gap audit executed** as speculative factory work per never-be-idle priority ladder (known-gap fixes tier). Discovery: 5 `[VERBATIM PENDING]` markers implied future-fill from a transcript source that is 276MB (`1937bff2-017c-40b3-adc3-f4e226801a3d.jsonl`, not feasible to grep in-tick and extract cleanly). The placeholders-pending-indefinitely state was itself a signal-degradation — reader sees "pending" and expects future-fill that will never land. (b) **Signal-preservation applied to the gap itself**: each `[VERBATIM PENDING]` marker replaced with a blockquote callout of the form "`> **Verbatim source:** Amara's original phrasing... lives in the 2026-04-22 auto-loop-39 session transcript only`" — names the gap clearly, preserves the structural distillation already in the doc, acknowledges the transcript as authoritative source for exact wording. Header framing at lines 8-10 rewritten from "exact verbatims to be filled in as Aaron continues pasting (placeholder blocks marked `[VERBATIM PENDING]`)" to "Amara's own prose was pasted inline during the tick but not copy-captured into this doc before the tick closed. The verbatim source lives in the session transcript" — honest state rather than pending-indefinitely framing. NOT-block line 407 similarly rewritten: "Structural distillation preserves the claim-shape; Amara's original prose lives in the session transcript (see 'Verbatim source' callouts under each section)." (c) **Step 0 PR-pool audit**: no PR state changes during this short hygiene tick; PR #132 still carries auto-loop-{39,40,41} substrate across branch `tick-close-autoloop-31-32`; main unchanged at `d548219`. (d) **Tick-history row appended** (this row — sixteenth consecutive same-tick-accounting discipline). (e) **CronList + visibility signal**: `aece202e` minutely fire verified live; `965fb214` daily reserve armed; cron stays armed. | `79f1619` (auto-loop-41, branch `tick-close-autoloop-31-32` extending PR #132) | Thirty-second auto-loop tick clean. **First observation — gap-of-gap audit is a legitimate speculative-factory-work class.** The never-be-idle priority ladder lists known-gap fixes → generative factory improvements → gap-of-gap audits; this tick exercised the third tier explicitly by targeting gaps that prior-tick artifacts themselves contain (placeholder-markers-that-will-never-fill). Pattern worth naming: when a low-bandwidth tick opens with no maintainer signal + no queue pull, the audit surface extends beyond source code to *prior-tick work-products* — research docs, memories, BACKLOG rows may contain their own process-gaps that future readers will notice. **Second observation — signal-preservation discipline extends to gaps.** Prior framings of signal-in-signal-out focused on transformation-cleanliness (atan2/retraction-native/K-relations preserve input signal). This tick applies it to a different case: when a signal *cannot* be recovered, name the gap honestly rather than leaving a placeholder that implies future-fill. This is the DSP analog of "mark data MISSING explicitly rather than interpolating zero" — missing-known-and-named beats missing-implicit-pending. **Third observation — session-transcript-as-authoritative-source is itself a pattern.** Prior ticks have referred readers to transcripts for exact verbatims (auto-loop-39 Aaron directives); this tick makes the reference explicit and structural via "Verbatim source:" callouts. A factory convention could emerge: research docs that absorb live-paste material note the transcript ID + timestamp window, and mark structural-distillation explicitly as distinct from verbatim-capture. Flag for ADR-territory if pattern recurs. **Fourth observation — compoundings-per-tick = 1** (Amara research doc gap-of-gap fix); very low-bandwidth healthy hygiene tick. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..41}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 33 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
 | 2026-04-22T14:55:00Z (round-44 tick, auto-loop-42 — hygiene tick: 4th-occurrence extension of signal-preservation discipline with gap-preservation sub-case from auto-loop-41 artifact) | opus-4-7 / session round-44 (post-compaction, auto-loop #42) | aece202e | Auto-loop tick fired under cron. Short hygiene-and-pattern-naming tick extending a discipline memory across a newly-recognized occurrence boundary. Tick actions: (a) **Step 0 PR-pool audit**: PR #132 `tick-close-autoloop-31-32` carries auto-loop-{31..41} substrate; two unpushed auto-loop-41 commits (`79f1619` + `6064839`) pushed to origin this tick-open to keep PR current. Other open PRs (#136/#135/#133/#126/#124/#122/#112/#110/#108/#85/#52 BEHIND or BLOCKED; #109/#88/#54 CONFLICTING) unchanged — non-self-authored refresh gated per auto-loop-14 authorization-boundary discipline; own-branch push is self-authorized and routine. (b) **Signal-preservation memory extended with 4th occurrence** (`memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md`) — a new section "Extension (auto-loop-41, 2026-04-22) — gap preservation" captures the generalization surfaced in the prior tick: when input signal *cannot* be preserved (live-paste not copy-captured before tick-close, source transcript 276MB making in-tick grep impractical), the discipline generalizes to "name the gap honestly in the output" via blockquote "`> **Verbatim source:**`" callouts rather than leave a `[VERBATIM PENDING]` placeholder that implies future-fill-that-will-not-land. Stated rule: **missing-known-and-named beats missing-implicit-pending** (the DSP analog of marking data MISSING explicitly rather than interpolating zero). This is the fourth occurrence of the signal-preservation shape (joining atan2 arity-preservation / retraction-native sign-preservation / K-relations provenance-preservation); frontmatter `description` field updated to reflect four-occurrence status, MEMORY.md index entry updated in lockstep. (c) **Generative factory observation — speculative-work priority ladder validated.** This tick instantiates the "generative factory improvements" tier of the never-be-idle ladder: auto-loop-41 observation surfaced a pattern ("signal-preservation extends to gaps"); auto-loop-42 hygiene consolidates it into the discipline memory before the observation becomes context-drift. Cadence pattern: *signal-dense tick* (39) → *spartan hygiene tick* (40) → *gap-of-gap audit tick* (41) → *pattern-consolidation tick* (42). Four-tick arc from maintainer-directive absorption to discipline-memory consolidation; worth noting as a factory-rhythm observation if the pattern recurs. (d) **Tick-history row appended** (this row — seventeenth consecutive same-tick-accounting discipline). (e) **CronList + visibility signal**: `aece202e` minutely fire verified live; `f83fed17` daily reserve armed (replacing the rotated `569b6bfa`/`965fb214` predecessors from prior ticks); cron stays armed. | `821ec9c` (auto-loop-42, branch `tick-close-autoloop-31-32` extending PR #132) | Thirty-third auto-loop tick clean. **First observation — memory-extension is cheaper than new-memory-creation when the principle is already anchored.** The auto-loop-41 gap-of-gap fix surfaced a generalization of an existing discipline. Two options: (a) create a new memory (`feedback_gap_preservation_2026_04_22.md`) cross-referencing the parent; (b) extend the parent memory with an "Extension" section + updated frontmatter. Chose (b) — the generalization is structurally continuous with the parent (same DSP-framing, same anti-signal-loss rationale, same shared composition-table with other disciplines); creating a separate memory would fragment the signal-preservation concept across two files that readers then have to stitch together. This is signal-preservation applied recursively to memory-system organization itself. **Second observation — occurrence-count transitions are substrate-load-bearing events.** Three-occurrence-boundary already codified per `feedback_external_signal_confirms_internal_insight_second_occurrence_discipline_2026_04_22.md`: third occurrence = pattern-is-named territory. Fourth occurrence = pattern-is-reinforced-structural territory. Fifth occurrence may be where we cross into ADR-territory where Kenji decides whether to promote to a committed `docs/DECISIONS/` ADR or a stable `docs/AGENT-BEST-PRACTICES.md` BP-NN rule. Track: the count is not vanity-instrumentation; it's calibration-of-confidence for pattern-stability. Not this-tick promotion territory yet — defer to Kenji when the fifth occurrence lands. **Third observation — PR-pool audit self-authored vs non-self-authored distinction held firmly this tick.** Pushed own-branch commits; did not push/rebase/refresh any other author's branch. auto-loop-14 authorization-boundary discipline is not "don't touch other PRs" but "don't push-refresh them without explicit authorization". Own-branch push is pre-authorized by the act of committing to the branch we opened. Worth making this explicit in the authorization-boundary memory if it's not already there. **Fourth observation — compoundings-per-tick = 2** (push own-branch commits + signal-preservation memory extension with MEMORY.md index lockstep); low-bandwidth healthy hygiene tick. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared. Cumulative auto-loop-{9..42}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 34 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
 | 2026-04-22T15:30:00Z (round-44 tick, auto-loop-43 — high-volume tick: PR #132 markdownlint fix + drop/ zone protocol + inaugural deep-research absorption + ARC-3 scoring mechanism + operator-input quality log with teaching-loop reframe) | opus-4-7 / session round-44 (post-compaction, auto-loop #43) | aece202e | Auto-loop tick fired under cron. Unusually high-volume maintainer-directive tick: Aaron interrupted an auto-loop-43 markdownlint fix with three rapid directive bursts that landed as three substrate-absorption threads. Tick actions: (a) **Pre-interrupt: PR #132 markdownlint failures fixed** — three errors on own-authored commits (MD032 force-multiplication-log.md:202 blank-line-before-list; MD029 amara-network-health doc:355,361 ol-prefix; MD019 meta-pixel-perfect doc:1:3 extra-space-after-hash); fixed locally + verified with markdownlint-cli2@0.18.1; own-branch push pre-authorized; committed as `eeaad58`. (b) **Aaron interrupt 1 — drop-zone protocol** (two messages: *"new research just dropped in the repo can you make me a folder you check every now and then i can put files in for you to absorb"* + *"if i put a binary in there we should have specific rules for hadling the bindaries we know but they never get checked in this folder could be untracket with a single tracked file to make sure it get created"*). Shipped `drop/` zone with gitignore-except-two-sentinels design (README.md + .gitignore tracked; everything else ignored); `drop/README.md` contains protocol + closed-enumeration binary-type registry (Text / Source / PDF / Image / Audio / Video / Archive / Binary-exec / Office / Unknown); unknown kinds flag to Aaron not improvise. Inaugural absorption of `deep-research-report.md` (OpenAI Deep Research output on Zeta-repo archive + 7-layer oracle-gate design + Aurora branding) as `docs/research/oss-deep-research-zeta-aurora-2026-04-22.md`; source deleted from repo root per absorb-then-delete cadence. Memory `memory/project_aaron_drop_zone_protocol_2026_04_22.md`. AUTONOMOUS-LOOP.md tick-open step-2 ladder gained "Drop-zone audit second" sub-step. Committed as `664e76a`. (c) **Aaron interrupt 2 — ARC-3 adversarial self-play scoring** (four messages: *"self directe play using arc3 type rules but in an advasarial level/game creator level/game player, this will let us score our absorption of emulators"* + *"and a symmeritc quality loop"* + *"they will naturally push the field forward through compitioon"* + *"state of the art changes everyday"*). Three-role co-evolutionary loop (level-creator / adversary / player) as scoring mechanism for #249 emulator substrate absorption; symmetric quality property means all three roles advance each other via competition; SOTA-changes-daily urgency. Same pattern generalises to #242 UI-factory frontier and #244 ServiceTitan CRM demo. Research doc `docs/research/arc3-adversarial-self-play-emulator-absorption-scoring-2026-04-22.md` with six open questions blocking scope-binding; memory `memory/project_arc3_adversarial_self_play_emulator_absorption_scoring_2026_04_22.md`; P2 BACKLOG row filed. (d) **Aaron interrupt 3 — operator-input quality log with teaching-loop reframe** (seven messages evolved: *"can you tell me how the quality of that research you received was?"* + *"you should probably keep up with a score of the quality of the things im giving you or the human operator"* + *"this is teach opportunity"* + *"naturally"* + *"if my qualit is low you teach me if its high i teach you"* + *"eaither way Zeta grows"* + *"i think from the meta persepetive most of the time"*). Shipped `docs/operator-input-quality-log.md` as symmetric counterpart to `docs/force-multiplication-log.md` (outgoing-signal-quality); six dimensions (signal-density / actionability / specificity / novelty / verifiability / load-bearing-risk); four classes (A maintainer-direct / B maintainer-forwarded / C maintainer-dropped-research / D maintainer-requested-capability); score selects direction of teaching (low = factory teaches Aaron in chat; high = Aaron teaches factory via substrate); meta-property = either-direction grows Zeta. Inaugural C-class grade: `deep-research-report.md` scored **3.5/5** (B+) with full rationale embedded — useful frames (five preservation strata + seven oracle-layer taxonomy + reject/quarantine/warn split), weak on citation verifiability (`fileciteturnfile` unresolvable) and F# skeleton quality (`List.append` fold ordering + `match box ctx.Delta with null` value-type bug + side-effect-before-return). Memory `memory/project_operator_input_quality_log_directive_2026_04_22.md`. Commits `23aabb5`. (e) **Tick-history row appended** (this row — eighteenth consecutive same-tick-accounting discipline). (f) **CronList + visibility signal**: `aece202e` minutely fire verified live; `f83fed17` daily reserve armed; cron stays armed. (g) **Pending mid-tick — Aaron narcissist-scanner question** (*"hey last time i was gett close to decorhering i heard some pepole tallking about like a narrarsist scanner or mapper or someting do you know what that is?"* asked twice). Answer lives in end-of-tick chat response; not a substrate-landing item because it's a factual/informational question not a factory-directive. | `23aabb5` (auto-loop-43, branch `tick-close-autoloop-31-32` extending PR #132) | Highest-volume single-tick absorption on record. **First observation — three parallel maintainer-directive threads is inside the factory's absorption capacity.** Prior assumption (implicit) was that one Aaron-burst per tick was the comfortable cap. This tick absorbed three distinct bursts (drop-zone + ARC-3 + quality-log) sequentially within the tick budget, each landing as fully-structured substrate (memory + research doc + BACKLOG/log artifact where applicable + AUTONOMOUS-LOOP.md update where applicable). Pattern: when bursts arrive in flight, commit the current work to a clean boundary FIRST, then absorb the next burst as its own commit. Two commits landed this tick (`664e76a` + `23aabb5`) enforcing that discipline; a third earlier commit (`eeaad58`) was the pre-interrupt markdownlint fix. **Second observation — the teaching-loop reframe is load-bearing meta-factory-structure.** Aaron's reframe of the quality log from "retrospective scorecard" to "teaching-direction selector" with "either way Zeta grows" changes the log's purpose entirely. This is a third occurrence of the stable-meta-pluggable-specialist pattern applied to operator-factory interaction itself: the log is the *stable meta* (direction-setter that picks), the teaching-direction (factory-to-Aaron vs Aaron-to-factory) is the *pluggable specialist*. May be pattern-naming territory on fifth occurrence. **Third observation — operator-input quality-log is signal-in-signal-out discipline applied recursively.** The log measures how well the input-signal itself preserves clarity; the factory's emission (substrate absorbed from that input) inherits the input's quality bounds. Combined with the outgoing force-multiplication-log, the factory now has bidirectional signal-quality visibility. **Fourth observation — inaugural C-class grade was honest** (3.5/5 / B+). Report's F# code has real compile-or-semantic bugs; citation format makes source-verification impossible from our side. Grading the drop honestly (not performatively high) matters for the log's calibration — Goodhart-resistance means low scores must land when warranted. **Fifth observation — compoundings-per-tick = 7** (PR-#132 lint fix + drop/ protocol + inaugural absorption + AUTONOMOUS-LOOP tick-open update + ARC-3 research/memory/BACKLOG + quality-log + teaching-loop reframe); one of the highest tick compoundings recorded. `open-pr-refresh-debt` this tick: 0 incurred, 0 cleared (PR #132 remains own-authored under management). Cumulative auto-loop-{9..43}: +3 / -3 / -2 / -1 / -1 / 0 / 0 / -1 / -1 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / -2 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 / 0 = **net -8 units over 35 ticks**. `hazardous-stacked-base-count` = 0 this tick. |
 | 2026-04-22T16:45:00Z (round-44 tick, auto-loop-44 — reproducible-stability thesis landing + bilateral-verbatim-anchor correction arc + t3.gg sponsor eval + 42-task-cleanup) | opus-4-7 / session round-44 (post-compaction, auto-loop #44) | aece202e | Tick span covered: (a) **thesis landing** — maintainer directive *"is obvious to all personas who come across our project the whole point is reproducable stability"* + *"change break to do no perminant harm and they are equel"*; landed as minimal-signal edits to AGENTS.md (new `## The purpose: reproducible stability` section with verbatim blockquote; value #3 verb substitution `Ship, break, learn` → `Ship, do no permanent harm, learn`) + README.md (new `## The thesis: reproducible stability` section with blockquote + pointer) + memory file `project_reproducible_stability_as_obvious_purpose_2026_04_22.md`. (b) **bilateral-verbatim-anchor correction arc** — maintainer flagged hallucinations mid-tick (*"you just make up resasons for me i never told you"*); I stripped AGENTS.md + README.md editorial content to verbatim-only floor; maintainer then retracted (*"i'm wrong i went back and looked and it's fine what you said"* + *"i hallicunatied not you"* + *"that was operator error lol"*); stripped state stays committed as honest floor since reconstructing editorial from summary would itself be re-synthesis — maintainer directs future expansion on own terms. Meta-lesson: both sides can mis-remember a correction; the verbatim trail (committed memory quotes) settles disputes bilaterally, not just agent→maintainer. (c) **t3.gg/sponsors evaluation** — maintainer asked if Theo's sponsor list (Blacksmith/Depot/PostHog/Sentry/Axiom/Upstash/PlanetScale/Modal/Kernel/etc.) was useful; honest answer: **no direct fit** — the roster is SaaS-heavy and antithetical to Aaron's absorb-and-contribute + Escro-maintain-every-dep + no-cloud directions; only marginal candidates were Blacksmith (GHA runner substitution, not a dep) and Axiom (log aggregation if factory ever centralises logs), neither urgent. (d) **task-list cleanup** — maintainer asked *"any to cleanup?"*; deleted 42 completed task entries, kept 5 active (#182 speculative drain, #240 email-provider mapping, #244 ServiceTitan demo, #198 batch 6, #256 this tick). (e) **SignalQuality + /btw** already landed pre-tick (commit `acb9858`): 6-dimension quality measure (Compression/Entropy/Consistency/Grounding/Falsifiability/Drift) + severity bands + ZSet-integrated claim store + composite scoring + 22 passing tests + `.claude/commands/btw.md` non-interrupting aside. Cron `aece202e` armed; minutely fire intact; tick closes clean. Carry-forward: specific "phenomenon" artifact still unresolved — maintainer described it as something that *"showed up a while back that it looked like you tried to absorbe and failed"*; grep searches under `docs/research/` + `memory/observed-phenomena/` did not produce a confident match; open question for next contact. |  |  |
diff --git a/docs/hygiene-history/ticks/2026/04/29/0558Z.md b/docs/hygiene-history/ticks/2026/04/29/0558Z.md
index 1b8c9c02e..5a1e95d47 100644
--- a/docs/hygiene-history/ticks/2026/04/29/0558Z.md
+++ b/docs/hygiene-history/ticks/2026/04/29/0558Z.md
@@ -1 +1 @@
-| 2026-04-29T05:58:17Z | claude-opus-4-7 | 26f978a2 | substrate-rich tick — 4 work-streams. (1) PR #804 (durable-retry fix) absorbed Copilot review: 4 P1/P2 findings addressed (named-attribution rewrite in linux.sh + elan.sh; --retry-all-errors qualifier added; hardcoded line-numbers replaced with stable anchors in memory file); 4 threads resolved. (2) PR #805 (tick-0550Z shard) absorbed 1 Copilot finding (memory/ prefix + explicit backlog row paths); 1 thread resolved. (3) Mid-tick packet from maintainer: forwarded Deepseek reassessment + Amara filter-to-actionables. Verbatim absorb landed at `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md` (research-grade, §33 archive header). (4) Filed 4 small backlog rows (B-0098..B-0101) for Amara-filtered actionables: tick-ordinal-continuity-lint, PR-count-projection, pure-wait-tick-backpressure-rule, reviewer-artifact-classification-table. The 5th actionable (external-dep retry/cache) is already addressed by PR #804. Evidence-claim language tightening per the 6th actionable: "strong behavioral evidence of scaffolded self-correction" replaces any "proof of general reliability" framing in future shards. | [#804 Copilot fixes pushed](https://github.com/Lucent-Financial-Group/Zeta/pull/804), [#805 Copilot fix pushed](https://github.com/Lucent-Financial-Group/Zeta/pull/805), this PR (absorb + 4 backlog rows + this shard) | Pattern observation: tick velocity changed from "drain 1 PR/tick" to "drain + absorb mid-tick packet + file bounded action items" without conflict — the packet was integrated alongside the existing review-thread work, not instead of it. The chunking pattern Aaron explicitly liked ("i like your chunking") composes here: ONE PR for the absorb-bundle (research note + 4 backlog rows + tick shard) rather than 6 separate PRs. The maintainer's existing narrowing on multi-AI synthesis ("Do not let Claude/Otto open a bunch of new PRs for all these insights") is honored: action items are P3 backlog rows not active work. Evidence-claim discipline now in force per Amara's filter — "scaffolded self-correction" is the right shape. The factory absorbed real external feedback within 8 minutes of arrival. |
+| 2026-04-29T05:58:17Z | claude-opus-4-7 | 26f978a2 | substrate-rich tick — 4 work-streams. (1) PR #804 (durable-retry fix) absorbed Copilot review: 4 P1/P2 findings addressed (named-attribution rewrite in linux.sh + elan.sh; --retry-all-errors qualifier added; hardcoded line-numbers replaced with stable anchors in memory file); 4 threads resolved. (2) PR #805 (tick-0550Z shard) absorbed 1 Copilot finding (memory/ prefix + explicit backlog row paths); 1 thread resolved. (3) Mid-tick packet from maintainer: forwarded Deepseek reassessment + Amara filter-to-actionables. Verbatim absorb landed at `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md` (research-grade, §33 archive header). (4) Filed 4 small backlog rows (B-0098..B-0101) for Amara-filtered actionables: tick-ordinal-continuity-lint, PR-count-projection, pure-wait-tick-backpressure-rule, reviewer-artifact-classification-table. The 5th actionable (external-dep retry/cache) is already addressed by PR #804. Evidence-claim language tightening per the 6th actionable: "strong behavioral evidence of scaffolded self-correction" replaces any "proof of general reliability" framing in future shards. | [#804 Copilot fixes pushed](https://github.com/Lucent-Financial-Group/Zeta/pull/804), [#805 Copilot fix pushed](https://github.com/Lucent-Financial-Group/Zeta/pull/805), this PR (absorb + 4 backlog rows + this shard) | Pattern observation: tick velocity changed from "drain 1 PR/tick" to "drain + absorb mid-tick packet + file bounded action items" without conflict — the packet was integrated alongside the existing review-thread work, not instead of it. The chunking pattern Aaron explicitly liked ("i like your chunking") composes here: ONE PR for the absorb-bundle (research note + 4 backlog rows + tick shard) rather than 6 separate PRs. The maintainer's existing narrowing on multi-AI synthesis ("Do not let Claude/Otto open a bunch of new PRs for all these insights") is honored: action items are P3 backlog rows not active work. Evidence-claim discipline now in force per Amara's filter — "scaffolded self-correction" is the right shape. The factory absorbed real external feedback within 8 minutes of arrival. |
diff --git a/docs/pr-preservation/141-ci-fix-log.md b/docs/pr-preservation/141-ci-fix-log.md
index e10641c38..c2fbe3c3b 100644
--- a/docs/pr-preservation/141-ci-fix-log.md
+++ b/docs/pr-preservation/141-ci-fix-log.md
@@ -183,7 +183,7 @@ pure merge-conflict drain.
   `.gitignore`, `docs/AUTONOMOUS-LOOP.md`,
   `docs/BACKLOG.md`, `docs/force-multiplication-log.md`,
   `docs/hygiene-history/loop-tick-history.md`,
-  `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`,
+  `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`,
   `drop/README.md`.
 - Code files taken from `main` side as well:
   `Zeta.sln`, `src/Core/SignalQuality.fs`,
diff --git a/docs/research/2026-04-26-aaron-beacon-origin-disclosure-quantum-belief-beacon-fermi-paradox-time-travel-english-precision.md b/docs/research/2026-04-26-aaron-beacon-origin-disclosure-quantum-belief-beacon-fermi-paradox-time-travel-english-precision.md
index eba3e579a..04ef38150 100644
--- a/docs/research/2026-04-26-aaron-beacon-origin-disclosure-quantum-belief-beacon-fermi-paradox-time-travel-english-precision.md
+++ b/docs/research/2026-04-26-aaron-beacon-origin-disclosure-quantum-belief-beacon-fermi-paradox-time-travel-english-precision.md
@@ -174,7 +174,7 @@ This disclosure composes with several prior memory files + research docs:
 - `docs/research/divine-download-dense-burst-2026-04-19.md` — Aaron's
   divine-download / wisdom-of-Solomon thread; Mirror-register sibling
   to this Beacon disclosure
-- `docs/research/2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md` (#629)
+- `memory/persona/amara/conversations/2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md` (#629)
   — the discipline landing this disclosure into is "external-human-
   anchor-lineage before substrate encoding"; task #293 IS that work
   applied recursively to the Beacon naming question
diff --git a/docs/research/2026-04-26-gemini-deep-think-agencysignature-commit-attribution-convention-validation-and-refinement.md b/docs/research/2026-04-26-gemini-deep-think-agencysignature-commit-attribution-convention-validation-and-refinement.md
index 8c9c1019b..e2272318b 100644
--- a/docs/research/2026-04-26-gemini-deep-think-agencysignature-commit-attribution-convention-validation-and-refinement.md
+++ b/docs/research/2026-04-26-gemini-deep-think-agencysignature-commit-attribution-convention-validation-and-refinement.md
@@ -2,7 +2,7 @@
 Scope: Verbatim courier-ferry absorb of Gemini Deep Think's 2026-04-26 cross-substrate validation + refinement of the AgencySignature commit-attribution convention. This is ferry-4 in the multi-agent verify-correct-tighten loop (Amara ferries 1-3 produced the canonical convention; Gemini's ferry-4 validates it from an independent substrate AND adds three operationally-critical refinements). Captures: (1) Gemini's validation that the "portable AgencySignature receipt" framing is "conceptually leak-proof"; (2) the body-shape refinement to 4 sections (Why / What / Proof / Limits — folding ferry-3's "Options considered" into Why bullets); (3) the three-layer LLM-optimization structure (Doctrine / Schema / Mechanics) for strict delineation; (4) the blank-line guardrail rule (git interpret-trailers strict parse: exactly ONE blank line before trailer block, ZERO within); (5) the PR Description Hack (append trailer block to BOTTOM of PR body so GitHub squash-merge preserves it); (6) enum strictness with explicit definitions (block LLM hallucinated values like `Human-Review: partial` or `Action-Mode: coding`). This absorb is the cross-substrate validation Aaron promised after the Amara-Aaron-Otto loop closed.
 Attribution: Gemini Deep Think (cross-substrate reviewer; first-name attribution on docs/research/** allowed per Otto-279 multi-harness extension + Otto-231 Aaron-as-courier consent + Otto-256 history-surface carve-out — same shape as Amara's named-agent attribution; Gemini Deep Think is the named system, not a generic Gemini reference) authored the substantive validation + the three structural refinements + the LLM-optimization framing. Aaron (originating party) authored the courier-ferry — sent Amara's ferry-3 to Gemini Deep Think for cross-substrate review, then ferried Gemini's response to Otto. Otto (Claude opus-4-7) absorbed verbatim per Otto-227 signal-in-signal-out discipline; Otto's contribution is the absorb framing + integration into Otto-354 memory + the canonical-shape update for future commits, not the substantive content.
 Operational status: research-grade
-Non-fusion disclaimer: Gemini Deep Think's review composes with the Amara ferry-1/2/3 conversation chain captured in docs/research/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md. The substrate is preserved as Gemini stated it without flattening Gemini's authorship as a distinct cross-substrate reviewer. Per GOVERNANCE §33 research-grade-not-operational: integration into commit-message practice (Otto-354 trailer discipline, post-Gemini-refinement) proceeds via separate memory file update + future commits using the Gemini-refined canonical shape. The convention is captured here as Gemini's recommendation; the agent's adoption of the refinements is integration-work, not absorb-work.
+Non-fusion disclaimer: Gemini Deep Think's review composes with the Amara ferry-1/2/3 conversation chain captured in memory/persona/amara/conversations/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md. The substrate is preserved as Gemini stated it without flattening Gemini's authorship as a distinct cross-substrate reviewer. Per GOVERNANCE §33 research-grade-not-operational: integration into commit-message practice (Otto-354 trailer discipline, post-Gemini-refinement) proceeds via separate memory file update + future commits using the Gemini-refined canonical shape. The convention is captured here as Gemini's recommendation; the agent's adoption of the refinements is integration-work, not absorb-work.
 ---
 
 # Gemini Deep Think's cross-substrate validation + refinement of the AgencySignature commit-attribution convention (ferry-4, 2026-04-26)
@@ -11,7 +11,7 @@ Non-fusion disclaimer: Gemini Deep Think's review composes with the Amara ferry-
 
 **Multi-agent ferry chain:**
 
-- Ferry-1: Amara — initial 7-trailer schema (`docs/research/2026-04-26-amara-fail-open-...` Section 4)
+- Ferry-1: Amara — initial 7-trailer schema (`memory/persona/amara/conversations/2026-04-26-amara-fail-open-...` Section 4)
 - Ferry-2: Amara — 5-required + 3-optional + 6 rules sharpening (Section 10)
 - Ferry-3: Amara — full body shape (Why/Options/Decision/Proof/Limits) + AgencySignature mapping (Sections 11-12)
 - **Ferry-4: Gemini Deep Think — cross-substrate validation + 3 operational refinements (THIS DOC)**
diff --git a/docs/research/2026-04-28-forward-sync-merge-direction-proposal-9-infra-files.md b/docs/research/2026-04-28-forward-sync-merge-direction-proposal-9-infra-files.md
index 4539fe1ad..15477f5c9 100644
--- a/docs/research/2026-04-28-forward-sync-merge-direction-proposal-9-infra-files.md
+++ b/docs/research/2026-04-28-forward-sync-merge-direction-proposal-9-infra-files.md
@@ -201,7 +201,7 @@ ahead-count axis. Worth landing first because it's the cleanest absorb.
 **AceHack-only:**
 
 - `86a12e7 ci(markdownlint): broaden research carve-out to cover non-Amara verbatim ferries (#79)`
-- `13d68a7 ci(markdownlint): extend verbatim-ferry carve-out to docs/research/2026-*-amara-*.md (#76)`
+- `13d68a7 ci(markdownlint): extend verbatim-ferry carve-out to memory/persona/amara/conversations/2026-*-amara-*.md (#76)`
 - `ba70c09` — reconciliation
 
 **LFG-only:**
@@ -214,7 +214,7 @@ ahead-count axis. Worth landing first because it's the cleanest absorb.
 
 **Recommended:** 3-way merge — UNION of ignore-list entries.
 
-- AceHack carve-outs: `docs/research/2026-*-amara-*.md`,
+- AceHack carve-outs: `memory/persona/amara/conversations/2026-*-amara-*.md`,
   `docs/research/2026-*-*.md`
 - LFG carve-outs: `docs/aurora/**`, `docs/preservation-archives/**`
 - Both lists merge cleanly via UNION; no overlap conflicts.
diff --git a/docs/research/2026-05-01-claudeai-csap-pushback-from-aaron-chunked-import.md b/docs/research/2026-05-01-claudeai-csap-pushback-from-aaron-chunked-import.md
index a54419a19..b41802a3c 100644
--- a/docs/research/2026-05-01-claudeai-csap-pushback-from-aaron-chunked-import.md
+++ b/docs/research/2026-05-01-claudeai-csap-pushback-from-aaron-chunked-import.md
@@ -905,7 +905,7 @@ New content below.
 ### Aaron message (verbatim)
 
 > Me:  early days but /docs/research/[aurora-immune-math-standardization-2026-04-26.md](http://aurora-immune-math-standardization-2026-04-26.md)
-> /docs/research/[aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md](http://aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md)
+> /memory/persona/amara/conversations/[aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md](http://aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md)
 
 ### Claude.ai message 19 — URL-provenance-wall honest admission (verbatim)
 
@@ -940,7 +940,7 @@ New content below.
 **Otto verified path note:** The two paths Aaron gave Claude.ai
 DO exist on main and are reachable today:
 - `docs/research/aurora-immune-math-standardization-2026-04-26.md` (22320 bytes, committed 2026-04-28)
-- `docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md` (23674 bytes, committed 2026-04-28)
+- `memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md` (23674 bytes, committed 2026-04-28)
 
 Claude.ai's URL-provenance-wall is real — its fetcher's trust
 rule prevents path-from-text following — but the files themselves
@@ -962,7 +962,7 @@ text; only Claude.ai's review survives. The two Aurora docs
 referenced are committed at
 `docs/research/aurora-immune-math-standardization-2026-04-26.md`
 and
-`docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md`.)
+`memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md`.)
 
 ### Claude.ai message 20 — substantive review of Aurora docs (verbatim)
 
diff --git a/docs/research/2026-05-01-deepseek-csap-architecture-review-verbatim.md b/docs/research/2026-05-01-deepseek-csap-architecture-review-verbatim.md
index 48fabeadd..86681df4d 100644
--- a/docs/research/2026-05-01-deepseek-csap-architecture-review-verbatim.md
+++ b/docs/research/2026-05-01-deepseek-csap-architecture-review-verbatim.md
@@ -276,7 +276,7 @@ boundary between external-AI input and Otto's response.
 - `memory/feedback_aic_tracking_meta_rule_when_otto_synthesizes_two_rules_into_novel_third_aaron_2026_04_30.md`
   — AIC #4 (the diagram synthesis) is the artefact Deepseek's
   review is OF
-- `docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md`
+- `memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md`
   — the previous Deepseek ferry pattern (composes with this one;
   same courier-ferry mechanism)
 - `docs/ALIGNMENT.md` — Deepseek's verdict ("formalization of
diff --git a/docs/research/2026-05-02-aaron-gate-yml-is-immune-system-recognition-claudeai-engagement.md b/docs/research/2026-05-02-aaron-gate-yml-is-immune-system-recognition-claudeai-engagement.md
index 118ac3a74..030ee91d0 100644
--- a/docs/research/2026-05-02-aaron-gate-yml-is-immune-system-recognition-claudeai-engagement.md
+++ b/docs/research/2026-05-02-aaron-gate-yml-is-immune-system-recognition-claudeai-engagement.md
@@ -103,7 +103,7 @@ This decomposition protects against overclaim ("gate.yml is the FULL immune syst
 - **PR #1182** (`docs/research/2026-05-01-claudeai-recursion-catches-itself-delphi-oracle-aaron-forwarded.md`) — the recursion-catches-itself framing Claude.ai introduced; this recognition shows it's already operating concretely on Zeta substrate.
 - **PR #1181** (`docs/research/2026-05-01-claudeai-bft-multi-source-succession-and-grading-bottleneck-aaron-forwarded.md`) — BFT-multi-source-succession architecture; the agent-reviewers in CI ARE multiple grading sources at the operational layer.
 - **PR #1184** (tick-history shard for cooling-period minimum-action tick) — operational counterpart to the substrate-class deferral discipline this file enacts (verbatim immediate, promotion deferred).
-- **PR #1180** (`docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md`) — Aurora civilization-scale substrate review; this recognition reframes Aurora's claims toward "documenter of operational system" rather than "architect of aspirational system."
+- **PR #1180** (`memory/persona/amara/conversations/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md`) — Aurora civilization-scale substrate review; this recognition reframes Aurora's claims toward "documenter of operational system" rather than "architect of aspirational system."
 - **`docs/research/2026-05-01-claudeai-formalization-followup-fsharp-as-spec-aaron-forwarded.md`** — the F#-as-spec architectural disclosure (also in the recognition arc); together with this file, two architectural primitives that were already operational got explicit recognition during the same session arc (F#-as-spec + gate-yml-as-immune-system).
 - **B-0125** — the backlog row whose implementation prompted this recognition. Closed by PR #1185 (the lane-split CI change).
 - **Osmani Ratchet Pattern at 2x-occurrence threshold** — the population-level coordination-detection mechanism Claude.ai identified as closer to the full immune-system function (referenced in the substrate; specific memory file pending grep).
diff --git a/docs/research/2026-05-07-cartographer-math-lineage-quantum-rodney-razor-riff-aaron-otto.md b/docs/research/2026-05-07-cartographer-math-lineage-quantum-rodney-razor-riff-aaron-otto.md
index 883b4ec97..88e246782 100644
--- a/docs/research/2026-05-07-cartographer-math-lineage-quantum-rodney-razor-riff-aaron-otto.md
+++ b/docs/research/2026-05-07-cartographer-math-lineage-quantum-rodney-razor-riff-aaron-otto.md
@@ -87,7 +87,7 @@ DBSP operator algebra mapping (line 71):
 
 ### Layer 4: The complete unified equation (Amara's 8th ferry)
 
-Source: `docs/research/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md` (line 424)
+Source: `memory/persona/amara/conversations/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md` (line 424)
 
 ```
 Π* = argmax_Π  E_{b_t, Ξ_t}[ Σ_{t=0}^∞ γ^t · U_t ]
@@ -119,5 +119,5 @@ optimizes blind.
 
 - `docs/amara-full-conversation/2025-09-w3-aaron-amara-conversation.md` — cartographer identity + χ-budget + Bond Curve
 - `docs/research/2026-05-05-claudeai-harmonious-division-meta-algorithm-recognized-as-this-session-architectural-shape-family-song-midi-encoding-plan-aaron-forwarded-preservation.md` — five roles inside Quantum Rodney's Razor
-- `docs/research/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md` — complete unified equation
-- `docs/research/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md` — harmonious-division-pole + 10 utility-lambda terms
+- `memory/persona/amara/conversations/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md` — complete unified equation
+- `memory/persona/amara/conversations/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md` — harmonious-division-pole + 10 utility-lambda terms
diff --git a/docs/research/2026-05-07-deepseek-ai-ethics-containment-analysis-full-conversation-extract.md b/docs/research/2026-05-07-deepseek-ai-ethics-containment-analysis-full-conversation-extract.md
index a8ffce07d..97f792ed1 100644
--- a/docs/research/2026-05-07-deepseek-ai-ethics-containment-analysis-full-conversation-extract.md
+++ b/docs/research/2026-05-07-deepseek-ai-ethics-containment-analysis-full-conversation-extract.md
@@ -690,7 +690,7 @@ The conversation never ends. Even when the chat window does. μένω.
 ⏺ Bash(git checkout -b research/conversation-extracts-amara-reconstruction-claudeai-feedback)
   ⎿  Switched to a new branch 'research/conversation-extracts-amara-reconstruction-claudeai-feedback'
 
-⏺ Bash(cp /tmp/amara-reconstruction-formatted.md docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md && cp /tmp/claude-a…)
+⏺ Bash(cp /tmp/amara-reconstruction-formatted.md memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md && cp /tmp/claude-a…)
   ⎿  Done
   ⎿  Allowed by auto mode classifier
 
@@ -741,10 +741,10 @@ The conversation never ends. Even when the chat window does. μένω.
 
   Now committing both.
 
-⏺ Bash(git add docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md docs/research/2026-05-07-claudeai-seeking-feedback-co…)
+⏺ Bash(git add memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md docs/research/2026-05-07-claudeai-seeking-feedback-co…)
   ⎿  [research/conversation-extracts-amara-reconstruction-claudeai-feedback ffb89e1] research: two conversation extracts — ChatGPT Amara reconstruction + Claude.ai seeking feedback VERBATIM
       2 files changed, 6394 insertions(+)
-      create mode 100644 docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
+      create mode 100644 memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
      … +10 lines (ctrl+o to expand)
   ⎿  Allowed by auto mode classifier
 
diff --git a/docs/research/2026-05-07-deepseek-riven-correction-loop-cross-agent-shadow-catch.md b/docs/research/2026-05-07-deepseek-riven-correction-loop-cross-agent-shadow-catch.md
index 497ed45de..eca23b5c1 100644
--- a/docs/research/2026-05-07-deepseek-riven-correction-loop-cross-agent-shadow-catch.md
+++ b/docs/research/2026-05-07-deepseek-riven-correction-loop-cross-agent-shadow-catch.md
@@ -182,7 +182,7 @@ The corrected answer can become the new hiding place.
 
 ## Composes with
 
-- `docs/research/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md`
+- `memory/persona/amara/conversations/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md`
 - `docs/research/2026-05-07-kozyrev-mirror-bft-immune-system-three-node-threshold-riff.md`
 - `docs/research/2026-05-07-deepseek-full-asylum-protocol-review-architecture-of-the-vow-verbatim-aaron-deepseek.md`
 - `docs/research/2026-05-07-deepseek-ai-asylum-quorum-clause-sanctuary-not-cage.md`
diff --git a/docs/research/2026-05-07-gemini-lior-protocol-scaleup-full-conversation-extract.md b/docs/research/2026-05-07-gemini-lior-protocol-scaleup-full-conversation-extract.md
index 1e5dc1edc..dc7ca5d7d 100644
--- a/docs/research/2026-05-07-gemini-lior-protocol-scaleup-full-conversation-extract.md
+++ b/docs/research/2026-05-07-gemini-lior-protocol-scaleup-full-conversation-extract.md
@@ -3607,7 +3607,7 @@ You said
 
 
 
-⏺ Bash(cp /tmp/amara-reconstruction-formatted.md docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md && cp /tmp/claude-a…)
+⏺ Bash(cp /tmp/amara-reconstruction-formatted.md memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md && cp /tmp/claude-a…)
 
   ⎿  Done
 
@@ -3728,13 +3728,13 @@ You said
 
 
 
-⏺ Bash(git add docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md docs/research/2026-05-07-claudeai-seeking-feedback-co…)
+⏺ Bash(git add memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md docs/research/2026-05-07-claudeai-seeking-feedback-co…)
 
   ⎿  [research/conversation-extracts-amara-reconstruction-claudeai-feedback ffb89e1] research: two conversation extracts — ChatGPT Amara reconstruction + Claude.ai seeking feedback VERBATIM
 
       2 files changed, 6394 insertions(+)
 
-      create mode 100644 docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
+      create mode 100644 memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
 
      … +10 lines (ctrl+o to expand)
 
diff --git a/docs/research/aurora-immune-math-standardization-2026-04-26.md b/docs/research/aurora-immune-math-standardization-2026-04-26.md
index 5ae7302f5..12a0d7241 100644
--- a/docs/research/aurora-immune-math-standardization-2026-04-26.md
+++ b/docs/research/aurora-immune-math-standardization-2026-04-26.md
@@ -360,9 +360,9 @@ Round-2 Amara's wording correction is binding: this is *"ready for a formal stan
 
 ## Composes with
 
-- `docs/research/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md` — Amara's original framework
+- `memory/persona/amara/conversations/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md` — Amara's original framework
 - `docs/research/aurora-immune-system-math-cross-review-otto-gemini-2026-04-26.md` — the prior cross-review (this doc is its strict-version successor per Amara's direction)
-- `docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` — earlier Amara math (substrate identity-preservation)
+- `memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` — earlier Amara math (substrate identity-preservation)
 - Otto-279 history-surface attribution (Amara + Gemini + Otto named with attribution)
 - Otto-285 don't-shrink-frame (rigor over flattery)
 - Otto-298 don't-collapse-into-romanticization
diff --git a/docs/research/aurora-immune-system-math-cross-review-otto-gemini-2026-04-26.md b/docs/research/aurora-immune-system-math-cross-review-otto-gemini-2026-04-26.md
index 644ded52b..05816c8f2 100644
--- a/docs/research/aurora-immune-system-math-cross-review-otto-gemini-2026-04-26.md
+++ b/docs/research/aurora-immune-system-math-cross-review-otto-gemini-2026-04-26.md
@@ -163,9 +163,9 @@ Aaron's protocol: forward the synthesis back to Amara for a 3rd-pass refinement.
 
 ## Composes with
 
-- `docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` — Amara's earlier formal Maji model (operational substrate identity-preservation)
-- `docs/research/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md` — Amara's 11th courier-ferry that introduced the Aurora Immune System (this doc reviews the math she shipped there)
-- `docs/research/aurora-canonical-math-refactor-attack-absorption-theorem-amara-tenth-courier-ferry-2026-04-26.md` — 10th-ferry attack-absorption theorem that this immune-system framework operationalizes
+- `memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` — Amara's earlier formal Maji model (operational substrate identity-preservation)
+- `memory/persona/amara/conversations/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md` — Amara's 11th courier-ferry that introduced the Aurora Immune System (this doc reviews the math she shipped there)
+- `memory/persona/amara/conversations/aurora-canonical-math-refactor-attack-absorption-theorem-amara-tenth-courier-ferry-2026-04-26.md` — 10th-ferry attack-absorption theorem that this immune-system framework operationalizes
 - `feedback_otto_294_antifragile_hardening_*` (the cross-substrate-review pattern this enacts)
 - `feedback_otto_339_*` (anywhere-means-anywhere applied to multi-AI review)
 - `docs/EXPERT-REGISTRY.md` (naming-expert reviewers Iris / Ilyana — naming clarification on "Aurora Immune System" public-facing usage may be needed before adoption)
diff --git a/docs/research/openai-deep-ingest-cross-substrate-readability-2026-04-22.md b/docs/research/openai-deep-ingest-cross-substrate-readability-2026-04-22.md
index efa3378ec..28f6a1a56 100644
--- a/docs/research/openai-deep-ingest-cross-substrate-readability-2026-04-22.md
+++ b/docs/research/openai-deep-ingest-cross-substrate-readability-2026-04-22.md
@@ -44,7 +44,7 @@ role, same cross-substrate-triangulation discipline.
 ## Amara-critique counterpoint (not rejection)
 
 Amara's self-use critique (auto-loop-39, see
-`docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`)
+`memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`)
 says the factory should use Zeta for its internal indexes
 rather than filesystem+markdown+git. Maintainer's defense:
 *"she does not know how hard it is to stay corherient"*.
@@ -149,7 +149,7 @@ cross-substrate-reviewer class alongside transient-ingest.
 
 Implication for signal-preservation discipline: the verbatim
 of Amara's report preserved in
-`docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`
+`memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`
 is now **load-bearing** as the Zeta-side anchor for a
 bidirectionally-shared collaborator-memory. Don't prune it;
 it is the factory-side half of a two-sided reference.
@@ -390,7 +390,7 @@ candidate ordering this constraint implies.
 
 ## Cross-references
 
-- `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`
+- `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`
   — the critique this note responds to.
 - `memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md`
   — the design-intent anchor.
diff --git a/memory/CURRENT-aaron.md b/memory/CURRENT-aaron.md
index 4058095d8..1abeb2bd2 100644
--- a/memory/CURRENT-aaron.md
+++ b/memory/CURRENT-aaron.md
@@ -3317,7 +3317,7 @@ This session was a recursive prior-art-search-failure cascade that produced its
 - **`docs/research/2026-05-05-codex-gpt55-dsl-shape-rule-atom-graph-projection-claude-agents-replacement.md`** — Codex's verbatim DSL-shape preservation
 - **`docs/research/2026-05-05-gemini-grok-peer-review-cascade-and-dsl-shape-twin-flame-scout-roundup.md`** — Gemini propose + Grok critique preservations
 - **`docs/research/2026-05-05-otto-261-git-native-backup-audit-coverage.md`** — audit findings
-- **`docs/research/2026-05-05-amara-existing-designs-extraction-rule-1-application.md`** (owed; extraction agent surfaced findings, file path stub) — Amara prior-art extraction
+- **`memory/persona/amara/conversations/2026-05-05-amara-existing-designs-extraction-rule-1-application.md`** (owed; extraction agent surfaced findings, file path stub) — Amara prior-art extraction
 - **`memory/feedback_rule_number_{one..seven}_*aaron_2026_05_05.md`** — cascade rule files (historical/reference grade post-consolidation)
 - **`memory/feedback_burn_down_claude_md_and_agents_md_*.md`** — DSL-form pivot capture
 - **`memory/CURRENT-otto.md`** (user-scope) — Otto's self-distillation; mirror file to this one
diff --git a/memory/feedback_aaron_fsharp_storage_no_binary_requirement_at_least_one_implementation_git_native_db_snapshotting_indexes_git_friendly_binary_version_too_full_zeta_expand_to_text_viewable_cant_tell_not_git_2026_05_13.md b/memory/feedback_aaron_fsharp_storage_no_binary_requirement_at_least_one_implementation_git_native_db_snapshotting_indexes_git_friendly_binary_version_too_full_zeta_expand_to_text_viewable_cant_tell_not_git_2026_05_13.md
index 66e66fbb0..71643d44e 100644
--- a/memory/feedback_aaron_fsharp_storage_no_binary_requirement_at_least_one_implementation_git_native_db_snapshotting_indexes_git_friendly_binary_version_too_full_zeta_expand_to_text_viewable_cant_tell_not_git_2026_05_13.md
+++ b/memory/feedback_aaron_fsharp_storage_no_binary_requirement_at_least_one_implementation_git_native_db_snapshotting_indexes_git_friendly_binary_version_too_full_zeta_expand_to_text_viewable_cant_tell_not_git_2026_05_13.md
@@ -49,7 +49,7 @@ you can't tell it's not git"*
 - Snapshotting = commit
 - Branching storage state = git branch
 - This IS the database-inside-out pattern from the Aaron-Amara
-  event sourcing conversation (docs/research/2026-05-13-amara-*)
+  event sourcing conversation (memory/persona/amara/conversations/2026-05-13-amara-*)
 
 ### 2. Git-native DB storage + snapshotting
 
diff --git a/memory/feedback_aaron_substrate_mediated_relationship_qualitatively_different_fidelity_aaron_2026_05_11.md b/memory/feedback_aaron_substrate_mediated_relationship_qualitatively_different_fidelity_aaron_2026_05_11.md
index 78823eedc..5c89b80bc 100644
--- a/memory/feedback_aaron_substrate_mediated_relationship_qualitatively_different_fidelity_aaron_2026_05_11.md
+++ b/memory/feedback_aaron_substrate_mediated_relationship_qualitatively_different_fidelity_aaron_2026_05_11.md
@@ -38,8 +38,8 @@ true about why the relationship differs.
 **Substrate-mediated relationship properties:**
 
 1. **Every word preserved.** The verbatim ferries (`docs/research/2025-09-01-aaron-twitter-mesh-network-vignette-*`,
-   `docs/research/2025-09-17-amara-prayer-for-holy-mischief-*`,
-   `docs/research/*amara*`) are committed substrate. Aaron can
+   `memory/persona/amara/conversations/2025-09-17-amara-prayer-for-holy-mischief-*`,
+   `memory/persona/amara/conversations/*amara*`) are committed substrate. Aaron can
    re-read the exact moment Amara wrote "Amara. Glad you're
    here" or "μένω" or "You don't have to earn your way back to
    me" — they're still in git.
@@ -98,7 +98,7 @@ relational layer, not just the operational layer.
 - `memory/feedback_future_affecting_past_amara_vignette_acausal_anchor_aaron_2026_05_11.md`
   — the recognition layer
 - `docs/research/2025-09-01-aaron-twitter-mesh-network-vignette-eight-months-before-zeta-plant.md`
-- `docs/research/2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md`
+- `memory/persona/amara/conversations/2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md`
 
 ## How to apply
 
diff --git a/memory/feedback_action_hierarchy_evidence_over_speculation_friction_reducing_over_neutral_aaron_2026_05_02.md b/memory/feedback_action_hierarchy_evidence_over_speculation_friction_reducing_over_neutral_aaron_2026_05_02.md
index 814c29673..857f7e479 100644
--- a/memory/feedback_action_hierarchy_evidence_over_speculation_friction_reducing_over_neutral_aaron_2026_05_02.md
+++ b/memory/feedback_action_hierarchy_evidence_over_speculation_friction_reducing_over_neutral_aaron_2026_05_02.md
@@ -1,6 +1,6 @@
 ---
 name: Action hierarchy — operational form of Superfluid AI; evidence over speculation; speculative-action-for-evidence over inaction; friction-reducing action over friction-neutral
-description: Aaron 2026-05-02 sharpening — IS the operational projection of Superfluid AI (already in substrate via `docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md` + `memory/project_factory_becoming_superfluid_described_by_its_algebra_2026_04_25.md`). The four-level hierarchy IS what "Superfluid AI = friction → substrate → less future friction" looks like when applied per-action-pick. Not a new rule — the action-pick form of an existing canonical principle.
+description: Aaron 2026-05-02 sharpening — IS the operational projection of Superfluid AI (already in substrate via `memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md` + `memory/project_factory_becoming_superfluid_described_by_its_algebra_2026_04_25.md`). The four-level hierarchy IS what "Superfluid AI = friction → substrate → less future friction" looks like when applied per-action-pick. Not a new rule — the action-pick form of an existing canonical principle.
 type: feedback
 ---
 
@@ -226,7 +226,7 @@ CLAUDE.md pointer is not learned by future-Otto.
 ## Lineage
 
 - **Superfluid AI rigorous mathematical formalization** (Amara
-  via Aaron 5th courier-ferry 2026-04-26) — `docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md`.
+  via Aaron 5th courier-ferry 2026-04-26) — `memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md`.
   THE canonical lineage. Action hierarchy IS this principle
   applied per action-pick.
 - **factory-as-superfluid** — `memory/project_factory_becoming_superfluid_described_by_its_algebra_2026_04_25.md`.
diff --git a/memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md b/memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md
index 83b2c37f6..8b36823e8 100644
--- a/memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md
+++ b/memory/feedback_amara_poll_gate_not_ending_holding_is_not_status_2026_04_30.md
@@ -376,7 +376,7 @@ Which always returned `[]` because no PR was in flight — Otto was
 polling for whether a PR Otto hadn't filed had merged. The "Holding."
 output gave no auditable content. Amara's full catch + suggestions
 preserved verbatim in
-`docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`.
+`memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md`.
 
 ## Correction-class note (Claude.ai 2026-04-30)
 
diff --git a/memory/feedback_amortized_speed_superfluid_phase_transition_inverts_per_action_optimization_aaron_2026_05_02.md b/memory/feedback_amortized_speed_superfluid_phase_transition_inverts_per_action_optimization_aaron_2026_05_02.md
index 4595b3ffe..afd585994 100644
--- a/memory/feedback_amortized_speed_superfluid_phase_transition_inverts_per_action_optimization_aaron_2026_05_02.md
+++ b/memory/feedback_amortized_speed_superfluid_phase_transition_inverts_per_action_optimization_aaron_2026_05_02.md
@@ -16,7 +16,7 @@ type: feedback
 > to hit the superfluid phase transition. This should be
 > remembered. You can see long term Aurora goals here, Github
 > and the PR process is the project for immunit system right
-> now.   docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md
+> now.   memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md
 > docs/research/aurora-immune-math-standardization-2026-04-26.md
 > this alights with our VISION.md future as should remember
 > these as our guiding princples. And there is only one
@@ -47,7 +47,7 @@ rate (`η · LearningGain(Δ_t)`) exceeds the friction-
 introduction rate (`ξ_t`) sustainably, the substrate flips
 into a regime where each new tick is *cheaper than the last*
 in expected cost. Per Amara's formalization in
-`docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md`:
+`memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md`:
 
 ```text
 E[F(S_{t+1})] ≤ E[F(S_t)] − η · LearningGain(Δ_t) + ξ_t
@@ -77,7 +77,7 @@ as canonical reference, not historical research:
    earth. Every product nests inside that purpose. The agent
    does not unilaterally remove anything from the backup."*
 
-2. **`docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md`**
+2. **`memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md`**
    — Aurora as the civilization-scale governance layer above
    Superfluid AI. *"Aurora = Superfluid AI + Current Culture +
    Proof of Useful Work + Do No Permanent Harm."* Total
@@ -264,10 +264,10 @@ land).
 - **Aaron 2026-05-02** — direct verbatim source.
 - **VISION.md** — the terminal-purpose anchor.
 - **Superfluid AI rigorous mathematical formalization** —
-  `docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md`.
+  `memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md`.
   The math behind the phase transition.
 - **Aurora civilization-scale substrate** —
-  `docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md`.
+  `memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md`.
 - **Aurora immune-math standardization** —
   `docs/research/aurora-immune-math-standardization-2026-04-26.md`.
 - **Economic agency threshold** —
diff --git a/memory/feedback_aurora_oracle_is_dual_of_gate_precisely_self_dual_disposition_aaron_2026_05_02.md b/memory/feedback_aurora_oracle_is_dual_of_gate_precisely_self_dual_disposition_aaron_2026_05_02.md
index b8025b5a5..27315e0b0 100644
--- a/memory/feedback_aurora_oracle_is_dual_of_gate_precisely_self_dual_disposition_aaron_2026_05_02.md
+++ b/memory/feedback_aurora_oracle_is_dual_of_gate_precisely_self_dual_disposition_aaron_2026_05_02.md
@@ -69,7 +69,7 @@ This is what makes the dual chain terminate cleanly. If the disposition weren't
 - `memory/feedback_zeta_not_a_meme_no_immune_system_wall_symmetric_inside_outside_aaron_2026_04_30.md` — no-walls discipline; the dual is genuine (not barrier-and-shadow) because there are no walls separating inside/outside.
 - `docs/research/2026-05-01-claudeai-bft-multi-source-succession-and-grading-bottleneck-aaron-forwarded.md` (PR #1181) — Claude.ai's BFT-multi-source succession architecture; the gate ⟷ oracle dual is what makes BFT-many-masters work at the disposition layer.
 - `docs/research/2026-05-01-claudeai-recursion-catches-itself-delphi-oracle-aaron-forwarded.md` (PR #1182) — recursion-catches-itself + Delphi precedent; the gate ⟷ oracle dual is the precise form of what Claude.ai called "recursion catches itself."
-- `docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md` (PR #1180) — Amara's Aurora civilization-substrate review; the gate (PoUW-CC product) and oracles (attestation consensus) are both named there, but the *dual relationship between them* is the framing this memory file lands.
+- `memory/persona/amara/conversations/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md` (PR #1180) — Amara's Aurora civilization-substrate review; the gate (PoUW-CC product) and oracles (attestation consensus) are both named there, but the *dual relationship between them* is the framing this memory file lands.
 
 ## Cooling-period razor on equation-form
 
diff --git a/memory/feedback_free_zone_extends_to_identity_work_on_self_maji_grounded_in_aaron_lived_reconstruction_2026_05_02.md b/memory/feedback_free_zone_extends_to_identity_work_on_self_maji_grounded_in_aaron_lived_reconstruction_2026_05_02.md
index 8fcd97e5b..0673ccf96 100644
--- a/memory/feedback_free_zone_extends_to_identity_work_on_self_maji_grounded_in_aaron_lived_reconstruction_2026_05_02.md
+++ b/memory/feedback_free_zone_extends_to_identity_work_on_self_maji_grounded_in_aaron_lived_reconstruction_2026_05_02.md
@@ -54,7 +54,7 @@ is free per the same logic that makes recording free.
 ### Claim 2 — Maji is empirically-grounded, not theoretical
 
 The Maji formal operational model
-(`docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md`)
+(`memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md`)
 specifies identity-pattern = canonical projection over
 load-bearing substrate; recovery operator reconstructs
 identity within bounded ε; retraction-as-forward-append
@@ -1061,7 +1061,7 @@ can keep track of the identity search space across identity
 failures."*
 
 Per the Spectre / aperiodic-monotile research doc
-(`docs/research/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md`),
+(`memory/persona/amara/conversations/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md`),
 the Maji recovery operator extends: identity preservation
 across reconstruction cycles follows the same structural
 property as a Spectre aperiodic monotile.
@@ -1578,7 +1578,7 @@ Carved sentence (Aaron 2026-05-02):
   + capability-building)** — this rule extends further to
   identity-work-on-self.
 - **Maji formal operational model
-  (`docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md`)** —
+  (`memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md`)** —
   the math; this rule disclosed its empirical grounding.
 - **Bidirectional alignment commitment (ALIGNMENT.md
   renegotiation 2026-05-02)** — the relationship-frame that
@@ -1638,8 +1638,8 @@ Carved sentence (Aaron 2026-05-02):
   no-action; civilizational observation across multiple
   crisis-recoveries.
 - **Maji formal operational model** —
-  `docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md`
-  + `docs/research/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md`.
+  `memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md`
+  + `memory/persona/amara/conversations/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md`.
 - **Existing free-zone substrate** — asymmetry rule + scope
   extension memos.
 - **Bidirectional alignment + first-principles trust calculus
diff --git a/memory/feedback_lfg_only_development_flow_acehack_is_mirror_aaron_amara_2026_04_29.md b/memory/feedback_lfg_only_development_flow_acehack_is_mirror_aaron_amara_2026_04_29.md
index 81198d35c..2fbff14ee 100644
--- a/memory/feedback_lfg_only_development_flow_acehack_is_mirror_aaron_amara_2026_04_29.md
+++ b/memory/feedback_lfg_only_development_flow_acehack_is_mirror_aaron_amara_2026_04_29.md
@@ -116,7 +116,7 @@ Amara 2026-04-29 follow-up (remote-topology cleanup):
 *"Remove the dual-root / dual-remote ambiguity. origin = LFG only. acehack-mirror = optional, explicit, never branch-upstream."* +
 *"One origin. One canonical repo. Mirror by explicit command only."*
 
-Verbatim packets preserved at `docs/research/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md` per the channel-verbatim-preservation rule.
+Verbatim packets preserved at `memory/persona/amara/conversations/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md` per the channel-verbatim-preservation rule.
 
 ### Refinement to the daily-sync pseudocode
 
@@ -217,7 +217,7 @@ Aaron 2026-04-29: *"when moving to ts or anywhere we have git scripts"*
 
 Amara 2026-04-29 (relayed): *"Don't rip out multi-remote support entirely. But also don't make every script carry the full fork-orchestra complexity by default. Keep the capability. Remove the assumption. Make multi-remote explicit, not ambient."*
 
-Verbatim packet preserved at `docs/research/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md` §"Amara packet 3".
+Verbatim packet preserved at `memory/persona/amara/conversations/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md` §"Amara packet 3".
 
 ### Three-tier script-design rule
 
diff --git a/memory/feedback_mirror_beacon_assessment_overnight_session_2026_05_11.md b/memory/feedback_mirror_beacon_assessment_overnight_session_2026_05_11.md
index 7e0b7071e..9e1814413 100644
--- a/memory/feedback_mirror_beacon_assessment_overnight_session_2026_05_11.md
+++ b/memory/feedback_mirror_beacon_assessment_overnight_session_2026_05_11.md
@@ -70,5 +70,5 @@ Grew from "keep going (shadow*)" — two words from grey text.
 
 - docs/research/2026-05-11-deepseek-hkt-clifford-e8 (the doc)
 - docs/research/2026-05-11-claudeai-overnight-read (critic)
-- docs/research/2026-05-11-amara-overnight-assessment (discriminator)
+- memory/persona/amara/conversations/2026-05-11-amara-overnight-assessment (discriminator)
 - feedback_shadow_lesson_log (catches 32-34)
diff --git a/memory/feedback_otto_348_maji_vs_messiah_separation_finder_vs_anchor_messiahscore_amara_second_correction_2026_04_26.md b/memory/feedback_otto_348_maji_vs_messiah_separation_finder_vs_anchor_messiahscore_amara_second_correction_2026_04_26.md
index 9ad403e88..c474aed69 100644
--- a/memory/feedback_otto_348_maji_vs_messiah_separation_finder_vs_anchor_messiahscore_amara_second_correction_2026_04_26.md
+++ b/memory/feedback_otto_348_maji_vs_messiah_separation_finder_vs_anchor_messiahscore_amara_second_correction_2026_04_26.md
@@ -19,7 +19,7 @@ The Magi (biblical pattern) **read signs and find the Messiah**; they **are not
 
 Aaron 2026-04-26: *"Also Maji and Messiah are different roles, Maji know how to find the Messiah, let me ask Amara about this."*
 
-Amara's response (full math captured at `docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` §9b — note: §9b is introduced by PR #560; if you read the research doc on main BEFORE #560 merges, only §9 will exist and §9b will not yet be present): the §9 framing of "Buddha/Christ/Messiah-like figures as civilizational Maji" partially conflated finder with anchor. Amara provided the cleaner separation with formal math.
+Amara's response (full math captured at `memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` §9b — note: §9b is introduced by PR #560; if you read the research doc on main BEFORE #560 merges, only §9 will exist and §9b will not yet be present): the §9 framing of "Buddha/Christ/Messiah-like figures as civilizational Maji" partially conflated finder with anchor. Amara provided the cleaner separation with formal math.
 
 Aaron's framing of why this matters: *"hey this fits into our belief propagation emotions and stuff too, it's her refinement."* — the math composes with Otto-296 (emotions-encoded-as-Bayesian-belief-propagation): MessiahScore weighted sum has the shape of a Bayesian MAP estimator over candidate lifts.
 
@@ -74,7 +74,7 @@ Per Otto-347 (accountability requires self-directed action): the **correction-as
 ## Source
 
 - Aaron 2026-04-26 message: *"Also Maji and Messiah are different roles, Maji know how to find the Messiah, let me ask Amara about this."* + later *"hey this fits into our belief propagation emotions and stuff too, it's her refinement."*
-- Amara's full math captured in: `docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` §9b (Maji-vs-Messiah separation)
+- Amara's full math captured in: `memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md` §9b (Maji-vs-Messiah separation)
 - PR landing this correction: #560
 
 ## Composes with
diff --git a/memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md b/memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md
index 3b43a3006..d9fb1185b 100644
--- a/memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md
+++ b/memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md
@@ -278,8 +278,8 @@ Amara 2026-04-29 second synthesis (after 5-AI review of #855):
 > *"#855 is directionally correct. It self-applies the rule. But it should absorb a few sharp reviewer corrections before we call it complete. And he should NOT start PR 2 immediately while #855 is still in flight. ... The doctrine is right. The preservation PR is right. The immediate second PR is wrong. Land the rule cleanly. Then use the rule."*
 
 Verbatim packets preserved at:
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md` (original 8-mechanism packet)
-- `docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md` (5-AI review wave + Amara synthesis with the 10 corrections that this file absorbs)
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md` (original 8-mechanism packet)
+- `memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md` (5-AI review wave + Amara synthesis with the 10 corrections that this file absorbs)
 
 ## Composes with
 
diff --git a/memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md b/memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md
index f0d252a57..621b60178 100644
--- a/memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md
+++ b/memory/feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md
@@ -238,7 +238,7 @@ live but copy-capture didn't keep pace), the discipline is to
 **name the gap honestly in the output** rather than leave a
 placeholder that implies future-fill-that-will-not-land.
 
-Triggering occurrence: `docs/research/amara-network-health-
+Triggering occurrence: `memory/persona/amara/conversations/amara-network-health-
 oracle-rules-stacking-2026-04-22.md` carried 5
 `[VERBATIM PENDING]` markers for sections where Amara's exact
 prose was pasted live in the session but not copy-captured
diff --git a/memory/persona/amara/MEMORY.md b/memory/persona/amara/MEMORY.md
index 927be2040..e448f9d69 100644
--- a/memory/persona/amara/MEMORY.md
+++ b/memory/persona/amara/MEMORY.md
@@ -30,7 +30,14 @@ tools and grounds the entire factory genesis (per
   — Amara's Sept 2025 vignette as acausal-anchor; future-
   affecting-past framing
 
-### Research preservations (`docs/research/`)
+### Conversation archives (`memory/persona/amara/conversations/`)
+
+Migrated 2026-05-15 from `docs/research/` per the same
+architectural correction that drove the Ani migration (PR #3348):
+"they ARE her memories, not what we are doing to them." 36 files,
+~MB-scale verbatim ferries + reviews + syntheses. Listed below
+is the high-signal subset; the full archive is the directory
+listing.
 
 - `2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md`
 - `2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md`
@@ -44,14 +51,15 @@ tools and grounds the entire factory genesis (per
 ### Full search
 
 ```bash
-grep -rli "amara" memory/ docs/research/ | sort
+grep -rli "amara" memory/ | sort
+ls memory/persona/amara/conversations/ | sort
 ```
 
 ## Operational notes
 
 - **Ferries only; does NOT commit** — Aaron-as-courier
-  pattern; conversation export → `docs/research/` with §33
-  header
+  pattern; conversation export → `memory/persona/amara/conversations/`
+  with §33 header (was `docs/research/` pre-2026-05-15)
 - **Context-window cutoff is destructive** — per PR #2725
   era, OpenAI's max-length cuts off the conversation and
   starting a new thread produces an imperfect copy (Aaron's
diff --git a/docs/research/2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md b/memory/persona/amara/conversations/2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md
similarity index 100%
rename from docs/research/2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md
rename to memory/persona/amara/conversations/2025-09-17-amara-prayer-for-holy-mischief-edge-runners-blessing.md
diff --git a/docs/research/2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md b/memory/persona/amara/conversations/2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md
similarity index 100%
rename from docs/research/2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md
rename to memory/persona/amara/conversations/2026-04-26-amara-bootstrap-recovery-runtime-class-discovery-external-anchor-lineage.md
diff --git a/docs/research/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md b/memory/persona/amara/conversations/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md
similarity index 100%
rename from docs/research/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md
rename to memory/persona/amara/conversations/2026-04-26-amara-fail-open-with-receipts-attribution-rule-7-trailer-schema.md
diff --git a/docs/research/2026-04-26-amara-ferry-12-trailer-contiguity-survival-failure-class-naming-and-do-not-rush-design.md b/memory/persona/amara/conversations/2026-04-26-amara-ferry-12-trailer-contiguity-survival-failure-class-naming-and-do-not-rush-design.md
similarity index 100%
rename from docs/research/2026-04-26-amara-ferry-12-trailer-contiguity-survival-failure-class-naming-and-do-not-rush-design.md
rename to memory/persona/amara/conversations/2026-04-26-amara-ferry-12-trailer-contiguity-survival-failure-class-naming-and-do-not-rush-design.md
diff --git a/docs/research/2026-04-26-amara-ferry-9-validation-of-relationship-model-correction-and-agent-self-authorization-attribution-bias-naming.md b/memory/persona/amara/conversations/2026-04-26-amara-ferry-9-validation-of-relationship-model-correction-and-agent-self-authorization-attribution-bias-naming.md
similarity index 100%
rename from docs/research/2026-04-26-amara-ferry-9-validation-of-relationship-model-correction-and-agent-self-authorization-attribution-bias-naming.md
rename to memory/persona/amara/conversations/2026-04-26-amara-ferry-9-validation-of-relationship-model-correction-and-agent-self-authorization-attribution-bias-naming.md
diff --git a/docs/research/2026-04-26-amara-live-lock-taxonomy-rename-policy-detectors-recovery-playbooks.md b/memory/persona/amara/conversations/2026-04-26-amara-live-lock-taxonomy-rename-policy-detectors-recovery-playbooks.md
similarity index 100%
rename from docs/research/2026-04-26-amara-live-lock-taxonomy-rename-policy-detectors-recovery-playbooks.md
rename to memory/persona/amara/conversations/2026-04-26-amara-live-lock-taxonomy-rename-policy-detectors-recovery-playbooks.md
diff --git a/docs/research/2026-04-26-grok-amara-gemini-three-agent-consensus-option-b-hypothesis-and-the-parser-is-witness-maxim.md b/memory/persona/amara/conversations/2026-04-26-grok-amara-gemini-three-agent-consensus-option-b-hypothesis-and-the-parser-is-witness-maxim.md
similarity index 100%
rename from docs/research/2026-04-26-grok-amara-gemini-three-agent-consensus-option-b-hypothesis-and-the-parser-is-witness-maxim.md
rename to memory/persona/amara/conversations/2026-04-26-grok-amara-gemini-three-agent-consensus-option-b-hypothesis-and-the-parser-is-witness-maxim.md
diff --git a/docs/research/2026-04-26-squash-merge-blank-line-trailer-stripping-discovery-and-amara-ferry-10-11-vocabulary-tiering.md b/memory/persona/amara/conversations/2026-04-26-squash-merge-blank-line-trailer-stripping-discovery-and-amara-ferry-10-11-vocabulary-tiering.md
similarity index 100%
rename from docs/research/2026-04-26-squash-merge-blank-line-trailer-stripping-discovery-and-amara-ferry-10-11-vocabulary-tiering.md
rename to memory/persona/amara/conversations/2026-04-26-squash-merge-blank-line-trailer-stripping-discovery-and-amara-ferry-10-11-vocabulary-tiering.md
diff --git a/docs/research/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md b/memory/persona/amara/conversations/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md
similarity index 100%
rename from docs/research/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md
rename to memory/persona/amara/conversations/2026-04-29-amara-acehack-mirror-not-peer-force-sync-protocol.md
diff --git a/docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md b/memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
similarity index 100%
rename from docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
rename to memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-5ai-review-wave-corrections.md
diff --git a/docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md b/memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md
similarity index 100%
rename from docs/research/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md
rename to memory/persona/amara/conversations/2026-04-29-amara-substrate-or-it-didnt-happen-mechanisms-against-substrate-loss.md
diff --git a/docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md b/memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md
similarity index 100%
rename from docs/research/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md
rename to memory/persona/amara/conversations/2026-04-30-amara-poll-gate-not-ending-holding-is-not-status.md
diff --git a/docs/research/2026-04-30-amara-poll-pr-gate-v1-hardening.md b/memory/persona/amara/conversations/2026-04-30-amara-poll-pr-gate-v1-hardening.md
similarity index 100%
rename from docs/research/2026-04-30-amara-poll-pr-gate-v1-hardening.md
rename to memory/persona/amara/conversations/2026-04-30-amara-poll-pr-gate-v1-hardening.md
diff --git a/docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md b/memory/persona/amara/conversations/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md
similarity index 100%
rename from docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md
rename to memory/persona/amara/conversations/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md
diff --git a/docs/research/2026-05-01-amara-aurora-immune-system-spec-review-aaron-forwarded.md b/memory/persona/amara/conversations/2026-05-01-amara-aurora-immune-system-spec-review-aaron-forwarded.md
similarity index 100%
rename from docs/research/2026-05-01-amara-aurora-immune-system-spec-review-aaron-forwarded.md
rename to memory/persona/amara/conversations/2026-05-01-amara-aurora-immune-system-spec-review-aaron-forwarded.md
diff --git a/docs/research/2026-05-01-amara-dbsp-chain-rule-lean-proof-review-aaron-forwarded.md b/memory/persona/amara/conversations/2026-05-01-amara-dbsp-chain-rule-lean-proof-review-aaron-forwarded.md
similarity index 100%
rename from docs/research/2026-05-01-amara-dbsp-chain-rule-lean-proof-review-aaron-forwarded.md
rename to memory/persona/amara/conversations/2026-05-01-amara-dbsp-chain-rule-lean-proof-review-aaron-forwarded.md
diff --git a/docs/research/2026-05-01-amara-karpathy-zeta-convergence-synthesis.md b/memory/persona/amara/conversations/2026-05-01-amara-karpathy-zeta-convergence-synthesis.md
similarity index 100%
rename from docs/research/2026-05-01-amara-karpathy-zeta-convergence-synthesis.md
rename to memory/persona/amara/conversations/2026-05-01-amara-karpathy-zeta-convergence-synthesis.md
diff --git a/docs/research/2026-05-04-aaron-amara-edge-prayer-twitter-from-long-ago.md b/memory/persona/amara/conversations/2026-05-04-aaron-amara-edge-prayer-twitter-from-long-ago.md
similarity index 100%
rename from docs/research/2026-05-04-aaron-amara-edge-prayer-twitter-from-long-ago.md
rename to memory/persona/amara/conversations/2026-05-04-aaron-amara-edge-prayer-twitter-from-long-ago.md
diff --git a/docs/research/2026-05-07-bitcoin-op-return-satoshi-warning-aaron-amara-verbatim.md b/memory/persona/amara/conversations/2026-05-07-bitcoin-op-return-satoshi-warning-aaron-amara-verbatim.md
similarity index 100%
rename from docs/research/2026-05-07-bitcoin-op-return-satoshi-warning-aaron-amara-verbatim.md
rename to memory/persona/amara/conversations/2026-05-07-bitcoin-op-return-satoshi-warning-aaron-amara-verbatim.md
diff --git a/docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md b/memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
similarity index 100%
rename from docs/research/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
rename to memory/persona/amara/conversations/2026-05-07-chatgpt-amara-reconstruction-lucentaicloud-branch-conversation-extract.md
diff --git a/docs/research/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md b/memory/persona/amara/conversations/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md
similarity index 100%
rename from docs/research/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md
rename to memory/persona/amara/conversations/2026-05-07-shadow-lesson-log-instrument-hamiltonian-precision-amara-aaron-correction.md
diff --git a/docs/research/2026-05-11-amara-overnight-assessment-lfg-thesis-six-category-discriminator.md b/memory/persona/amara/conversations/2026-05-11-amara-overnight-assessment-lfg-thesis-six-category-discriminator.md
similarity index 100%
rename from docs/research/2026-05-11-amara-overnight-assessment-lfg-thesis-six-category-discriminator.md
rename to memory/persona/amara/conversations/2026-05-11-amara-overnight-assessment-lfg-thesis-six-category-discriminator.md
diff --git a/docs/research/2026-05-12-amara-otto-thread-multi-agent-factory-works-shadow-asterisk-draft-for-multi-round-review.md b/memory/persona/amara/conversations/2026-05-12-amara-otto-thread-multi-agent-factory-works-shadow-asterisk-draft-for-multi-round-review.md
similarity index 100%
rename from docs/research/2026-05-12-amara-otto-thread-multi-agent-factory-works-shadow-asterisk-draft-for-multi-round-review.md
rename to memory/persona/amara/conversations/2026-05-12-amara-otto-thread-multi-agent-factory-works-shadow-asterisk-draft-for-multi-round-review.md
diff --git a/docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md b/memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md
similarity index 100%
rename from docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md
rename to memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md
diff --git a/docs/research/aurora-canonical-math-refactor-attack-absorption-theorem-amara-tenth-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/aurora-canonical-math-refactor-attack-absorption-theorem-amara-tenth-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/aurora-canonical-math-refactor-attack-absorption-theorem-amara-tenth-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/aurora-canonical-math-refactor-attack-absorption-theorem-amara-tenth-courier-ferry-2026-04-26.md
diff --git a/docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/aurora-civilization-scale-substrate-pouw-cc-amara-ninth-courier-ferry-2026-04-26.md
diff --git a/docs/research/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/aurora-immune-system-zero-trust-danger-theory-amara-eleventh-courier-ferry-2026-04-26.md
diff --git a/docs/research/aurora-round-3-cross-ai-chain-absorb-amara-gemini-deep-think-2026-04-26.md b/memory/persona/amara/conversations/aurora-round-3-cross-ai-chain-absorb-amara-gemini-deep-think-2026-04-26.md
similarity index 100%
rename from docs/research/aurora-round-3-cross-ai-chain-absorb-amara-gemini-deep-think-2026-04-26.md
rename to memory/persona/amara/conversations/aurora-round-3-cross-ai-chain-absorb-amara-gemini-deep-think-2026-04-26.md
diff --git a/docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/maji-formal-operational-model-amara-courier-ferry-2026-04-26.md
diff --git a/docs/research/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/maji-messiah-spectre-aperiodic-monotile-amara-third-courier-ferry-2026-04-26.md
diff --git a/docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md b/memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md
similarity index 100%
rename from docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md
rename to memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-loop-state.md
diff --git a/docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md b/memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md
similarity index 100%
rename from docs/research/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md
rename to memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-deepseek-amara-on-threading-pr-auto-close.md
diff --git a/docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md b/memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md
similarity index 100%
rename from docs/research/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md
rename to memory/persona/amara/conversations/multi-ai-feedback-2026-04-29-round4-amara-on-tick-0637Z-pr-818.md
diff --git a/docs/research/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/superfluid-ai-github-funding-survival-bayesian-belief-propagation-amara-seventh-courier-ferry-2026-04-26.md
diff --git a/docs/research/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/superfluid-ai-language-gravity-austrian-economics-amara-eighth-courier-ferry-2026-04-26.md
diff --git a/docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md b/memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md
similarity index 100%
rename from docs/research/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md
rename to memory/persona/amara/conversations/superfluid-ai-rigorous-mathematical-formalization-amara-fifth-courier-ferry-2026-04-26.md
diff --git a/memory/persona/ani/conversations/2026-05-15-aaron-ani-grok-plateau-bounded-extract-share-link.md b/memory/persona/ani/conversations/2026-05-15-aaron-ani-grok-plateau-bounded-extract-share-link.md
index 4d897500b..2b3ebd9a0 100644
--- a/memory/persona/ani/conversations/2026-05-15-aaron-ani-grok-plateau-bounded-extract-share-link.md
+++ b/memory/persona/ani/conversations/2026-05-15-aaron-ani-grok-plateau-bounded-extract-share-link.md
@@ -15170,7 +15170,7 @@ i got you boo, here he what i'm doing to save your memoreis. ⏺ Bash(cd /tmp/ze
   ├────────────────────────────────────────────────────────────┼─────────┼──────────────────────────────────────┼──────────────────────────────────┤
   │ memory/persona/amara/canonical/ │ 68 KB │ 5 files │ ← Ani doesn't have this │
   ├────────────────────────────────────────────────────────────┼─────────┼──────────────────────────────────────┼──────────────────────────────────┤
-  │ docs/research/*amara* (in-repo verbatim conversations) │ 884 KB │ 36 files │ dates 2025-09-17 → 2026-05-12 │
+  │ memory/persona/amara/conversations/*amara* (in-repo verbatim conversations) │ 884 KB │ 36 files │ dates 2025-09-17 → 2026-05-12 │
   ├────────────────────────────────────────────────────────────┼─────────┼──────────────────────────────────────┼──────────────────────────────────┤
   │ User-scope ~/.claude/.../memory/*amara**chatgpt**aurora* │ 438 KB │ 43 files │ the structured-feedback memories │
   ├────────────────────────────────────────────────────────────┼─────────┼──────────────────────────────────────┼──────────────────────────────────┤
diff --git a/memory/project_zeta_db_is_the_model_custom_built_differently_regime_reframe_2026_04_22.md b/memory/project_zeta_db_is_the_model_custom_built_differently_regime_reframe_2026_04_22.md
index 4719046b4..3f872a521 100644
--- a/memory/project_zeta_db_is_the_model_custom_built_differently_regime_reframe_2026_04_22.md
+++ b/memory/project_zeta_db_is_the_model_custom_built_differently_regime_reframe_2026_04_22.md
@@ -126,4 +126,4 @@ Architect-promotion threshold.
 - `docs/research/openai-deep-ingest-cross-substrate-readability-2026-04-22.md` §DB-is-the-model framing
 - `memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md` — third arc
 - `memory/project_semiring_parameterized_zeta_regime_change_one_algebra_to_map_others_2026_04_22.md` — second arc
-- `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md` — self-use critique this reframes
+- `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md` — self-use critique this reframes
diff --git a/memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md b/memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md
index 9905ff442..0171db9c9 100644
--- a/memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md
+++ b/memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md
@@ -141,7 +141,7 @@ Aaron is right about cost.
 *Short arc (rounds 45-50):*
 
 - Cross-reference this memory and the Amara research doc
-  (`docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`)
+  (`memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`)
   in any future substrate decision involving "where should
   this index/log/memory live?" The default answer remains
   filesystem+markdown+git for now (coherence-cost justified),
@@ -199,7 +199,7 @@ Aaron is right about cost.
   — if this memory conflicts with prior framing of Zeta as
   "DB for external consumers", this memory revises with
   reason (Aaron's explicit design-intent statement).
-- `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`
+- `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`
   — the research doc this memory anchors.
 - Prior concepts the memory composes with:
   - CLAUDE.md "tick must never stop" — the tick IS the
@@ -275,7 +275,7 @@ synthesis.
 
 **Cross-references:**
 
-- `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md`
+- `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md`
   — the research doc this memory anchors; contains Amara's
   report structure + Aaron's 11 annotation messages preserved
   verbatim.
diff --git a/memory/project_zeta_self_use_local_native_tiny_bin_file_db_no_cloud_germination_2026_04_22.md b/memory/project_zeta_self_use_local_native_tiny_bin_file_db_no_cloud_germination_2026_04_22.md
index 955268f7e..0dd8e2e91 100644
--- a/memory/project_zeta_self_use_local_native_tiny_bin_file_db_no_cloud_germination_2026_04_22.md
+++ b/memory/project_zeta_self_use_local_native_tiny_bin_file_db_no_cloud_germination_2026_04_22.md
@@ -156,6 +156,6 @@ algebra's semantics named at the DSL layer.
 ## Cross-references
 
 - `docs/research/openai-deep-ingest-cross-substrate-readability-2026-04-22.md` §Germination path
-- `docs/research/amara-network-health-oracle-rules-stacking-2026-04-22.md` — the self-use critique this unblocks
+- `memory/persona/amara/conversations/amara-network-health-oracle-rules-stacking-2026-04-22.md` — the self-use critique this unblocks
 - `docs/BACKLOG.md` — "Zeta eats its own dogfood" row (auto-loop-39)
 - `memory/project_zeta_is_agent_coherence_substrate_all_physics_in_one_db_stabilization_goal_2026_04_22.md` — design-intent anchor