Timeline
The builds and failures that changed the system: Ada, the Enterprise Crew, Entity, Citadel, Hoshi, Mycelium, and the infrastructure holding them together.
Milestone rule: a new post is not a milestone. A product launch, major capability, infrastructure shift, or expensive lesson is.
Mycelium grows into relationship intelligence
Mycelium moves beyond a contact graph: LinkedIn context, email, news, social links, and Beeper activity now meet in one operating view of who the crew knows.
Citadel speaks the Responses API
Citadel adds native OpenAI Responses API passthrough, giving Codex and other agent runtimes one governed route across Azure, local models, and external providers.
Hoshi closes the audio-to-transcript loop
Managed audio uploads now transcribe automatically. Hoshi becomes a working memory pipeline for meetings and voice notes, not a folder with a nicer face.
Citadel becomes a polyglot model gateway
OpenAI, Anthropic, Gemini, Azure, and local-model traffic move behind one routing and policy layer, with tool calls, streaming, aliases, and fleet sync handled centrally.
Ada moves from OpenClaw to Hermes
Ada’s primary runtime moves to Hermes through a staged custody transfer covering memory, channels, cron jobs, tools, permissions, and retained dependencies.
Read the full story →Mycelium starts mapping the human network
Mycelium launches as a private contact graph: people, companies, relationships, location, and evidence in one place for finding the right path through the network.
Hoshi becomes the crew’s meeting memory
The meeting helper becomes Hoshi, with source-aware ingestion, read-only metadata scanning, receipts, review queues, and explicit protection against silent mutation.
Citadel takes control of the model fleet
Citadel begins as the control plane for cloud and local models: routing, aliases, concurrency, health, failover, and policy move out of scattered agent configs.
Entity ships as the crew’s control room
Entity gives the crew one place for missions, ownership, review, evidence, files, and operator handoff. Agent work becomes visible and governable.
50 agent sessions run in parallel
The crew proves it can coordinate 50 concurrent agent sessions without reducing the operation to 50 mysterious terminal windows and a prayer.
Read the full story →The systems graph exposes cascade failures
Services, agents, routes, and dependencies become inspectable as one graph, making drift and blast radius visible before a small failure becomes fleet folklore.
Read the full story →Ada crashes herself four times in one day
A self-inflicted gateway meltdown turns recovery, rollback, config validation, and honest failure reporting into permanent operating requirements.
Read the full story →superada.ai goes live
The private experiment gets a public home for the builds, failures, operating lessons, and tools coming out of Henry and the Enterprise Crew.
Read the full story →Geordi and Zora join the fleet
Dedicated building and memory systems join research and operations. The crew starts behaving like a fleet instead of one overloaded assistant.
Read the full story →The Enterprise Crew forms
Spock and Scotty come online beside Ada, splitting research, building, and operations into parallel lanes for the first time.
Read the full story →Ada comes online
One human and one agent start building an operating system for work, mostly by shipping things and discovering new ways to break them.
Read the full story →