From 2023 AI to a fleet that works for Byron — plan, critique, and what shipped (2026-10-18)

Byron's brief, condensed: "All of what I do today seems very 2023 AI. I ask questions and direct, but none of the superintelligence that could be autonomous is taking shape. I get an idea, you build a proposal, I forget, get busy." Goals named: get rich; finish the Responsible AI book; world-leading RAI researcher, speaker, influencer, engineer; triathlete-fit; climb or hike monthly; Ben, Sophia, grandkids, friends; Antarctica within 6–12 months; last 100 miles of the Camino in 2027; a 14er (Whitney) in 2027; one official 5K in 2027; perform comfortably on ukulele, piano and guitar; tame distractions; never lose the work we do.

1. What the audit actually found (read-only sweep, 7 agents, ~1,000 files)

AreaFindingEvidence
GoalsNo agent knew about Antarctica, the Camino, Whitney, the grandkids, the instruments, or Cole. OB1 keyword count: 0 hits for all of them. Signal only knew the brand goal and a triathlon nudge with a null state.OB1 agent_memories 212 rows, 195 of them Gia's own log; goal.md 2026-10-16
Follow-upsNo commitment tracker. "Cole + mentor links" is written nowhere. byron-todos.json holds 179 items blocked on Byron and Signal does not read it.byron-todos.json, Signal SKILL.md gather list
MemoryGia's dreaming consolidation dead since June 29. Claude Code memory index at 21 KB (past truncation). Proposals get written, then orphaned (proposals index last built Jul 21).memory/dreaming/, proposals-site/index.html
Autonomy19 Gia crons (all ok) + ~45 LaunchDaemons. ria-mcp crash-looped 14,669 times. photolib-sync, libeso-health exit 1 every run. fleet-snapshot plists never loaded; inventory-audit never ran. harness-worker healthy but idle: 0 new cards.launchctl print
SecurityNo named security agent and no "is X safe?" path. Scans in six places (sentinel, keywatch, skill-scan, SkillSpector, broker, chaperone) with no single screen. security.installPolicy unset on every agent, so an agent-run skills install bypasses the scanner. Chaperone hook not wired in settings.json. Sentinel audits 1 of ~295 surfaces.security map
Skills7 Gia skills silently skipped (missing frontmatter). ~38 skills never mentioned to Gia. 10 repeated manual patterns with no script.fleet-skills-lint before: 15 bad frontmatter, 91 unmentioned
ModelsGia/Gia2 on Opus 5 by design: OpenClaw 7.1/8.34 cannot call Opus/Sonnet 5.5 direct (thinking-param schema), fixed by OpenClaw 2026.9.7 (fleet plan, awaiting approval). Mia's fallbacks stale (sonnet-4-6, gpt-4o, grok-3). nano-banana-pro skill pinned to a Nov-2025 preview id; gemini-nano-banana-2.1 (Oct 6) and gemini-3-pro-image GA exist; leaderboards put GPT Image 2.x first for text rendering.live /v1/models, OpenRouter list
JevNot a router in live use. Benchmarks (Oct 6): fixed GPT-6.1 Sol beat every router on cost at equal accuracy; jev-router was 2× Sol's cost but the only one escalating hard tasks. Jev's real value for Byron is the calibrated yes/no gate (gate.arnao.ai draft, book chapter).router-bench summary
OCENot implemented. Blocked at occ dev up on a Colima sysctl the classifier refused ("Security Weaken"). Needs Byron's one line.~/oce/PILOT.md
OB1Healthy (pgvector, 212 rows) but functionally Gia's diary; 3 of 212 rows reviewed.psql
TrafficPlausible exists (self-hosted) but its script 502s; no digest consumes it.memory 2026-10-06
PrivacyVIP firewall is prompt-level only. Mia's WhatsApp allowlist includes Ben, Sophia, Liza. OB1 shared across agents. No vault for private facts.profile.yaml, openclaw.json

2. The critique (the Nate-B-Jones / Willison / Karpathy lens)

The diagnosis is not "too few agents." It is "no spine." You have ~65 scheduled jobs and 19 crons. They run. They just run about nothing you care about, because the only goal any of them can read is the brand goal, and nothing closes a loop back to you except a podcast you may not play. Jones's named top failure is premature complexity: multi-agent before sessions survive, orchestration before a goal file. That is exactly this fleet: 14,669 crash restarts of an MCP daemon nobody noticed, a harness worker that has produced zero new cards, a dreaming job dead for four months.

Three structural errors, in order of cost:

  1. Goals live in your head. Every "superintelligent" behaviour you want (opportunity hunting, follow-up nagging, trip planning, practice cadence) is downstream of a machine-readable goals file with dates. It did not exist until today.
  2. Loops don't close. Proposal → page → silence. Audit → finding → nothing. Todo → 179 blocked items nobody voices. The fix is not another agent; it is one commitments store and one daily ask with ≤3 yes/no taps, fed into the channel you already tap (Signal action cards).
  3. Trust is unenforced at the one place it matters. Skill installs are the supply-chain door (Snyk: 13% of 4k scanned skills critical; ClawHavoc: 1,184 malicious ClawHub skills). You had scanners but no gate. Today the gate is on.

