Back to corpus
architecturetechnical paper candidatescore 66

Unified Agent OS — Architecture Document

The Unified Agent OS (UAOS) merges three autonomous systems — **Pulse** (development), **Heartbeat** (monitoring), and **Dream Weaver / Noosphere** (incubation) — into a single coherent platform. Today these systems share the filesystem implicitly and bridge state through ad-hoc scripts (`noosphere_bridge.py`, `cadence_bridge.py`). The UAOS replaces those stitches with a unified state bus, a single lifecycle model, and formalized handoff protocols.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Dream Origin:** dream_202601291857_a242e7 > **Version:** 1.0 — Design Phase > **Date:** 2025-02-09 The Unified Agent OS (UAOS) merges three autonomous systems — **Pulse** (development), **Heartbeat** (monitoring), and **Dream Weaver / Noosphere** (incubation) — into a single coherent platform. Today these systems share the filesystem implicitly and bridge state through ad-hoc scripts (`noosphere_bridge.py`, `cadence_bridge.py`). The UAOS replaces those stitches with a unified state bus, a single lifecycle model, and formalized handoff protocols. 1. **Preserve what works** — Every current Pulse session, Dream Weaver incubation, and Heartbeat check must continue to function unchanged. Migration is additive, not reductive. 2. **Shared state, separate concerns** — Each subsystem keeps its domain logic but reads/writes to a common state layer. 3. **Events over polling** — Move from file-watching and cron loops to an event bus that subsystems publish to and subscribe from. 4. **Extensibility for Cadence** — The multi-agent coordination system (higher-level / lower-level agents, INBOX/OUTBOX protocols) becomes a first-class orchestration layer. | Component | Role | |-----------|------| | `dual_runner.py` | Rate-aware session executor across two Claude Max accounts | | `enriched_spawn.py` | Context-enriched prompt builder for sub-agent iterations | | `server.ts` (MCP) | MCP server exposing `pulse_start`, `pulse_status`, `pulse_iterate`, etc. | | `sessions/*.json` | Per-session state files (id, project, iteration count, status, goal) | **State Model:** JSON files in `[home-path]`, one per session. Status enum: `running | paused | complete | blocked | failed | aborted`.

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.