Back to corpus
research notebacklog referencescore 18

LIVING IMPLEMENTATION CHECKLIST — Unified Agent OS

Workspace document requiring curation.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

## Phase 0: Governance & Foundation - [x] **0.1** Project Charter — `PROJECT_CHARTER.md` | Owner: Agent | Confidence: High - [x] **0.2** System Glossary — `GLOSSARY.md` | Owner: Agent | Confidence: High - [x] **0.3** Invariants & Assumptions — `INVARIANTS.md` | Owner: Agent | Confidence: High - [x] **0.4** Implementation Guide — `IMPLEMENTATION_GUIDE.md` | Owner: Agent | Confidence: High - [x] **0.5** Living Checklist — This file | Owner: Agent | Confidence: High - [ ] **0.6** Architecture Document — `ARCHITECTURE.md` | Owner: Agent | Confidence: High - Input: Charter + Glossary + existing Pulse v3/Heartbeat/Dream Weaver code - Output: System architecture diagram, data flow, component contracts - Validation: All glossary terms appear; all invariants addressed - [ ] **0.7** Database Schema Design — `infra/supabase/` | Owner: Agent | Confidence: Medium - Input: Architecture doc + Glossary - Output: SQL migrations with RLS policies - Validation: Multi-tenant queries isolated; all core types have tables - [ ] **0.8** API Contract (OpenAPI) — `packages/api/openapi.yaml` | Owner: Agent | Confidence: Medium - Input: Architecture doc + Glossary - Output: OpenAPI 3.1 spec - Validation: All user-facing features have endpoints; types match @agentos/core ## Phase 1: Core Package & Types - [ ] **1.1** Initialize monorepo — Turborepo + workspace config - Output: `turbo.json`, root `package.json`, `tsconfig.base.json` - Validation: `turbo build` runs clean - [ ] **1.2** @agentos/core types — Tenant, Session, Agent, Skill, Event types - Output: `packages/core/src/types/` - Validation: Compiles strict; all glossary terms have type definitions - [ ] **1.3** Event system — Typed event definitions + bus interface - Output: `packages/core/src/events/` - Validation: Publish/subscribe works; events are serializable - [ ] **1.4** Constants & enums — Status codes, limits, defaults - Output: `packages/core/src/constants/` - Validation: No magic strings in other packages ## Phase 2: Engine (Pulse Port) - [ ] **2.1** Session manager — Create, run, checkpoint, resume, complete - Input: Existing Pulse v3 session logic - Output: `packages/engine/src/session/` - Validation: Session state machine matches spec; multi-tenant safe - [ ] **2.2** Model router — Multi-provider model routing with fallback - Output: `packages/engine/src/model/` - Validation: Supports Anthropic, OpenAI, Google; fails gracefully - [ ] **2.3** Chain executor — DAG-based multi-session workflows - Output: `packages/engine/src/chain/` - Validation: Parallel branches execute; conditional logic works - [ ] **2.4** Quality gates — Pluggable validation system - Output: `packages/engine/src/gates/` - Validation: Build, lint, test gates work; custom gates register - [ ] **2.5** Rollback manager — Git-based checkpoint

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

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.