From a61455a4ea0dc9d98fd0969ba2414496f426de3d Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 05:37:55 -0400 Subject: [PATCH 1/4] =?UTF-8?q?backlog:=20Otto-168=20"Frontier"=20naming?= =?UTF-8?q?=20conflict=20with=20OpenAI=20Frontier=20=E2=80=94=20rename=20f?= =?UTF-8?q?actory=20UI?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Aaron Otto-168: "i just found this https://openai.com/index/ introducing-openai-frontier/ ... naming conflicts ... also absorb everyting lol, it composes nicely ... backlog" OpenAI announced an "OpenAI Frontier" (Otto-168 WebFetch got 403; scope TBD next tick via WebSearch or URL-retry). Factory currently uses "Frontier UI / Frontier UX" as the public- facing user-UI layer name. Brand conflict. Three-class usage scope locked so rename surgically targets the conflicting usage without disrupting technical or industry vocabulary: (a) CONFLICTING (rename): frontier-ux-zora-evolution design doc, "Frontier UI/Frontier plugin" BACKLOG rows, memory pointers. (b) TECHNICAL-LITERATURE (keep): Timely-Dataflow antichain frontier, Naiad partial-order composition, bloom-filter research frontier. (c) INDUSTRY-TERM (keep): "frontier model", "frontier LLM", frontier-environment confidence memory. Rename candidates (Zora / Starboard / Bridge / Horizon / Vantage / Aurora) with analysis; Aaron + naming-expert make the call. 6-step action sequence filed. Non-actions: don't rename literature/industry uses; don't ship same-tick as discovery; don't pick name unilaterally. Composition: Aurora+Zeta+KSK naming triangle stays intact; DST+Cartel-Lab+Veridicality internal module names unaffected. Priority P1 (active brand conflict); effort 3×S (scope research + naming + rename PR). Placed under P2 research-grade section (adjacent to Frontier plugin inventory row, line ~4360), not BACKLOG tail — avoids positional-append conflict pattern that cost #334 this session. Co-Authored-By: Claude Opus 4.7 --- docs/BACKLOG.md | 116 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 116 insertions(+) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index 523b5d03..672e1f75 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -4714,6 +4714,122 @@ systems. This track claims the space. - [ ] **Ongoing memory-sync mechanism — keep in-repo `memory/` mirrored with auto-memory writes during each Otto tick.** Aaron 2026-04-24 Otto-113 directive *"our memories should all be checked in now"* + Otto-114 confirmation that in-repo memory/ is the natural home for ALL memory types. Otto-113 one-shot sync (PR #307) mirrored 439 files. Going forward, every Otto tick that writes to `~/.claude/projects/.../memory/` should also land new/updated files in-repo `memory/` with matching MEMORY.md pointer update (per memory-index-integrity + memory-reference-existence-lint workflows). Proposed mechanisms: (a) end-of-tick skill that rsyncs new memories to a branch + PRs them; (b) direct-to-repo writes with auto-memory as read-cache; (c) GHA cron periodic sync. Initial preference: (a) for CLI-tool compatibility today, (b) long-term. Also includes path-unification design (decide whether to deprecate the `~/.claude/projects/...` path for this project entirely or keep as staging). Priority P2 research-grade; effort S (rsync skill) + M (direct-write tooling). Composes with `memory/feedback_natural_home_of_memories_is_in_repo_now_all_types_*.md` (Otto-114 policy) + PR #307 one-shot sync + memory-index-integrity workflow. +- [ ] **"Frontier" naming conflict with OpenAI Frontier + — rename factory's UI-layer "Frontier" to something + non-conflicting.** Aaron 2026-04-24 Otto-168: *"i just + found this https://openai.com/index/introducing-openai- + frontier/ ... naming conflicts ... also absorb everyting + lol, it composes nicely ... backlog"*. OpenAI announced + something called "OpenAI Frontier" (Otto-168 unable to + fetch the page directly — 403 response; scope TBD next + tick via WebSearch or URL-retry). Regardless of shape, + the factory's public-facing "Frontier UI / Frontier UX" + name creates brand confusion if Zeta's UI ships publicly + under that name. Action: rename the factory's user- + facing surface to something non-conflicting; preserve + technical-literature and industry-term uses of + "frontier" (three-class distinction below). + + **Scope — three classes of "Frontier" usage + (137 grep hits total):** + + (a) **CONFLICTING (must rename).** Factory's public- + user-facing UI layer name: + - `docs/research/frontier-ux-zora-evolution-2026-04-24 + .md` — primary UX design doc + - BACKLOG row ~4381 / ~4408 — "Frontier UI" + "Otto-63 + Frontier burn-rate-UI" cross-refs + - `memory/feedback_aaron_dont_wait_on_approval_log_ + decisions_frontier_ui_is_his_review_surface_*.md` + and siblings + + (b) **TECHNICAL-LITERATURE (keep).** "Frontier" as + established term in timely-dataflow / differential- + dataflow / DBSP academic lineage: + - `docs/WATERMARK-RESEARCH.md` — Timely-Dataflow + antichain frontier + `Frontier` type + - `docs/research/retraction-safe-semi-naive.md` — + "frontier/partial-order composition (Naiad §3)" + - `docs/research/bloom-filter-frontier.md` — "research + frontier" = cutting-edge-design-space metaphor + + (c) **INDUSTRY-TERM (keep).** "Frontier model" / + "frontier LLM" / "frontier moves fast" — generic AI- + industry vocabulary: + - `docs/research/harness-run-*.md` "frontier-model + baselines" + - `docs/research/claude-cli-capability-map.md` + "frontier research" tier descriptor + - `docs/research/hacker-conferences.md` "frontier LLM + red-team work" + - `memory/feedback_frontier_confidence_*` — frontier- + environment confidence (different sense entirely) + + **Rename candidates (Otto proposes; naming-expert + persona + Aaron final call):** + - **Zora** — already in UX design doc filename + (`frontier-ux-zora-evolution`); inherits directly; + preserves Star-Trek-computer-but-BETTER design + language. + - **Starboard** — Star Trek bridge-facing term + + navigation nod; Zeta-native coinage. + - **Bridge** — simple, Star-Trek-adjacent, no known + major product conflict. + - **Horizon** — thematic sibling to "Frontier"; + Windows NT Horizon VDI minor conflict. + - **Vantage** — clean of conflicts; less thematic. + - **Aurora** — already in factory naming triangle + (Aurora+Zeta+KSK); conflating could leak UI into + governance-layer conceptual space. Not + recommended. + + **Action sequence:** + 1. Fetch + summarize OpenAI Frontier announcement + (next tick; WebFetch 403 this tick; try WebSearch + or URL-retry). + 2. Assess conflict severity (product vs program vs + research-name scope). + 3. Naming-expert persona consultation on candidates; + weight factors include trademark risk, voice + consistency with Zora/Star-Trek design language, + alignment with Aurora/Zeta/KSK naming triangle. + 4. Aaron final call on new name. + 5. Repo-wide rename PR: UX design doc + BACKLOG rows + + memory pointer updates. Class (b) + (c) usages + untouched. + 6. Memory entry locking the new name canonically + + archiving the "Frontier" period as pre-Otto-168 + history. + + **Non-actions:** + - Do NOT rename technical-literature "frontier" + usages (broader community vocabulary). + - Do NOT rename industry-term "frontier model" / + "frontier LLM" usages. + - Do NOT ship the rename same-tick as discovery. + Naming decisions that affect public branding + deserve deliberate treatment. + - Do NOT unilaterally pick a name from Otto's + candidate list. Aaron is the concept owner. + + **Composition (per Aaron "composes nicely").** + Composes with: + - `docs/research/frontier-ux-zora-evolution-2026-04- + 24.md` — primary rename target; "Zora" in filename + is one candidate. + - BACKLOG "Frontier plugin inventory" row (directly + below) — cross-reference update post-rename. + - Aurora / Zeta / KSK naming triangle (`docs/ + definitions/KSK.md`, Amara 5th/7th/16th ferries) — + rename slots into this ecosystem without adding a + fourth brand. + - DST + Cartel-Lab + Veridicality internal module + names — unaffected (not public-UI). + + Priority P1 (active brand conflict); effort S + (rename PR) + S (naming-expert) + S (OpenAI Frontier + scope research). + - [ ] **Frontier plugin inventory + in-source discipline — catalogue the plugins Zeta's factory needs for the Frontier UI + substrate (both `.claude-plugin/` and `.codex-plugin/`), restructure around the new skill-vs-plugin best practices, and enforce that all plugins land in-source rather than in harness-local sandboxes.** Aaron 2026-04-24 Otto-103 directive: *"we should backlog what plugins we need for frontier, seems like a big opportunity to restruture for new best practices and everyting else, we also wanna make sure our plugins are making it into source and not some harness sandbox. backlog."* **Context.** After session restart Aaron flagged five Codex built-in skills (Image Gen / OpenAI Docs / Plugin Creator / Skill Creator / Skill Installer) + asked Otto to figure out skills-vs-plugins distinction. Otto-103 research (PR #290, `docs/research/codex-builtins-skills-vs-plugins-factory-integration-2026-04-24.md`) established: **plugin = distribution/installation unit (JSON manifest + bundle); skill = single capability unit (SKILL.md)**. Plugins are containers; skills are contents. This row goes further — catalogue what plugins the factory itself needs. From 670963657652c66176a9f55914613c1ad7ea8840 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 05:39:51 -0400 Subject: [PATCH 2/4] =?UTF-8?q?backlog:=20Otto-169=20WebSearch=20completes?= =?UTF-8?q?=20OpenAI=20Frontier=20scope=20research=20=E2=80=94=20severity?= =?UTF-8?q?=20HIGH?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit WebSearch unblocked the deferred Otto-168 URL-research. OpenAI Frontier (launched 2026-02-05) is a full enterprise AI-agent platform — not internal research, not a model name. Direct overlap with the factory's "Frontier UI" agent-orchestration space. Consulting-partnership distribution (Accenture / BCG / Capgemini / McKinsey) guarantees wide enterprise-AI dissemination. Severity assessment: HIGH. Filed inline to the existing BACKLOG row. Action sequence steps 1 (scope fetch) + 2 (severity) now complete; steps 3-6 (naming-expert + Aaron final call + rename PR + memory archive) still pending. Co-Authored-By: Claude Opus 4.7 --- docs/BACKLOG.md | 55 ++++++++++++++++++++++++++++++++++++------------- 1 file changed, 41 insertions(+), 14 deletions(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index 672e1f75..cee13684 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -4719,16 +4719,42 @@ systems. This track claims the space. non-conflicting.** Aaron 2026-04-24 Otto-168: *"i just found this https://openai.com/index/introducing-openai- frontier/ ... naming conflicts ... also absorb everyting - lol, it composes nicely ... backlog"*. OpenAI announced - something called "OpenAI Frontier" (Otto-168 unable to - fetch the page directly — 403 response; scope TBD next - tick via WebSearch or URL-retry). Regardless of shape, + lol, it composes nicely ... backlog"*. + + **OpenAI Frontier scope (Otto-169 WebSearch):** launched + 2026-02-05 as an **enterprise AI-agent platform** for + building, deploying, and managing AI agents at + enterprise scale. Not internal research, not a model + name — a full product in the agent-orchestration space. + Interoperates with agents from OpenAI, enterprises, + Google / Microsoft / Anthropic (third-party). Initial + enterprise customers: Uber, State Farm, Intuit, Thermo + Fisher Scientific. Frontier Partners program (AI-native + builders: Abridge, Clay, Ambience, Decagon, Harvey, + Sierra). Frontier Alliances program (consulting giants: + Accenture, Boston Consulting Group, Capgemini, + McKinsey). Companion feature "Workspace Agents" + (successor to custom GPTs; plugs into Slack, Salesforce, + etc.). + + **Conflict severity: HIGH.** The OpenAI Frontier + product is in exactly the agent-orchestration / UI- + layer space where the factory's "Frontier UI / Frontier + UX" operates (Star-Trek computer but BETTER, user- + facing surface for agents). Consulting partnerships + guarantee the OpenAI Frontier name will be widely + disseminated in enterprise-AI procurement conversations + in 2026. Shipping Zeta's UI publicly under "Frontier" + would create immediate brand confusion with a + well-capitalized competitor. + + **Regardless of the specific OpenAI product shape,** the factory's public-facing "Frontier UI / Frontier UX" - name creates brand confusion if Zeta's UI ships publicly - under that name. Action: rename the factory's user- - facing surface to something non-conflicting; preserve - technical-literature and industry-term uses of - "frontier" (three-class distinction below). + name creates brand confusion if Zeta's UI ships + publicly under that name. Action: rename the factory's + user-facing surface to something non-conflicting; + preserve technical-literature and industry-term uses + of "frontier" (three-class distinction below). **Scope — three classes of "Frontier" usage (137 grep hits total):** @@ -4784,11 +4810,12 @@ systems. This track claims the space. recommended. **Action sequence:** - 1. Fetch + summarize OpenAI Frontier announcement - (next tick; WebFetch 403 this tick; try WebSearch - or URL-retry). - 2. Assess conflict severity (product vs program vs - research-name scope). + 1. ~~Fetch + summarize OpenAI Frontier announcement~~ + DONE Otto-169 WebSearch (see scope block above). + 2. ~~Assess conflict severity.~~ DONE Otto-169: + **HIGH** — direct overlap in agent-orchestration / + UI-layer space + enterprise-consulting-partnership + distribution channels. 3. Naming-expert persona consultation on candidates; weight factors include trademark risk, voice consistency with Zora/Star-Trek design language, From aed14a1f6580fa557df2fcadd29411953112142b Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 08:05:03 -0400 Subject: [PATCH 3/4] fix(#348): markdown inline-code spans + URL continuous on one line MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Resolves 5 P1 review threads all reporting the same class of issue: inline-code spans (backticks) and URLs broken across newlines. CommonMark inline-code spans cannot span newlines — the `span` is literally broken as rendered, and readers cannot copy the path cleanly. Same for URLs: Markdown auto-linkers stop at whitespace. Fix pattern: move the full backticked path (or URL) onto its own line, wrapping the surrounding prose instead. No content removed. Threads addressed: - 59Vtvx — OpenAI Frontier URL split across line break - 59WtwY — `docs/research/frontier-ux-zora-evolution-*.md` split (first occurrence, Class-a list) - 59Wtwq — `memory/feedback_aaron_dont_wait_on_approval_log_ decisions_frontier_ui_is_his_review_surface_*.md` split; also updated to the concrete landed filename - 59Wtw8 — same UX design-doc path split (Composition section) - 59WtxM — `docs/definitions/KSK.md` split Same fix pattern as PR #352 (server-meshing-*.md path). --- docs/BACKLOG.md | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index cee13684..f61f9f6d 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -4717,9 +4717,10 @@ systems. This track claims the space. - [ ] **"Frontier" naming conflict with OpenAI Frontier — rename factory's UI-layer "Frontier" to something non-conflicting.** Aaron 2026-04-24 Otto-168: *"i just - found this https://openai.com/index/introducing-openai- - frontier/ ... naming conflicts ... also absorb everyting - lol, it composes nicely ... backlog"*. + found this + https://openai.com/index/introducing-openai-frontier/ + ... naming conflicts ... also absorb everyting lol, it + composes nicely ... backlog"*. **OpenAI Frontier scope (Otto-169 WebSearch):** launched 2026-02-05 as an **enterprise AI-agent platform** for @@ -4761,12 +4762,13 @@ systems. This track claims the space. (a) **CONFLICTING (must rename).** Factory's public- user-facing UI layer name: - - `docs/research/frontier-ux-zora-evolution-2026-04-24 - .md` — primary UX design doc + - Primary UX design doc: + `docs/research/frontier-ux-zora-evolution-2026-04-24.md` - BACKLOG row ~4381 / ~4408 — "Frontier UI" + "Otto-63 Frontier burn-rate-UI" cross-refs - - `memory/feedback_aaron_dont_wait_on_approval_log_ - decisions_frontier_ui_is_his_review_surface_*.md` + - Memory pointer (concrete file in + `memory/MEMORY.md`): + `memory/feedback_aaron_dont_wait_on_approval_log_decisions_frontier_ui_is_his_review_surface_2026_04_24.md` and siblings (b) **TECHNICAL-LITERATURE (keep).** "Frontier" as @@ -4841,15 +4843,15 @@ systems. This track claims the space. **Composition (per Aaron "composes nicely").** Composes with: - - `docs/research/frontier-ux-zora-evolution-2026-04- - 24.md` — primary rename target; "Zora" in filename - is one candidate. + - Primary rename target — "Zora" in filename is one + candidate: + `docs/research/frontier-ux-zora-evolution-2026-04-24.md` - BACKLOG "Frontier plugin inventory" row (directly below) — cross-reference update post-rename. - - Aurora / Zeta / KSK naming triangle (`docs/ - definitions/KSK.md`, Amara 5th/7th/16th ferries) — - rename slots into this ecosystem without adding a - fourth brand. + - Aurora / Zeta / KSK naming triangle — rename slots + into this ecosystem without adding a fourth brand + (see `docs/definitions/KSK.md`, Amara 5th / 7th / + 16th ferries). - DST + Cartel-Lab + Veridicality internal module names — unaffected (not public-UI). From 1b61f9106b71aae1a9525066ba7cf718c86032c5 Mon Sep 17 00:00:00 2001 From: Aaron Stainback Date: Fri, 24 Apr 2026 08:54:00 -0400 Subject: [PATCH 4/4] =?UTF-8?q?fix(#348):=202=20review=20threads=20?= =?UTF-8?q?=E2=80=94=20Otto-63=20dangling=20ref=20+=20KSK.md=20proposed-pa?= =?UTF-8?q?th=20clarification?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/BACKLOG.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index f61f9f6d..58b248c8 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -4764,8 +4764,10 @@ systems. This track claims the space. user-facing UI layer name: - Primary UX design doc: `docs/research/frontier-ux-zora-evolution-2026-04-24.md` - - BACKLOG row ~4381 / ~4408 — "Frontier UI" + "Otto-63 - Frontier burn-rate-UI" cross-refs + - "Frontier UI" + Frontier burn-rate-UI concept, + cross-referenced in the plugin-inventory row below + (no standalone BACKLOG row yet — the concept lives in + memory pointers and is referenced inline here) - Memory pointer (concrete file in `memory/MEMORY.md`): `memory/feedback_aaron_dont_wait_on_approval_log_decisions_frontier_ui_is_his_review_surface_2026_04_24.md` @@ -4850,8 +4852,9 @@ systems. This track claims the space. below) — cross-reference update post-rename. - Aurora / Zeta / KSK naming triangle — rename slots into this ecosystem without adding a fourth brand - (see `docs/definitions/KSK.md`, Amara 5th / 7th / - 16th ferries). + (see `docs/definitions/KSK.md` (proposed, landing via + the "KSK naming definition doc" BACKLOG row above), + Amara 5th / 7th / 16th ferries). - DST + Cartel-Lab + Veridicality internal module names — unaffected (not public-UI). @@ -4880,7 +4883,7 @@ systems. This track claims the space. 1. **`zeta-codex-plugin`** (the Otto-103 A/B/C question). In-tree manifest at `.codex-plugin/plugin.json` pointing at existing `.codex/skills/**` (Option B from Otto-103) is the likely shape if we ship this. Aaron's call per Otto-103 specific-ask. 2. **`zeta-claude-plugin`** (parallel for Claude Code). Currently Zeta's `.claude/skills/**` is unbundled; a `.claude-plugin/plugin.json` at repo root would make the skill suite installable as a single plugin. Useful for other projects that want to consume Zeta's skill library. - 3. **`frontier-UI-plugin`** (speculative; ties to the Otto-63 Frontier burn-rate-UI row). Plugin that surfaces Zeta's factory state (tick-history / memory-index / alignment-trajectory-plot / PR-queue-health) to the Frontier UI surface. Requires the Frontier UI to exist first; not a near-term deliverable. + 3. **`frontier-UI-plugin`** (speculative; ties to the Frontier burn-rate-UI concept cross-referenced in the Frontier-naming-conflict row above). Plugin that surfaces Zeta's factory state (tick-history / memory-index / alignment-trajectory-plot / PR-queue-health) to the Frontier UI surface. Requires the Frontier UI to exist first; not a near-term deliverable. 4. **`zeta-decision-proxy-plugin`** (PR #222 decision-proxy-evidence schema). Plugin exposing the `docs/decision-proxy-evidence/` substrate as first-class tooling for any agent (Otto / future Codex Otto / Aminata / etc.) that needs to file evidence records. 5. **`zeta-drift-detector-plugin`** (future; depends on the provenance-aware-bullshit-detector implementation from 8th-ferry arc landing). Plugin wrapping SD-9 + DRIFT-TAXONOMY pattern 5 + citations-as-first-class + the bullshit-detector. Would give any agent a `$drift-check` invocation. @@ -4907,7 +4910,7 @@ systems. This track claims the space. - **`.claude/skills/**` (~200 skills)** — largest factory-authored skill surface; classification matrix in Phase 1 decides how it gets plugin-wrapped (if at all). - **`~/.claude/settings.json` `enabledPlugins`** — inspected via project settings; third-party plugin consumption separate from factory-authored output. - **GOVERNANCE.md §4 skill-creator workflow** — skill authoring discipline; plugin authoring discipline is parallel. - - **Otto-63 Frontier burn-rate-UI** row — plugin #3 (`frontier-UI-plugin`) ties directly; dependent on Frontier UI existing. + - **Frontier burn-rate-UI concept** (cross-referenced in the Frontier-naming-conflict row above; no standalone BACKLOG row yet) — plugin #3 (`frontier-UI-plugin`) ties directly; dependent on Frontier UI existing. - **Otto-79 cross-harness-edit-no** — each harness's plugins live in its own substrate (`.claude-plugin/` vs `.codex-plugin/`); factory discipline applies to both independently. **Scope limits:**