../missions / life-os
Ethan Life OS — an AI-agent operating system
One founder operating like a team: briefs in, verified work out, and lessons compounding across every project — Resonate included.
- problem
- A solo founder is the bottleneck: strategy, research, building, and review all queue behind one person. Most 'AI productivity' setups organize work but don't do it — they hand you more to manage, not more throughput.
- my_role
- I designed and built the whole system — the orchestration model, the agent contracts, the folder protocols, the gated build loop, and the memory that compounds. It's the operating layer I run everything else through, Resonate included.
- system_built
- A Markdown-only vault plus an agent runtime in Claude Code: one orchestrator that only decomposes and delegates, eleven specialist subagents with defined contracts, an inbox → outbox → archive flow under a single-source-of-truth rule, and an autonomous build loop that gates every change.
- proof
- 11 specialist agents · 30+ slash commands · an autonomous build loop with four verification gates (typecheck · unit · behavioral RLS · mutation-score) · test-first delivery · a strictest-wins review chain · git-backed and in daily use.
- proof_status
- private artifact / private metric
- proof_note
- Private working system. Public proof stays on architecture and method; the vault itself stays private.
- artifact_note
- Private build artifact; internals stay private by design.
- why_it_matters
- This is the honest version of 'I move like a team.' It isn't a claim — it's the machine that lets one founder run a company at real throughput, and it's why Resonate's strategy, research, red-teams, and build exist at the depth they do.
- Specialist Agents
- 11
- Slash Commands
- 30+
- Build-Loop Gates
- 4
- Daily Driver
- yes
Ethan Life OS is a Markdown-only knowledge vault plus an agent-orchestration runtime, run inside Claude Code and backed by Git. The operating model is deliberate: I talk to exactly one orchestrator agent — the conductor — who never does domain work himself. He decomposes intent into written briefs and delegates every substantive task to a roster of eleven specialist subagents, each with a defined contract: research, build, engineering/harden, librarian, sales, fundraising, adversarial red-team, observability, reflection, team-optimization, and financial modeling.
Work flows through per-agent inbox → outbox → archive folders under a strict single-source-of-truth discipline, wired together with a [[wikilink]] graph and frontmatter schemas. The headline capability is the autonomous build loop: select → scope-gate (architecture, security, and UI review lenses) → test-first build (a failing test is the first deliverable) → independent verification (typecheck · unit · behavioral RLS · a mutation-score gate) → a strictest-wins review chain. Adversarial red-team is a first-class stage, not an afterthought, and a compounding 'lessons' memory gets read back into future briefs so the system gets sharper over time.
It started life as an overbuilt Notion 'Life OS' — good at organizing, but it couldn't do the work. The rebuild turned it into a runtime that actually executes: the same operating-system instinct, now pointed at shipping real software and running a company. Resonate is the highest-priority project managed through it — its strategy, research, product specs, GTM, red-teams, and financial models are all produced by these agents.
- One orchestrator that never does domain work — only decomposes and delegates — keeps the whole system legible as it scales.
- A failing test as the first deliverable makes 'done' falsifiable instead of vibes-based.
- Adversarial red-team as a first-class stage catches strategy and security holes before they ship, not after.
- The real unlock isn't any one agent — it's the memory: lessons from one project compound into every brief that follows.
