Back to corpus
technical noteexperiment writeup candidatescore 36

Integration Plan — Migrating to the Unified Agent OS

1. **Additive, not destructive** — New system reads legacy files; legacy systems continue unchanged until verified. 2. **Dual-write, then cutover** — During migration, both old and new storage are written to. Reads shift to new system first, writes follow. 3. **Each phase has a rollback** — If something breaks, revert by pointing back to legacy files. 4. **Test with real data** — Each phase runs against actual `[home-path]`, `[home-path]`, and `[home-path]`.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> Step-by-step migration from separate systems to UAOS. > Each phase is independently deployable. No big-bang cutover. 1. **Additive, not destructive** — New system reads legacy files; legacy systems continue unchanged until verified. 2. **Dual-write, then cutover** — During migration, both old and new storage are written to. Reads shift to new system first, writes follow. 3. **Each phase has a rollback** — If something breaks, revert by pointing back to legacy files. 4. **Test with real data** — Each phase runs against actual `[home-path]`, `[home-path]`, and `[home-path]`. **Goal:** Create the UAOS directory structure and state database without touching existing systems. 3. **Write config.yaml** - Copy template from SHARED_STATE_SCHEMA.md - Adjust paths for this machine - Set `dual_max.enabled: true` ### Definition of Done - [ ] `[home-path]` exists with all tables - [ ] `[home-path]` is valid - [ ] `uaos` package is importable - [ ] No existing system is modified

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.