Back to corpus
architecturetechnical paper candidatescore 56

SOOP-2 Architecture

This document is the authoritative architecture reference for SOOP-2. It describes what exists today (SEA at ~40% shipped), what SOOP-2 adds, and exactly how the pieces connect. Every section maps to at least one acceptance criterion from the launch checkpoint.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# SOOP-2 Architecture > Skills Operating System Phase 2 > Status: APPROVED DESIGN | Date: 2026-05-12 | Version: 1.0 This document is the authoritative architecture reference for SOOP-2. It describes what exists today (SEA at ~40% shipped), what SOOP-2 adds, and exactly how the pieces connect. Every section maps to at least one acceptance criterion from the launch checkpoint. The Rail document at `Desktop/crucible-output/soop-2/03-rail/EXECUTION-PLAN.md` is the execution companion. This document explains _why_. The Rail explains _when_ and _who_. 1. System layers (top to bottom) 2. Type system as cross-cutting concern 3. The 6 categories with examples 4. Meta-review contrarian as a first-class SEA entity 5. Silent return type 6. Closed feedback loop topology 7. Mesh assignment 8. EW invariant alignment 9. Anti-patterns to avoid 10. Architecture decisions log The full stack from user intent to feedback reward has 10 layers. Each layer is described with its current state, what SOOP-2 changes, and its integration surface.

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.