How I Built a 15-Wing Personal AI Operating System in 6 Months

The Architecture Decisions That Actually Matter

Model Routing: Sonnet + Haiku

Not every wing needs the same model. The CEO wing makes high-stakes decisions: it gets Claude Sonnet. The Sanyu wing sends a wellness check-in notification, that gets Haiku.

This single decision cut my AI costs by 40% without reducing quality anywhere it mattered.

function getModelForWing(wing: WingId): string {
  const heavyWings = ['ceo', 'corpus', 'engineering', 'consulting'];
  return heavyWings.includes(wing)
    ? 'claude-sonnet-4-6'
    : 'claude-haiku-4-5-20251001';
}

Prompt Caching on Every System Block

Every wing has a system prompt. The system prompt is static: it describes the wing's role, my context, the rules of engagement. In Claude API, any static block ≥4096 tokens can be cached. I made sure every system prompt hit that threshold.

Result: cache read tokens cost 10% of standard tokens. On 15 wings used daily, this compounds fast.

Redis Signal Protocol: Wings Talk to Each Other

This is the architectural decision I'm most proud of. Wings don't just respond to me: they signal each other.

When the Cycle wing logs a new phase, it writes a signal to Upstash Redis:

cycle:phase_changed → {phase: 'follicular', energy: 'rising'}

The Marketing wing reads this signal when planning content. The Body wing adjusts workout recommendations. The CEO wing knows to schedule high-stakes calls in the high-energy follicular phase.

This is not just an AI chatbot. This is an orchestrated intelligence system.

The Corpus: 1,194 Knowledge Chunks via Upstash Vector

The Corpus wing ingests everything: my book, my project documentation, my journal entries, my research notes. 1,194 chunks, vectorized and stored in Upstash Vector.

When I ask any wing a question, the Corpus retrieval runs first. The AI answers with the context of everything I've ever thought or documented. It's like having a second brain that never forgets.

Inngest for Async Everything

Some things can't happen synchronously. The daily brief compiles insights from 8 wings. The production log update pings finance. The crisis check-in waits for a response before routing.

Inngest handles all of this. Every long-running task is an Inngest function. No timeouts, no blocking, full visibility into every step.