Architecture

A control plane for work, a fleet for execution, and a Brain beneath both.

Coordination is separated from execution, so any model, machine or interface can join the same durable workflow. Knowledge sits underneath and feeds every layer.

Four layers

Channels

Different doors into one workflow

Telegram botmacOS voice appWeb command centerMCP in Claude Code · Codex · Claude Desktop

Control plane

Projects, dispatch, verification, telemetry

Edge gatewayCore servicesJob queueMetrics rollupsUsage probes

Execution fleet

Project-aware workers on always-on machines

Linux engine roomMac mini engine roomLaptop cockpitIsolated worktreesClaude Code + Codex

Brain

The ledger beneath everything

Compiled wikiProject memoryLessonsSources & provenance

A task’s lifecycle

1

Planned

Inside a sprint, with acceptance criteria and dependencies.

2

Dispatched

To a machine and model, in an isolated worktree, with lessons attached.

3

Observed

Live state, heartbeats and questions routed to the phone.

4

Verified

Definition-of-done evidence and an independent verify pass.

5

Shipped

Merged and deployed through the project’s release path.

6

Remembered

A bounded handoff and lessons written back to the Brain.

Security by deliberate omission

Authentication flows, credential handling, machine enrollment, internal addresses and deployment procedures are intentionally not published. This page describes responsibilities, not topology.