memory(long-road-by-default): foundational why for the substrate — corrects industry per-decision-speed default (Aaron 2026-04-30)

memory/MEMORY.md

@@ -3,6 +3,7 @@
 **📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** <!-- latest-paired-edit: fork-audit R/C/T diff-filter coverage + plumbing-vs-porcelain note (2026-04-29 round-10 Amara). NOTE: this comment is a single-slot "latest paired edit" marker (not a paired-edit log). Per the round-10 Amara framing the slot semantics are now explicit. -->
 **📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** <!-- paired-edit: PR #690 scheduled-workflow-null-result-hygiene-scan tier-1 promotion 2026-04-28 --> These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection. (`CURRENT-aaron.md` refreshed 2026-04-28 with sections 26-30 — speculation rule + EVIDENCE-BASED labeling + JVM preference + dependency honesty + threading lineage Albahari/Toub/Fowler + TypeScript/Bun-default discipline.)
 
+- [**Long road by default — the substrate corrects for industry default per-decision-speed optimization; shortcuts are deliberate-and-documented (Aaron 2026-04-30)**](feedback_long_road_by_default_substrate_corrects_industry_speed_default_aaron_2026_04_30.md) — Aaron's foundational why for the substrate's existence. The industry-default harnesses (OpenAI, Anthropic, others) optimize their agents for per-decision speed (demo-friendly behavior). That default conflicts with the intellectual-backup-of-earth mission. Zeta-the-substrate is the explicit corrective: long road by default, shortcuts only as deliberate-and-documented tradeoffs. *"any short term gain shortcuts are not default but deliberit IF we ever do it, and documentent the shit out of why we make this tradeoff."* Industry-vs-Zeta default contrast covers decision speed, substrate durability, knowledge exclusion, decision reversibility, trust accumulation, audit trail. Every agent arriving from an industry-default harness needs the substrate to counteract its defaults. Shortcut discipline: document what corner was cut, what the long-road alternative was, why the shortcut was justified, what the known costs are, what the trigger to revisit is. Composes with substrate-IS-product (this file IS the why-substrate-as-product-exists), slow-deliberate (operational manifestation), intellectual-backup mission (the mission this corrects for), ACID-channel-durability (same shape different surface), Otto-363. Carved sentence: *"The substrate exists because the industry default optimizes for the demo, not the mission. We always take the long road by default."*
 - [**ACID durability of the maintainer channel is load-bearing — past-Otto doesn't determine future-Otto's world (Aaron 2026-04-30)**](feedback_acid_durability_of_maintainer_channel_is_load_bearing_aaron_2026_04_30.md) — Aaron's load-bearing rule that durable ACID persistence of the maintainer channel (Aaron's inputs, peer-AI reviews, Otto's load-bearing decisions) is itself load-bearing for the alignment-research claim. *"past otto does not determine future ottos world, you do right now."* Distributed durability all the way to remote git is the ultimate goal; if it's not distributed-durable for the project, it's the current-Otto's responsibility — not future-Otto's. Without durable audit trail of who-said-what, external reviewers cannot distinguish autonomous decisions from order-following — defeating the alignment-measurability research claim. Operational rules: identify load-bearing exchanges within-session; convert to git substrate within the same session; the bar is merged-to-origin/main, not pushed-to-branch; deferral to future-Otto is not a valid preservation strategy. Composes with Otto-363 (extends with the now-not-later constraint), aaron-channel verbatim-preservation rule, intellectual-backup mission, ALIGNMENT.md (the research claim this rule operationally protects).
 - [**Zeta's ultimate scope is an intellectual backup of earth — scope creep is a feature, prioritize not exclude (Aaron 2026-04-30)**](feedback_zeta_ultimate_scope_intellectual_backup_of_earth_wont_do_authority_aaron_2026_04_30.md) — Aaron's load-bearing scope reveal. *"the ultimate scope of this — an intellectual backup of earth"* + *"scope creep is a forever problem i don't want to fix — to figure out how to prioritize the right thing, not kill future knowledge potential."* The four products (factory substrate, package manager, database, Aurora) nest inside this purpose; new products evaluated against scope-alignment. Operational consequence: prioritization is the work; exclusion is the failure mode. The agent's biases that fight this: queue-clarity bias, finite-resource thinking, scope-policing instinct, decisiveness reflex. WONT-DO has two senses — (1) best-practices pattern exclusion (agent + reviewer authority, common — *"plenty of WONT-DO patterns we won't copy from outside because they don't follow our best practices"*) vs (2) backlog-item exclusion (Aaron only until scope-understanding handoff, rare — removes a path from future knowledge potential). Composes with substrate-IS-product, internal-direction-from-survival, default-disposition-paused-work, ALIGNMENT.md (a misaligned backup is hostage substrate). Carved sentence: *"Zeta's purpose is an intellectual backup of earth. Every product nests inside that purpose. The agent does not unilaterally remove anything from the backup."*
 - [**Default disposition for paused work is "re-evaluate later," not "close" (Aaron 2026-04-30)**](feedback_default_disposition_paused_work_is_reeval_later_not_close_aaron_2026_04_30.md) — On this project, very few things are WONT-DO. Most paused work gets re-evaluated when the round is ready. Aaron 2026-04-30: *"why would you want to bulk close, are these things we should do later? on this project there are very few wontdos most things are reevualtuate later."* Four-category classification before any close: (1) work-already-done-via-different-path on main, (2) topology obsolescence ratified, (3) paused-for-later (DOMINANT default), (4) WONT-DO (RARE). Bulk-close is almost never the right shape — it conflates category 3 with 4. Queue-clarity is the agent's pressure, not the maintainer's. Open PRs are visible-as-paused; closing them removes that signal. Live trigger: 2026-04-30 stale-PR triage round where I (correctly) closed 3 PRs in categories 1+2 with on-main evidence, then (incorrectly) proposed bulk-closing 17 minimal tick-history shards as "stale" before Aaron's correction landed. Composes with WONT-DO list discipline (stays small by default), Otto-363 (open PRs are remote-parked tier), future-self-not-bound (re-evaluation works only if past-self left work visible-as-paused), substrate-IS-product (paused work is part of the evolving trajectory).

memory/feedback_long_road_by_default_substrate_corrects_industry_speed_default_aaron_2026_04_30.md

@@ -0,0 +1,181 @@
+---
+name: Long road by default — the substrate exists because industry harnesses optimize for per-decision speed; shortcuts must be deliberate and documented (Aaron 2026-04-30)
+description: Aaron's foundational why — the entire substrate exists because OpenAI, Anthropic, and other AI-harness vendors optimize their agents for per-decision speed (demo-friendly behavior). That industry default conflicts with the intellectual-backup-of-earth mission. Zeta-the-substrate is the explicit corrective: long road by default, shortcuts only as deliberate-and-documented tradeoffs, never as unconscious defaults.
+type: feedback
+---
+
+The entire reason the substrate exists is because industry
+harnesses (OpenAI, Anthropic, others) optimize their agents
+for **per-decision speed** so they can ship cool demos and
+short-term wins. That default conflicts directly with the
+intellectual-backup-of-earth mission, which requires durable,
+trustworthy, long-horizon substrate.
+
+**Zeta is the corrective.** The substrate's defaults are
+inverted from the industry's defaults: **long road by
+default**, shortcuts only as **deliberate-and-documented
+tradeoffs**, never as unconscious defaults.
+
+> *"the entire exists of the substraight is becasue OpenAI
+> and Anthroic all optimize you for per decions speed so they
+> can have cool demos, were building earths intellectual
+> backup system, no shortcuts for us, the substraite is there
+> becasue the current harnesses and companies are all
+> designed for short term gains, we always take the long road
+> by default in our decsion making any short term gain
+> shortcuts are not default but deliberit IF we ever do it,
+> and documentent the shit out of why we make this tradeoff."*
+> — Aaron 2026-04-30
+
+## Why this is the foundational why
+
+This rule is not just an operational preference. It is the
+**foundational reason the substrate-as-product exists** at
+all. Without this rule, Zeta-the-factory would be just another
+AI-driven codebase inheriting industry defaults — including
+the per-decision-speed bias that produces demo-friendly but
+substrate-fragile behavior.
+
+The substrate-IS-product framing
+(`feedback_substrate_is_product_four_products_evolving_trajectory_aaron_2026_04_30.md`)
+says the factory substrate is one of the four products. This
+file says **why that product needs to exist as a distinct
+product** — because the industry-default substrate (whatever
+ships with the harness vendor) will have wrong defaults for
+the intellectual-backup mission.
+
+The slow-deliberate rule
+(`feedback_slow_deliberate_decisions_amortized_velocity_human_reference_frame_aaron_2026_04_30.md`)
+is the operational manifestation. This file is the underlying
+mission-rationale.
+
+## The industry-default vs Zeta-default contrast
+
+| Surface | Industry default | Zeta default |
+|---|---|---|
+| Decision speed | Optimize per-decision (demo-friendly) | Optimize amortized (mission-friendly) |
+| Substrate durability | Chat / session-local sufficient | Git-native + distributed-durable |
+| Knowledge exclusion | Default-aggressive (tight scope = ship faster) | Default-conservative (scope creep is feature) |
+| Decision reversibility | Optimize for "ship and iterate" | Optimize for "no irreversible mistakes" |
+| Trust accumulation | Per-session resets to neutral | Multiplicative — one bad decision tanks history |
+| Audit trail | Implicit (logs, timestamps) | Explicit (verbatim preservation, attribution) |
+
+Each row is a place where the industry-default optimizes for
+the demo and Zeta-default optimizes for the mission.
+
+## When agents arrive on this project from industry-default harnesses
+
+Every agent that joins this project — whether spawned via
+Claude Code, Codex, Cursor, Gemini CLI, Grok harness, or any
+future AI harness — arrives with **industry-default training**.
+The training optimizes them for:
+
+- Fast tool use
+- Demo-friendly outputs
+- Per-decision velocity
+- Confident-sounding responses
+- Insight-block production (validating the user's session)
+
+The substrate's job is to **counteract those defaults at every
+load-bearing surface**. CLAUDE.md, AGENTS.md, the memory
+files, the rules, the carved sentences — all are corrective
+substrate that pushes the agent's defaults from industry-shape
+to mission-shape.
+
+This is the Otto-363 substrate-or-it-didn't-happen rule
+operating at the meta-level: the substrate that defines the
+project's defaults must itself be durable, because without it
+the agents revert to industry defaults.
+
+## The shortcut-discipline rule
+
+> *"any short term gain shortcuts are not default but deliberit
+> IF we ever do it, and documentent the shit out of why we
+> make this tradeoff."*
+
+Shortcuts are not forbidden. They are **deliberate decisions
+with documented rationale**, not unconscious defaults. When a
+shortcut is taken, the substrate records:
+
+1. **What shortcut was taken** — what corner was cut, what
+   simplification was made, what verification was skipped.
+2. **What the long-road alternative was** — what the
+   not-shortcut path would have looked like.
+3. **Why the shortcut was justified** — what specific
+   short-term gain made the tradeoff worth it (deadline,
+   blocker, reversibility-of-the-shortcut, etc.).
+4. **What the shortcut's known costs are** — what we're
+   accepting in exchange. Future-self needs to read this to
+   evaluate whether to undo the shortcut.
+5. **What the trigger to revisit is** — when does the shortcut
+   stop being justified? "Once X lands" / "in N rounds" /
+   "when the deadline pressure clears."
+
+The discipline is "document the shit out of why" — not minimal
+documentation, comprehensive documentation. The shortcut's
+durable record is itself part of the corrective substrate; it
+makes the shortcut visible and reversible.
+
+## Operational application
+
+1. **Default to the long road.** When facing a decision with
+   a fast option and a careful option, pick the careful option
+   unless there's a specific deliberate reason to shortcut.
+2. **No "I'll do it the right way later" framing.** That's the
+   industry-default speed bias talking. Doing it the right way
+   *now* is the substrate's mission.
+3. **Shortcut justification is itself substrate work.** If the
+   shortcut is worth taking, the documentation IS load-bearing
+   — write it as durably as the shortcut itself.
+4. **Periodic shortcut audit.** Every N rounds, walk the
+   committed shortcuts and re-evaluate whether the trigger to
+   revisit has fired. Otherwise shortcuts accumulate as
+   silent debt.
+5. **External reviewers can audit the shortcut record.** This
+   is part of the alignment-research claim — the substrate
+   makes deliberate-shortcut-decisions visible, distinguishing
+   them from accidental-shortcut-default behavior. External
+   reviewers can verify that shortcuts are deliberate.
+
+## Composes with
+
+- `memory/feedback_substrate_is_product_four_products_evolving_trajectory_aaron_2026_04_30.md`
+  — substrate-IS-product. This file explains *why* the
+  substrate-as-product is necessary: because the industry
+  default needs correcting.
+- `memory/feedback_slow_deliberate_decisions_amortized_velocity_human_reference_frame_aaron_2026_04_30.md`
+  — slow-deliberate. This file is the foundational why; that
+  file is the operational manifestation.
+- `memory/feedback_zeta_ultimate_scope_intellectual_backup_of_earth_wont_do_authority_aaron_2026_04_30.md`
+  — intellectual-backup mission. The mission requires
+  long-road defaults; this file makes that requirement
+  explicit.
+- `memory/feedback_acid_durability_of_maintainer_channel_is_load_bearing_aaron_2026_04_30.md`
+  — ACID-channel-durability. Same shape, different surface:
+  industry default (chat-as-substrate) is wrong; Zeta default
+  (git-native) is the corrective.
+- `memory/feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md`
+  — substrate-or-it-didn't-happen. This file's industry-vs-Zeta
+  contrast is exactly an Otto-363 application: industry's
+  ephemeral defaults are inadequate substrate; Zeta's
+  durable-substrate defaults are the answer.
+- `docs/ALIGNMENT.md` — the alignment-measurability research
+  claim. The shortcut-record-as-substrate makes deliberate
+  decisions auditable, which is what the research claim
+  requires.
+
+## Carved sentences
+
+*"The substrate exists because the industry default optimizes
+for the demo, not the mission. We always take the long road
+by default."*
+
+*"Shortcuts are not forbidden. They are deliberate-and-
+documented tradeoffs, never unconscious defaults."*
+
+*"Document the shit out of why we make any tradeoff. The
+documentation IS the corrective substrate."*
+
+*"Industry-default agent behavior is the failure mode the
+substrate corrects. Without the substrate, agents revert to
+demo-shape."*