The ecosystem
GAIA is a suite of small engines, not a framework, not a control plane. Each project owns one mechanism, speaks a wire protocol, and composes with the rest. The layers below are the architecture: packaging → engines → orchestration → surfaces, with planes underneath serving the whole stack.
The layers
Packaging
Everything installs, updates, and ships through tamias packs. Pluggable adapters fetch content; the store caches it; drivers dispense it to whoever asks.
The entrypoint: fetch, store, cache, dispense
Package and content manager: every 9aia tool installs and updates through tamias packs.
Config loading & templated content packs
Config expertise: generic config ports plus templated content packs distributed via tamias.
Planes
Cross-cutting services that govern the stack itself: releases and the CI gate ride the same pack machinery as everything else.
Engines
The machines. Each a small engine owning exactly one mechanism: memory, secrets, coordination, sessions, scheduling, verification. They compose over wires, not plugins.
Distributed substrate: entities across machines
Distributed substrate: a generic entity plane with namespaced ops, snapshots, and locks.
The ledger: durable work memory
Records engine: a myco CLI owns every write to a repo's markdown work ledger.
Repo memory: verified code maps
Code-map engine: crawls repos into verified per-module cards agents query instead of re-exploring.
The critic: claims verified against code
Verification engine: extracts claims from docs and cards, verifies them against the code, repairs the fixable.
The WAL: coordination in milliseconds
Ephemeral coordination: claims, ops, and topics over the git object store.
Secrets broker: sealed, not spilled
Secrets broker: code carries cuora:// references; values materialize as env vars at run time, audited.
Session lifecycle: agents, agnostically
Session lifecycle engine: one canonical IR and pluggable store drivers across coding agents.
Git & workspace expertise
Git and workspace expertise: lasius.toml clones and syncs every repo of a GitHub org.
Calendars as code: scheduled work
Scheduled-work engine: declare calendars in YAML, plan and apply them against live providers.
Orchestration
Campaigns that drive work across machines: declarative events, nodes, and drivers, with a session plane on every node.
Campaigns: event-driven orchestration
Orchestration engine: declarative campaigns of events, nodes, and drivers across your machines.
Surfaces
What humans and agents actually see. Products ship tamias drivers; surfaces render their ViewNode IR across CLI, TUI, and web.
The screen: renders every view
Visualization host: renders ViewNode IR trees emitted by tamias drivers across CLI, TUI, and web.
How a change ships
The suite manages its own development. This is the loop, end to end:
tamias: installs and dispenses the packs that carry everything elsemyco + kuda: track the work and remember the codesturn: coordinates agents in milliseconds over the git object storeperegrin + sepia: run campaigns and manage agent sessions across machinespavo: renders every view the drivers emitbupha: gates every push through CItarsi: cuts the release
Every project has its own docs site (tutorial, how-tos, reference, and explanation) linked from each card above. Start with tamias, the entrypoint.