Skip to content
Annihilation

Annihilation

The LiveView control room for BEAM-native psychonaut orchestration. Quanta move through bursts and waves, psychonauts fan out in parallel, and the tether stays in the loop.
Read the Introduction Read the Plan GitHub

Operator Console

Psychonauts, quanta, and a tethered control room.

Annihilation is being rearchitected into a Postgres-backed, LiveView-driven psychonaut system: durable state in the database, hot runtime state in ETS, and human control made explicit through tether, reaching, drift, and grounding flows.

RuntimePostgres + ETS

Durable system state lives in Ecto-backed tables while hot process state stays fast in memory.

EventsPhoenix.PubSub

Agent lifecycle, burst state, tether interactions, and quantum updates stream through explicit topics.

ControlLiveView + desktop shell

The primary operator surface is a LiveView app wrapped in a native window when you want it local.

LearningAGENTS + playbooks

Plain-English conventions live in AGENTS.md; learned rules, skills, and confidence scores live in Postgres.

Live SignalTether online
repo.bootmigrations applied, default pipeline seeded, session row ready
quanta.collect12 open quanta matched to the active pipeline for the next burst
agent.spawnorchestrator, coder, tester, and docs psychonauts online
liveview.syncdashboard streaming burst state, agent deltas, and tether queue updates
reaching.openhuman input requested before a grounding action mutates code or pipeline state
reflection.rundiary entries, playbook deltas, and skill updates proposed from session evidence

Capabilities

Built for a persistent operator loop.

The new architecture shifts the center of gravity away from a terminal-first prototype and toward a durable system with a browser-grade control surface and a native desktop wrapper.

Quanta as the Core Unit

Work is modeled as quanta with parents, sessions, labels, priorities, and pipelines. The data model becomes explicit instead of hiding in issue tracker side effects.

Phoenix Control Room

Dashboard, tether, grounding, focus, and quanta views move into LiveView so operator state is live, inspectable, and easier to extend than a terminal grid.

Hot State, Durable Spine

ETS owns the fast-moving runtime tables. Postgres keeps the source of truth for sessions, events, pipelines, rules, and assumptions.

Grounded Self-Extension

Psychonauts can still propose new tools, skills, and pipeline changes, but the tether remains the final boundary before those mutations land.

Runtime Loop

Collect. Fan out. Ground. Learn.

The operator loop stays short on ceremony and heavy on observability. Every stage is visible, interruptible, and tied back to concrete application state.

  1. 01

    Collect quanta

    Open quanta are matched to their pipelines, grouped into a burst, and advanced into the next wave.

  2. 02

    Parallel execution

    Psychonauts stream, recurse, and execute tools concurrently while OTP supervision keeps failures contained.

  3. 03

    Reach and ground

    Questions surface in the tether queue, drift is reviewed explicitly, and mutations are grounded before they land.

  4. 04

    Carry memory forward

    Reflection turns session events into diary entries, playbook updates, and skill scoring that shape the next burst.

Entry Points

Start where you need signal.

The docs are shifting with the rearchitecture. Start with the target model, then drill into the supervision tree, data model, and design rationale.

Introduction Vocabulary, design principles, and the high-level shape of the rearchitected system.
Rearchitecture Plan Full target stack, schema, supervision tree, UI layout, and migration plan.
Architecture Trace the supervision tree, event flow, persistence layer, and runtime boundaries.
Design Decisions Review the tradeoffs behind the system direction and the constraints shaping the runtime.