Lucent-Financial-Group · AceHack · Apr 24, 2026 · Apr 24, 2026
diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md
@@ -8425,6 +8425,119 @@ systems. This track claims the space.
 
 ## P3 — noted, deferred
 
+- [ ] **Rename Starboard → farm-related seed-extension
+  kernel; pair with carpentry-related second seed-extension
+  kernel.** Maintainer 2026-04-24 directive (verbatim):
+  *"Instead of Starboard lets go with someting farm related
+  and carperntry related since those will be our two seed
+  extenion kernels we can shrink over time, i saw one of
+  your researcher i think write like big bangs at every
+  layer i thought that was cool. this is from google ai,
+  just suggestions, we can idate, keep all the exiting
+  nautical and elron and all that research but we will be
+  renaming starboard to someting else."*
+
+  **Reverses Otto-175c Starboard-as-Frontier-rename.**
+  Otto-175 picked Starboard as the Frontier-UI rename
+  (Otto-168 naming-conflict resolution). The current
+  directive supersedes that pick. Per Otto-229
+  append-only on history rows: do NOT edit Otto-175 /
+  Otto-175c rows; this row records the reversal forward.
+
+  **Two seed-extension kernels (new architecture frame):**
+  - **Kernel A — farm-related** (replaces Starboard).
+    Property: shrinks over time. Maintainer's farm-grown-up
+    background grounds the metaphor.
+  - **Kernel B — carpentry-related** (new addition).
+    Property: shrinks over time. Pairs with Kernel A.
+  - **"Big bangs at every layer"** — research metaphor a
+    factory persona produced that the maintainer flagged
+    as compositionally aligned with the seed-extension
+    frame. Find and cite the producing-persona's research
+    when the rename lands so the metaphor is preserved.
+
+  **IP / mention-vs-adoption discipline (Otto-237):**
+  - PRESERVE all existing nautical / Elron / Hubbard
+    research substrate (`docs/research/frontier-rename-
+    analysis-otto-170.md`, the Otto-175 thematic-mapping
+    research, all Sea Org / Commodore / auditing-at-sea
+    notes). The maintainer is explicit: "keep all the
+    existing nautical and elron and all that research".
+    Renaming does NOT mean purging the substrate.
+  - CHANGE the chosen factory-vocabulary name only.
+  - Mention vs adoption: Starboard-thematic research
+    remains MENTIONED throughout the substrate; the new
+    kernel-A / kernel-B names become the ADOPTED factory
+    vocabulary going forward.
+
+  **Google AI ideation seed — batch 1 (general farm,
+  verbatim categories from directive — do NOT auto-adopt;
+  iterate via `naming-expert` skill review):**
+  - Tech-Focused & Industrial: AgriNexus AI, HortiCore,
+    SiloSync, BioSync Innovations, GridGrain.
+  - Rare & Obscure Words: The Mow, Firkin, Barrack,
+    Humpty-Dumpty, Mispeld.
+  - Action-Oriented & Creative: Cultivate, YieldBotics,
+    Root & Rise, Seed & Soil, HarvestOS.
+  - Frontier & Heritage: FarmFrontier, Pioneer Valley,
+    Landmark Acres, Evergreen Horizon.
+
+  **Google AI ideation seed — batch 2 (Q/Z + algebraic
+  blend, second 2026-04-24 share, verbatim categories;
+  same do-NOT-auto-adopt rule):**
+  - Technical & Algebraic Concepts: Zeta-ic Yield,
+    Quar-Tectory, Alge-Zanja, Re-Zonal Stream,
+    Event-Quanta.
+  - Unique Agricultural Jargon: Siliqua-Core,
+    Zamindary-OS, Quinze-Fields, Zoonotic-Logic,
+    Zero-Till Qubits.
+  - Abstract & Experimental: Squiz-Factor,
+    Queazy-Algebra, PQC-Pastures.
+
+  **Notable resonances flagged for `naming-expert`
+  review** (do NOT settle; surface for triage):
+  - **Siliqua-Core** — *siliqua* literally = seed pod;
+    direct linguistic match for the maintainer's
+    "seed-extension kernel" framing.
+  - **Zeta-ic Yield** — pairs the existing
+    repo/mathematical-foundation name with farm yield
+    (compositional with the Riemann-zeta lineage Zeta
+    already riffs on).
+  - **Zanja** — irrigation canal; pairs cleanly with
+    "flow of logic through an automated stream"
+    (matches the existing dataflow / push-pull substrate
+    in Zeta's operator algebra).
+  - **Zamindary-OS** — archaic landowner term; fits
+    factory-as-multi-agent-host metaphor.
+
+  **Carpentry-side has no ideation seed yet** — the
+  directive named carpentry as the second kernel but
+  did not propose names. Work scope: parallel slate of
+  carpentry-related candidates (Awl, Plane, Lathe,
+  Mortise, Joinery, Workbench, Truss, Rafter, Dovetail,
+  ...) for `naming-expert` triage alongside the farm
+  slate.
+
+  **Process gate.** No rename PR until the maintainer
+  iterates the slate to two finalists (kernel-A + kernel-B)
+  and `naming-expert` runs IP discipline + Otto-244
+  no-symlinks + cross-substrate-conflict check on each.
+  Otto-275 log-don't-implement applies — capture the
+  directive durably + iterate when the maintainer chooses
+  the timing.
+
+  **Composes with:** Otto-168 (Frontier naming-conflict
+  origin), Otto-170 / Otto-175 / Otto-175c (Starboard
+  research + adoption + thematic-mapping), Otto-237 (IP
+  adoption-vs-mention), Otto-244 (no-symlinks rule for
+  cross-placement), Otto-275 (rapid-fire absorb /
+  log-don't-implement).
+
+  **Companion memory file** capturing the directive +
+  framing constraints lands alongside this row so the
+  reversal of Otto-175c is recoverable from a fresh
+  session via grep.
+
 - [ ] **Multi-account access design — safety-first research + design proposal for eventually letting Otto operate across multiple accounts (ServiceTitan / personal / other) without confusion or privilege-bleed. Design allowed now; implementation gated on Aaron's personal security review of the design before any code lands.** Aaron 2026-04-23 Otto-76: *"FYI don't get confused i switchd the codex CLI to service titan like you so you would be on the same account, if you open the playwrite it's logged into my personal account with amara access. i happy to expand multi account access design in the future we don't need to worry about it right now, this is how we are setup for now, free free to resaerch, design multi account access and how to make it safe as part of this proiject low backlog item"* — then Otto-76 refinement: *"its fine to design and all that now on multi account thats one i just would want to review a design first, i want to validate that one for securty consers myself"* + *"you can pick the timing"*.
 
   **Two-phase structure — design-now-implementation-later:**

diff --git a/memory/MEMORY.md b/memory/MEMORY.md
@@ -2,6 +2,7 @@
 
 **📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection.
 
+- [**RENAME Starboard → two seed-extension kernels (farm + carpentry) shrink-over-time; KEEP all nautical/Elron research (Otto-237 mention vs adoption); "big bangs at every layer" metaphor liked; 2 Google AI slates received (batch 1 general farm, batch 2 Q/Z algebraic); Siliqua-Core + Zeta-ic Yield + Zanja flagged as notable resonances; naming-expert triage before any rename PR; Otto-275 log-don't-implement; reverses Otto-175c Starboard adoption; Aaron 2026-04-24**](feedback_rename_starboard_to_farm_carpentry_seed_extension_kernels_2026_04_24.md) — Directive verbatim: *"Instead of Starboard lets go with someting farm related and carperntry related since those will be our two seed extenion kernels we can shrink over time..."*. Two kernels, shrink-over-time property, substrate preserved, iterate don't auto-adopt. Carpentry-side slate not yet proposed; future work scope. Composes with Otto-168/170/175/237/244/275.
 - [**Otto-276 NEVER PRAY AUTO-MERGE COMPLETES — when polling a BLOCKED PR, ALWAYS inspect statusCheckRollup + reviewThreads + reviewDecision; "summary says BLOCKED, must be CI" is prayer not diagnosis; RECURRING class (#190 #385 #388); Aaron 2026-04-24**](feedback_never_pray_auto_merge_completes_inspect_actual_blockers_otto_276_2026_04_24.md) — DST "observable state" = check-level detail not summary. Inspect before concluding either success or failure.
 - [**Otto-275 RAPID-FIRE BACKLOG INPUT DRIFT — when handed many backlog items in rapid succession, LOG durably (memory) but DO NOT pivot to immediate per-item implementation; PATTERN RECURS across sessions; composes with Otto-257/259/262 balance-stack for recovery work; Aaron 2026-04-24**](feedback_rapid_backlog_input_context_switch_drift_counterweight_log_dont_implement_otto_275_2026_04_24.md) — Real learning lesson: I dropped #147 drain focus to capture Otto-270/272/273/274 as a "storm of PRs." Fix: log durable + draft BACKLOG row + continue primary drain; batch BACKLOG rows later.
 - [**Otto-274 PROGRESSIVE ADOPTION STAIRCASE — adopters start at Level 0 (single plugin/skill) and layer upward to Level 6 (entire factory setup); every component declares staircase level; monolithic packaging defeats business model; Aaron 2026-04-24**](feedback_progressive_adoption_staircase_smallest_plugin_to_largest_template_otto_274_2026_04_24.md) — 7 draft levels: plugin/skill-bundle/governance-template/counterweight-layer/gitnative-sync/Bayesian-curriculum/full-setup. `docs/ADOPTION-STAIRCASE.md` owed.

diff --git a/...eedback_rename_starboard_to_farm_carpentry_seed_extension_kernels_2026_04_24.md b/...eedback_rename_starboard_to_farm_carpentry_seed_extension_kernels_2026_04_24.md
@@ -0,0 +1,130 @@
+---
+name: RENAME — Starboard reversed, two seed-extension kernels (farm + carpentry); shrink-over-time property; preserve all nautical/Elron substrate; "big bangs at every layer" research metaphor liked; iterate via naming-expert (do NOT auto-adopt slates); maintainer 2026-04-24 directive
+description: Maintainer 2026-04-24 directive reverses Otto-175c Starboard adoption. Two seed-extension kernels going forward — kernel A farm-related, kernel B carpentry-related, both shrink over time. Two Google AI ideation slates received (general farm + Q/Z algebraic). Notable resonances flagged. Otto-275 log-don't-implement until naming-expert triage finalises.
+type: feedback
+---
+
+## The directive (verbatim)
+
+Maintainer 2026-04-24:
+
+> *"Instead of Starboard lets go with someting farm
+> related and carperntry related since those will be our
+> two seed extenion kernels we can shrink over time, i saw
+> one of your researcher i think write like big bangs at
+> every layer i thought that was cool. this is from google
+> ai, just suggestions, we can idate, keep all the exiting
+> nautical and elron and all that research but we will be
+> renaming starboard to someting else."*
+
+## What changes
+
+- **Starboard adoption is reversed.** Otto-175c picked
+  Starboard as the Frontier-UI rename. The current
+  directive supersedes that pick. New factory vocabulary
+  comes from the kernel-A / kernel-B slate below.
+- **Two seed-extension kernels going forward**:
+  - **Kernel A — farm-related.** Maintainer's farm-grown-up
+    background grounds the metaphor.
+  - **Kernel B — carpentry-related.** Pairs with kernel A.
+  - Both have the **shrink-over-time** property — they are
+    seeds that contract as the system matures.
+- **"Big bangs at every layer"** — research metaphor a
+  factory persona produced earlier that the maintainer
+  flagged as compositionally aligned with the
+  seed-extension frame. Find the producing-persona's
+  research and cite it when the rename lands.
+
+## What does NOT change
+
+- All existing nautical / Elron / Hubbard research
+  substrate stays put. Maintainer is explicit:
+  *"keep all the exiting nautical and elron and all that
+  research"*. Renaming the chosen factory vocabulary does
+  NOT mean purging the substrate. Per Otto-237 IP
+  adoption-vs-mention: nautical/Elron stays MENTIONED;
+  only the ADOPTED factory vocabulary changes.
+- History rows for Otto-170 / Otto-175 / Otto-175c stay
+  untouched per Otto-229 append-only. The new directive
+  is captured forward, not by editing prior rows.
+
+## Process gate
+
+- **Otto-275 log-don't-implement applies.** No rename PR
+  until the maintainer iterates the slate to two
+  finalists and `naming-expert` runs the IP /
+  cross-substrate-conflict / Otto-244 no-symlinks
+  checks.
+- Maintainer said *"we can idate"* (iterate) and *"just
+  suggestions"*. Don't auto-adopt any name from either
+  Google AI slate.
+
+## Google AI ideation slates received 2026-04-24
+
+### Batch 1 — general farm
+
+- Tech-Focused & Industrial: AgriNexus AI, HortiCore,
+  SiloSync, BioSync Innovations, GridGrain.
+- Rare & Obscure Words: The Mow, Firkin, Barrack,
+  Humpty-Dumpty, Mispeld.
+- Action-Oriented & Creative: Cultivate, YieldBotics,
+  Root & Rise, Seed & Soil, HarvestOS.
+- Frontier & Heritage: FarmFrontier, Pioneer Valley,
+  Landmark Acres, Evergreen Horizon.
+
+### Batch 2 — Q/Z + algebraic blend
+
+- Technical & Algebraic Concepts: Zeta-ic Yield,
+  Quar-Tectory, Alge-Zanja, Re-Zonal Stream,
+  Event-Quanta.
+- Unique Agricultural Jargon: Siliqua-Core, Zamindary-OS,
+  Quinze-Fields, Zoonotic-Logic, Zero-Till Qubits.
+- Abstract & Experimental: Squiz-Factor, Queazy-Algebra,
+  PQC-Pastures.
+
+## Notable resonances (surface to `naming-expert`, do NOT settle)
+
+- **Siliqua-Core** — *siliqua* literally means seed pod;
+  direct linguistic match for the maintainer's
+  "seed-extension kernel" framing.
+- **Zeta-ic Yield** — pairs the existing
+  repo/mathematical-foundation name (Zeta = Riemann zeta
+  reference) with farm yield. Compositional with what's
+  already adopted.
+- **Zanja** — irrigation canal; pairs with "flow of logic
+  through an automated stream" — matches the existing
+  push-pull dataflow / operator algebra substrate.
+- **Zamindary-OS** — archaic Indian-subcontinent landowner
+  term; fits the factory-as-multi-agent-host metaphor.
+
+## Carpentry-side gap
+
+The directive named carpentry as the second kernel but did
+NOT propose a name slate for it. Work scope when the
+maintainer iterates: parallel slate of carpentry-related
+candidates (Awl, Plane, Lathe, Mortise, Joinery,
+Workbench, Truss, Rafter, Dovetail, Tenon, Spoke, Adze,
+...) for `naming-expert` triage alongside the farm slate.
+
+## Composes with
+
+- **Otto-168** (Frontier naming-conflict origin)
+- **Otto-170** (Frontier rename research; nautical
+  candidate set including Starboard)
+- **Otto-175** / **Otto-175c** (Starboard adoption +
+  thematic-mapping; now reversed by this directive)
+- **Otto-237** (IP adoption-vs-mention discipline —
+  applies directly to "keep nautical/Elron research")
+- **Otto-244** (no-symlinks rule for cross-placement)
+- **Otto-275** (rapid-fire absorb / log-don't-implement)
+- **Otto-229** (append-only on history rows — don't edit
+  the Otto-175 rows; this memory + new BACKLOG row
+  capture the reversal forward)
+
+## Future Otto reference
+
+If a rename PR is being drafted: confirm the maintainer
+has named the two finalists (kernel-A + kernel-B), and
+that `naming-expert` has run IP + cross-substrate checks
+on each. Without both, defer per Otto-275. The
+ideation-seed slates above are NOT a license to pick.