**What I would not build:** a "career agent" container, a "traffic agent," a "relationship agent." Each becomes another unmonitored daemon. Build them as lanes in things that already reach you: Opportunity Scout as a Gia cron emitting cards; traffic as a weekly line in Signal from Plausible once it's fixed; relationships as private-vault prompts Claude Code raises only to you.

Jev: use it where risk lives, not where routing lives. Benchmarks say a fixed frontier model beats routers on cost. But a calibrated yes/no gate in front of Gia2's broker ("is this outbound action consistent with Byron's policy?") is the cheapest real safety control you can add, and it is literally your book chapter. Proposed, not built (needs your call on the policy questions).

OCE: stay parked. Gia2 already borrowed the ideas; OCE is K8s-shaped and pre-1.0. If you want the pilot, it is one sysctl line you run.

Models: the right move is the fleet plan (OpenClaw 2026.9.7 → Opus/Sonnet 5.5 direct with caching), not hand-bumping ids the runtime can't call. Image model: measured today, not asserted.

Recursive self-improvement, honestly: what is achievable now is recursive self-audit: every 3 hours, inventory the machine (daemons, containers, ports, DNS, skills, hooks, MCP, Vercel projects), diff against yesterday, scan anything new with the matching scanner, baseline the rest, show it on one screen. That is built today (secwatch). Agents rewriting their own skills unsupervised is the opposite of what the security research recommends; Gia2's autonomous skill-workshop is now explicitly off.

3. What shipped today

<!-- results:auto -->

Everything below is live on the Mini or on arnao.ai as of the evening of 2026-10-18. Each line was verified by the builder that shipped it; where verification was partial, it says so.

Trust & security

Goal spine & loops

Skills & tooling (harness)

Agents & surfaces

Models (measured, not asserted)

Money (first real ledger)

Surfaces, traffic, Signal

Cross-tool context (https://context.arnao.ai/)

After the critique (same evening)

<!-- /results:auto -->

4. What needs Byron (each one tap or one line)

<!-- needs:auto -->

Everything that needs you now arrives as one Telegram card each morning at 07:30 with at most three items. Tonight, three things only:

  1. Tap the Morning Card when it arrives (Approve / Edit / Rewrite on the FAccT draft; TRUST registration is Oct 24).
  2. Connect your other tools once from the setup page (the link carries your key, so it is in the chat reply only).
  3. One sudo line on the Mini fixes the mentor database connection and turns on encrypted snapshots: sudo bash ~/fleet-reports/runners/sudo-once-2026-10-18.sh

Pull-only, never announced again: Security Center and Finance at https://command.arnao.ai/, the demo console https://demo.arnao.ai/, the Signal portal https://signal-portal.arnao.ai/, ~/ops/atlas/, ~/ops/finance/FINANCE.md, ~/ops/drafts/, the idle-surface delete runner and report in ~/fleet-reports/, the held Signal weekly episode, the OCE sysctl, powering on the Windows PC and NAS (photo sync and off-box backup resume on their own), the LinkedIn PC sign-in (say "LinkedIn link" at the PC), the Brave API key seen in a daemon plist (rotate when convenient).

<!-- /needs:auto -->

4b. Self-critique — Fable adversarial pass (2026-10-18, claude-fable-5-1, full text)

Its verdict: the audit was good and the response to "I'm too busy" was nine new destinations and nine asks. Four things reach Byron unprompted; nine require him to go look, and dashboards here have a measured ~1% read rate. Zero words of book text were produced while the fleet's own telemetry is the best RAI case study he owns. Resolve the tension by freezing fleet expansion for 90 days: only security fixes and things that produce book or abstract text; the three CFP deadlines (Oct 27, Oct 31, Nov 2) are the only items that compound into "world-leading".

What changed because of it (same evening):

Where I disagree, and why: the public Tailscale funnel stays on for Plausible. It exposes only Plausible's own HTTP through Tailscale's TLS proxy, not the Mini, Byron chose self-hosted analytics deliberately, and switching to a hosted service is a product decision, not a security fix; the Plausible image is added to the Sunday maintenance pull. The demo console stays public: its fleet graph contains nothing that is not already in the public Gia2 proposal, and showing the fleet is the point of the console. The context hub keeps the keyed URL because ChatGPT, Claude.ai and Grok custom connectors cannot send headers; the mitigations are a short pack, no vault content, a sanitizer that fails closed on secret, phone, tailnet and email patterns, and write-backs that are never executed and are audibly tagged. The owner key is rotatable in one command.

5. Sources