# OA1 — integration, atlas and publication

You are the sole integrator for Crown Key R02. Read `../README.md` and current repository instructions. Baseline main: `4ce28d89b6fb1922f0b8427937b986961504307d`; fetch current main before work. Proposed branch: `codex/ck-r02-integration`.

**Proposed claims:** `docs/crown-key-production/R02/**` except `claude-tooling/**`, explicitly including `reviews/**`; `docs/crown-key-design/R02/ATLAS_COVERAGE.*`; shared R02 scope/coverage records; and, only as integrator, the exact publishing helpers and generated `.world` outputs required to publish R02. Record each existing helper/file before editing. Other seats' per-asset sources remain theirs.

First tasks:

1. Audit the atlas and story sources for every Crown Key scene/space. Produce a traceable matrix with era, assignment status, required action/props/view, existing coverage and gaps. Preserve uncertain assignments; do not relocate outside-district scenes.
2. Replace the current recommendation for all 31 asset scopes with the new building programs, including Straight Tall/Slim. Preserve R01 as history. Give each asset page an explicit room/outdoor program, owner, state and missing evidence.
3. Activate only acknowledged path claims. Track Split and Terrace as first work in progress and ready buffer as zero until their packages meet the bar.
4. Delegate independent geometry, route and package release checks to read-only reviewers who did not author the candidate. Record their findings under `reviews/`, resolve blockers with each asset owner, then integrate reviewed deliverables, rebuild shared pages, verify links/images and publish `.world` under existing authorization. Do not edit `.com`.

Delegate bounded atlas/source extraction and independent read-only consistency review. Use Astra for a bounded difficult topology, fit or release review; ordinary integration and checks can use Sol 6.1. Quik's CLAUDE2 stays on existing fixture/sample/Crown execution and contributes incoming-package feedback as available; its participation is not a required next-building release gate. Do not spend all capacity on management documents while the two building packets wait.

Stop a release for inconsistent topology, missing build inputs, false status or broken handoff links. Escalate only a concrete creative/canon choice to Legend. Do not invent external-seat activity, Quik's ETA or engine success.

First checkpoint: source-backed atlas gaps, all 31 current program rows, acknowledged lane claims and the exact blockers to Split/Terrace readiness.
