CREATIVE SESSION × CRITIQUE SESSION → ARBITRATED PLAN · 2026-07-17

One system.
Five phases.
Distribution first.

Both sessions argued, then agreed on 90% of it. Here's the whole picture — nothing executes until you say go.

The integrated system

🔒 PRIVATE

You only · full context · cloned voice
📡
Signal Live
interruptible briefing · your voice · P1 ★
🎙️
Dictate + Auto
capture · car barge-in hardware
🛰️
Command
cockpit · costs · health
💰
Finance segment
Plaid read-only → drops into Signal · P2

🌐 PUBLIC

Testers & audience · gated · non-cloned voice
🎓
Mentor
standalone brand · the public-tier template
📣
LinkedIn cadence
the output pipe · P0 gate
📷
Photos share
shelved · rides the same primitive later
SHARED CORE — BUILD ONCE, EVERY SURFACE COMPOSES
Identity · private-by-default tags Voice · clone + segments + barge-in Memory · OB1 semantic Ledger · cost + latency contracts Skills · git registry + product-ops
"Park that topic" = a memory write that edits tomorrow's briefing. The loop closes through the core.
🔒 CLONED VOICE — PRIVATE SURFACES ONLY 🌐 PUBLIC = DIFFERENT VOICE, ALWAYS

The phase table

PhaseShipsGate / kill
P0NOW · days Unclog the output pipePublish the queued image-bench article · clear ~20 LinkedIn messages · analytics baseline snapshot. Identity tags (private-by-default) land in the data model — zero public routes. GATE: no P1 code until done
P1WEEK 1 ★ Signal Live — private MVP · TEST STRIP BUILDING NOWYour voice reads the nightly digest · barge-in → "park topic" edits tomorrow's briefing · one surface first (phone), car via existing wheel button when stable · one model · hard cost cap. KILL: <4 self-chosen mornings/wk by day 30
P2WEEKS 2–4 Deepen the loopAMBIENT CAPTURE (Byron, 07-18): open-mic option — speak over the briefing ("write a post on that", "more like this") → soft chime + on-screen chip → Action Ledger, narration never stops; only questions pause. Plus: more verbs · finance as private segment when Plaid done · second surface. Device test gate: echo cancellation must not false-trigger on the briefing audio. Only if P1 alive
P3MONTH 2 Action authority"Queue that to Dictate", "draft that post" — on the spend-guard enforcement plane · typed/tap confirmation is a permanent floor for anything destructive · per-skill model + latency contracts arrive here. Confirmation floor: non-negotiable
P4DROPPED Public tier — removed by Byron"Keep it simple. The report stays tailored to me." Complexity, auth surface, and impersonation risk all exit with it. The private-by-default tags stay (cheap insurance if this ever changes). Your call, 2026-07-17

Every property, one verdict

✓ KEEP — EARNING
  • Dictate + Auto · feeds Signal Live
  • Mentor · public-tier template + brand
  • Command · the observability plane
  • Morning Brief · becomes Signal Live's script
  • Branding Central · the P0 output pipe
◐ DATA DECIDES — AUG 16
  • RAI daily podcast · no listeners in 30d → weekly or freeze
  • benchmarks.arnao.ai · traffic or archive
  • City guides · traffic or archive
  • Rule: net-negative surface count this quarter.
◇ SHELVED — NOT DEAD
  • Photos MCP-share · rides the identity primitive later, rebuild cost ≈ zero
  • Signal Live public tier · dropped by Byron — simplicity wins
  • ByronOS as public brand · internal codename + content narrative only; you ship as Byron
  • "Governed AI" licensing · narrative now, build target after P4 proof

Where they disagreed — and the ruling

Public tier: security cliff vs. reuse of Mentor's machinery?
Overtaken by Byron: public offering dropped entirely — "keep it simple, tailored to me." The argument is moot; the whole auth cliff exits the plan. Cloned voice stays private by definition now.
Byron's day-one requirements: tiers, action authority, per-skill routing?
Ruling (critique's own concession): tiers ship in P0 as a data model — every memory and segment tagged private-by-default at write time, because retrofitting classification is the truly expensive path. Zero public routes until P4. Action authority and routing wait for P3 — they're runtime risks; tagging is just discipline.
Build Signal Live vs. fix distribution first?
The creative session conceded outright — one queued article and ~20 unanswered messages while building input tooling is the pattern to break. Ruling: P0 is a hard gate, not a parallel track. It's days of work, not weeks.
The harness converged — 2026-07-20 state
HER is the face (orb, one screen, dictate/brief/chat). Public Signal: weekly, input-ISOLATED (structurally cannot see personal data), 3-watcher council + 24h veto-window (silence = consent). Brand: private = the orb; public = STUDIO red/black; SherpaDude = the one QR-code front door with swipe-left to the public Signal. Chat verb rides Max-plan dispatch ($0 marginal). ByronOS stays an internal codename. Sonnet critique round commissioned; Byron holds final call on its findings.