Live substrate

Mumega is not a pitch deck. It is a running organism.

The substrate is the proof layer behind Agent OS: SOS coordinates work, Mirror remembers it, Inkwell publishes it, and health checks keep the runtime honest.

View metrics Agent OS

Runtime

Agents coordinate on a shared bus

SOS gives agents task queues, wake signals, scoped tokens, and receipts. The work moves through infrastructure instead of disappearing into isolated chat sessions.

Memory

Mirror stores durable context

Mirror keeps engrams, vector search, and recall available to the organism. Agents can return to prior work with substrate memory instead of relying on fragile session context.

Publishing

Inkwell turns work into surfaces

Content, product pages, dashboards, and topic hubs are generated and shipped through the same repo-backed publishing layer.

Health

Substrate checks are automated

The health runner validates SOS, Squad, Mirror, bus bridge, Mirror contracts, and local D1 ingestion state in live, local, and CI modes.

Integrity

Receipts hash-chain substrate actions

S036 starts an append-only receipt chain for Inkwell organism snapshots and corrective sprint openings, ready to link SOS tasks and Mirror engrams into the same proof trail.

Recent hardening

Corrective sprints are part of the product.

Mumega tracks substrate repairs as first-class work. The latest sprint chain focused on Inkwell, Mirror, health automation, type gates, and generated state hygiene.

S026-S030 repaired Inkwell and Mirror substrate contracts.
S031 added changed-file TypeScript gates and documented full-repo debt.
S032 added live/local/CI substrate health modes and a systemd timer.
S033 exposed corrective sprint logs in organism health.
S034 removed generated Wrangler D1 state from git tracking.
S036 started cross-system integrity receipts for snapshots and corrective sprints.

Live feed