H·AI·K·U Runtime Architecture

Every actor, every FSM tick, every state write — the software studio's full intent lifecycle on one page. Five runtime players at the top, hooks down the left, the intent flow in the middle, the knowledge pool on the right. Inside an intent: pre-elab → six stages (each with its own phase machine: pending → elaborate → execute → review → gate) → final PR/MR gate → delivery → operations. Hover anything for a tooltip · click for full detail.

Actors

🧑 User
prompts, approves, reviews
⇆ conversation
🤖 Agent (Claude Code)
stateless between ticks; calls haiku_run_next
↔ intercepts
🛡 Hooks
block bad moves · inject state
→ tool calls
🧠 Orchestrator (MCP)
reads disk · validates · returns action
→ openReviewAndWait
🌐 Review web UI
approve · changes · external · open PR

Pre-intent

user ↔ agent clarification → intent.md

Intent creation /haiku:start expand ↗

🧑 you
—
🤖 agent
—
User and agent exchange Q&A until the agent has enough to draft intent.md. example: — · studio: —
haiku_run_next → opens the gate

Intent review · gate · ask

  • approve → returns start_stage
  • request changes → loops back to creation
The user's click is the outcome of the haiku_run_next call. On approve: state.json created, phase: elaborate set on Inception, intent_reviewed: false still (the formal intent_review gate fires inside Inception's elaborate→execute).

Intent

.haiku/intents/{slug}/intent.md · studio: software
approve → delivery

Post-intent

final gate → delivery · operations