Back to corpus
technical noteexperiment writeup candidatescore 24

METAMORPHOSIS: Unified Agent OS — Summary Report

| System | Current State | UAOS Role | |---|---|---| | **Pulse v3** | `dual_runner.py` + MCP server + session JSONs | Development engine — executes autonomous dev sessions | | **Heartbeat v2** | `HEARTBEAT.md` + state JSON + main agent polling | Monitoring layer — periodic checks, alerts, proactive work | | **Dream Weaver / Noosphere** | `incubator.py` + `noosphere.py` + daemon + MCP + GitHub Actions engine | Incubation engine — idea exploration, evolution, emergence | | **Cadence** | `cadence_bridge.py` + governan

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Dream ID:** dream_202601291857_a242e7 > **Status:** ✅ Design Complete > **Date:** 2025-02-09 A **Unified Agent OS (UAOS)** that merges four currently separate systems into one cohesive platform: | System | Current State | UAOS Role | |---|---|---| | **Pulse v3** | `dual_runner.py` + MCP server + session JSONs | Development engine — executes autonomous dev sessions | | **Heartbeat v2** | `HEARTBEAT.md` + state JSON + main agent polling | Monitoring layer — periodic checks, alerts, proactive work | | **Dream Weaver / Noosphere** | `incubator.py` + `noosphere.py` + daemon + MCP + GitHub Actions engine | Incubation engine — idea exploration, evolution, emergence | | **Cadence** | `cadence_bridge.py` + governance markdown + Supabase sync | Orchestration layer — multi-agent coordination, priority routing | ### 1. SQLite as the Unified State Store Instead of scattered JSON files (`sessions/*.json`, `dreams.json`, `heartbeat-state.json`) and ad-hoc bridges (`noosphere_bridge.py`), a single SQLite database (`[home-path]`) holds all state. JSON blobs are used for subsystem-specific fields to maintain flexibility. ### 2. Event Bus Over File Watching Systems currently discover each other's state by reading files. UAOS introduces an event bus with defined topics (`pulse.iteration.completed`, `dream.emerged`, `heartbeat.alert`, etc.). Cross-system reactions are registered as event listeners, not embedded in each system's code.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

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.