# CLAUDE2 — coordination addendum for Quik's existing main developer

Continue the `QUIK-CROWN-LANDMARK-README(1).md` session brief already sent by Quik. This addendum connects your existing execution work with the other four seats. Preserve your current session and local branch/worktree; no restart, new branch or new broad file ownership is required.

Your execution order remains orientation fixture → connected test sample → isolated Crown Landmark review/modeling. Shared-world placement and district construction remain held under the existing brief. Only one agent controls the editor at a time.

Keep the sealed TEST-ONLY package unchanged. Your feedback claim remains the existing suggested destination, `docs/crown-key-production/R01/claude-pilot/quik-feedback/R01/`, outside the sealed package. Register any additional exact support/test files with OA1 before editing; this addendum does not claim `docs/crown-key-production/R02/reviews/`. OA1 owns that directory and delegates independent geometry/route/package checks to read-only reviewers.

Follow the existing brief's acquisition and manifest instructions. It correctly distinguishes the browser-assembled Coordination ZIP from direct C01/C02/fit ZIPs and the TEST-ONLY folder. Do not invent a download URL or treat missing canonical R01/MANIFEST.json as proof that the assembled package is broken.

Coordination tasks, in support of your existing work:

1. Report the actual candidate/source revision, tool and engine versions, current implementation stage, practical blockers and next useful handoff checkpoint. Record actual observations; do not invent an ETA or engine success.
2. Use merged Crown PR #45 C02/81-room evidence at `a7220db` and the current issue list. Preserve issued INT R02 work. Keep document findings separate from observed import, collision, scale, material and traversal results.
3. Send implementation feedback to OA1 and CLAUDE1 promptly so reusable tooling fixes help the next buildings. Your current work takes priority over unsolicited broad package audits.
4. When an incoming Split/Terrace package reaches you and time permits, report practical setup, import or usability findings. This feedback helps the team, but your availability is not a required build-ready release gate.

OA1's independent reviewer checks the next building package. You are not assigned to independently approve your own Crown work, and you do not need to complete a separate Split/Terrace review before the other seats can release a sound package. Actual engine-verified claims still require the relevant project evidence.

Use Claude subagents for bounded supporting research or separate tests that do not compete for editor control. Continue building with Quik; let the other lanes prepare and independently review the next two packages.
