Gimbo's Universe / AI Builder · The Personal AI Fleet
AI Experiments · Living system · 2026

I run my life
with a fleet
of agents.

Not one chatbot. An org chart of them — a chief of staff that sees the whole board, and specialists it delegates to. This is how a one-person life starts to run like a company: each agent owns a domain, drafts the work, and stops at the line only a human should cross.

Role
Architect · Builder · Operator
Status
Live · running daily
Pattern
Manager-of-agents · brain + skills + ledgers
Built with
Claude · markdown brains · cron
§ The shift

From doing the work
to managing a fleet

For a year I used AI like everyone else: one chat, one task, repeat. The shift came when I stopped asking "do this for me" and started asking "who on my team should own this?" — and then built the team. A chief of staff at the top. Specialists underneath. Each with a written-down version of my own judgment, so they can make the small calls and hand me only the ones that matter.

Before

One doer

Me + a chatbot, starting from scratch every time. Context died with each conversation. Nothing accumulated.

After

A fleet

An org of agents, each owning a domain, each with memory, ledgers, and a daily rhythm. Work compounds.

The lever

Leverage, not automation

The win isn't speed. It's that a single person can hold six lanes of life at once — and not drop the ball.

§ The org chart

A chief of staff,
and the specialists it delegates to

The top of the chart sees the whole board and routes work. Each specialist owns one domain and inherits the same "virtual twin" of how I think — so nothing contradicts itself.

Meta-agent · 参谋长
Chief of Staff
Sees the whole board · daily briefing · routes work to the right specialist · catches what's falling through the cracks
│   delegates to   ↓
投资官 · CIO
Chief Investment Officer
Researches & monitors the portfolio with a value-investing discipline — never executes a trade
营销官 · CMO
Chief Marketing Officer
Turns what I make into things people can read — drafts & adapts per channel, never auto-publishes
健康官 · CHO
Chief Health Officer
Keeps the health line from slipping — movement, food, and mental wellbeing — by lowering the bar to log, never by nagging
Day job · 供应链
Planning Agents
A planning + ordering + reconciliation stack for my work in NZ healthcare distribution
↑   feeds every cell   ↑
Horizontal layer · 进化官 · EVO
Chief Evolution Officer
Captures everything I read, watch, hear and talk through — distills a "so what," then routes the signal to whichever cell should change because of it. The few things that change how I think flow back to upgrade the whole system. The conveyor that turns consumption into change.
CAPTURE → DISTILL → ROUTE → CLOSE THE LOOP
↑ This very page was drafted by the CMO cell, then published by me. That gap is the whole point.
§ The pattern

Every agent is built
the same four ways

No agent is a clever prompt. Each is a small, durable system that the next one can copy.

1 · Brain

A virtual twin

Markdown files that write down who I am, how I decide, and the voice to report back in. Specialists inherit the top-level brain instead of duplicating it — one source of "how Gimbo thinks."

2 · Skills

Invocable on call

Each agent is a skill I summon by name. It reads its brain, does the domain work, and reports in a tight, scannable format — never a wall of text.

3 · Ledgers

One source of truth

Open loops, a portfolio, a content pipeline — living files, not vibes. State survives between sessions, so the work compounds instead of resetting.

4 · Rhythm

It runs itself

Scheduled jobs wake the right agent at the right time — a morning briefing on weekdays, a portfolio review tied to the tax year. The fleet has a heartbeat.

§ What I learned

Five rules that make
a fleet you can trust

Building it taught me more about delegation — to people and to machines — than any management book.

01

Agents draft. Humans decide.

Every specialist stops before the irreversible act — no trade is ever executed, nothing is ever auto-posted. The agent does 95% and hands me the last 5% that actually carries risk.

02

One source of truth per domain.

If a fact lives in two places, it's already wrong in one. Each domain has exactly one ledger, and everything else reads from it.

03

Honesty beats coverage.

If a run fails or data didn't load, the agent says so — plainly. A confident wrong answer is worse than a flagged gap. No fabricated numbers, ever.

04

Privacy is a first-class constraint.

Anything that might go public is desensitized first — no employer, no real names, no private figures. The rule is wired into the agents, not left to memory.

05

Inherit, don't duplicate.

Specialists share one brain for "how I think," and only add what's unique to their domain. Change my mind once, and the whole fleet updates.

The point isn't
automation.
It's leverage.

A fleet you can trust runs on written-down rules, not vibes — and it gives one person the reach of a small team.

A living system · still growing · drafted by the fleet, shipped by the human