LostSouls.world

Legend × Quik × Chris · 2026-10-17 · R01

Production foundations.
Technical evidence.

The retained R01 pilot, contracts and reconciled status. Start with R02 for current five-seat assignments and expanded building interiors.

On this page

Crown Key R01 · technical support and pilot evidence

R01 · Updated 2026-10-17 · America/New_York · technical_support_superseded_by_R02_direction

Retain the R01 pilot, source evidence and tooling contracts as support for the current five-seat plan. Develop all 25 building variants and six structures with the expanded interior scope and parallel ownership defined in R02.

Legend reports Quik is about to start Crown Landmark. Authoring, proposed modeling and isolated staging can proceed within that scope while other building packages advance in parallel. Final geography, shared frame, world placement, shell acceptance and actual engine acceptance remain independent decisions; this packet does not invent their approval.

Current production direction

Current five-seat plan · R02 · R02 AI start here

The current five-seat production plan is at https://thelostsouls.world/CrownKey/production/plan/ and docs/crown-key-production/R02/AI_START_HERE.md. Three OpenAI seats and two Claude seats work in parallel: Quik starts Crown Landmark authoring/staging while the team completes Split Complex and Terrace Tower packages. Every enclosed building receives a lobby plus one or two useful interior spaces, with Atlas scene requirements taking priority. Open structures receive appropriate arrival and access spaces. R01 remains technical and historical support.

Start here

AI and new-developer brief · Plan JSON · Claude assignment · Quik feedback

Retained pilot evidence

Open the R01 execution record: dated agent findings, reviewed sample inputs R02 and first building studies. PR status has been reconciled; R02 controls current assignments and expanded interiors. This is not live telemetry or engine acceptance.

Current evidence

Baseline main: 4ce28d89b6fb1922f0b8427937b986961504307d. Recheck HEAD and open PRs before work; this is a dated plan, not a live status feed.

Read in this order

People and responsibilities

PersonRoleResponsibility
Legend / AsaCreative ownerSelect creative direction, proposed scale and geography; approve accepted releases and main publication.
Quik / QuikyCodeImplementation and engine feedbackStart Crown Landmark authoring and isolated staging; report actual software, scale, import and traversal evidence. Final world placement and engine acceptance remain separate.
Chris MillerJoining developerUse /millertime/ as a focused project desk. Chris has offered to explore Sophia; start with a proposed isolated import/motion study and coordinate the selected source with Legend/Quik. Character capture and music/UI remain research interests.
CodexProduction coordination and asset authoringOwn plan/ledger entries, proposed design values, asset briefs, visual packages and integration; review Claude's tooling.
ClaudeTooling owner and independent asset reviewerOwn schema, validators, generators, migration proposals and schematic decision sheets; review Codex packages.

Ownership and branch claims

AreaOwnerBoundary
Plan and future asset ledger entriesCodexOperational entries only; no duplicate authoritative dimensions.
Plan publishing helperCodexPublish this plan and its download mirrors; no geometry/schema ownership.
Dimension/ledger schemas, validators and drawing/blockout generatorsClaudeClaude proposes exact new paths at Checkpoint A before editing. Schema PR includes migration impact and any shared CI changes.
Per-asset dimension values and sample fixture inputsCodex / assigned asset package ownerOwner claims exact files before edits. Codex proposes initial sample and Split Complex values; Legend selects design scale; Quik measures implementation.
Existing issued assets and Unreal worldExisting owners / QuikRead sources; new candidates stay isolated. No overwrite or world construction release.

Checkpoints and build order

CheckpointOwner / stateOutput and gate
A · Baseline and schema proposalClaude; Codex reviews / completedBaseline SHA, active PR inventory, exact branch/path claims, schema changes and migration impact. PR #51 (merged 7a81eb8) published schema/path/migration evidence after Codex review. Gate: One owner per edited file; extend existing contracts without silently modifying released R05 sources.
B · Dated decision sheetsClaude; Legend selects / plannedSchematic bridge, clearance-datum/route and shoreline options, affected assets, sources and a separately marked recommendation. Gate: Choices unblock affected site work only after Legend records a selection. Rendered concept art comes from the visual team.
C · Synthetic fixture pipelineClaude; Codex reviews / completedSVG drawings and Blender blockout from the same test contract; known-size asymmetric orientation fixture. PR #51 (merged 7a81eb8) supplies reviewed fixture evidence and the TEST-ONLY Quik import package; Quik’s Unreal results are pending and this is not engine acceptance. Gate: Check value changes, openings/markers/reservations, unknowns, revision stamps and test-only enforcement. Record actual tool versions.
D · Isolated connected sample contractsCodex values; Claude tools / completedR02 proposed test-only sample is mapped, reviewed and included beside the independent orientation fixture in PR #51’s merged TEST-ONLY Quik package. Actual Unreal results remain pending. Gate: Codex supplies explicit proposed test-only dimensions. Trace any entrance dependency to local geometry; L25/L26 findings do not prove or disprove entrance fit. No candidate shell is auto-accepted.
E · Quik's practical import and traversal testQuik; Codex and Claude support / pending_external_testRecorded versions, import settings, dimensions, orientation, interface/traversal evidence and short feedback form. Gate: Use feedback to revise the package standard before scaling. Final district placement, shell and engine acceptance remain separate.
F · Split ComplexCodex / asset package owner; Claude reviews / in_progressReconcile newer H1 direction with the older Candidate B skeleton, then author lobby plus selected interior spaces, proposed dimensions, derived drawings/model, consistent views and a coherent build packet. Gate: Essential geometry and interfaces must be coherent for a modeling handoff. Carry Quik feedback into the package; distinguish proposed modeling readiness from shell, placement and engine acceptance.
G · Terrace Tower, then reviewed familiesCodex / asset package owners; Claude reviews / in_progressDevelop Terrace Tower alongside Split Complex: exterior, lobby, representative dwelling and shared terrace lounge; then reuse reviewed family components. Gate: Own exact files independently. Review core/setback/room fit and incorporate importer feedback before claiming an engine-verified package.

R01 role reference

Follow R02: Crown Landmark implementation support plus Split Complex and Terrace Tower package development run concurrently. Aim to keep the next complete package ready for Quik and another in integration. Bounded subagents have explicit inputs, outputs and one owner per authoritative file; the plan is not live agent telemetry.

The table retains the original pilot role suggestions. Use the R02 plan for the current five seats and their exact assignments.

Pilot roleOriginal model / effortBounded task
Coordinator and ledger authorCodex lead / Task-dependentSequence the current asset, reconcile sources and integrate the package.
Asset package ownerGPT-6.1 Sol / HighPropose dimensions with sources/status, author scope and reconcile drawings to visual requirements.
Inventory and consistency supportGPT-6 Luna / Low / MediumIndex sources, flag missing fields, verify names/links and assemble checklists.
Visual developmentGPT-6.1 Sol + image-generation tool / High for planningUse model/drawing references for images; image generation is separate from language-model reasoning.
Difficult interface reviewGPT-6 Astra / High; Max for a bounded difficult reviewReview complex geometry and unresolved dependencies when needed.
Tooling and cross-model reviewClaude environment / Chosen for the actual taskBuild deterministic tools and independently critique asset packages.

Readiness means evidence

MilestoneMeaning
PreparationExisting sources, components and decisions organized; unresolved values remain visible.
Ready for shell developmentSelected exterior direction, proposed dimension contract, plans and interfaces are coherent enough for modeling; not shell acceptance.
Ready for interior developmentReviewed shell supports selected rooms, openings and circulation; proposed assignments remain labelled.
Engine verifiedActual project evidence records import, scale, collision, traversal, materials and agreed runtime tests; document completeness alone does not qualify.

What a complete package contains

Rules that prevent drift

Asset sequence

All 31 registered assets

Names and IDs are indexed from the current build register. Readiness still comes from each asset's controlling evidence.

Global IDAssetKind / register priority
PI-BLD-0001-V01Crown Landmarkbuilding / P0
PI-BLD-0002-V01Split Complexbuilding / P2
PI-BLD-0003-V01Terrace Towerbuilding / P2
PI-BLD-0004-V01Twist Tallbuilding / P2
PI-BLD-0004-V02Twist Compactbuilding / P2
PI-BLD-0005-V01Garden Canyonbuilding / P2
PI-BLD-0005-V02Terraced Gardenbuilding / P2
PI-BLD-0006-V01Frame Tallbuilding / P2
PI-BLD-0006-V02Frame Midbuilding / P2
PI-BLD-0006-V03Frame Compactbuilding / P2
PI-BLD-0007-V01Courtyard Officesbuilding / P1
PI-BLD-0007-V02Glass Office Blockbuilding / P1
PI-BLD-0008-V01Stepped Residencesbuilding / P1
PI-BLD-0008-V02Compact Residencesbuilding / P1
PI-BLD-0009-V01Crescent Hotelbuilding / P1
PI-BLD-0009-V02Compact Terrace Blockbuilding / P1
PI-BLD-0010-V01Long Arcadebuilding / P1
PI-BLD-0010-V02Curved Arcadebuilding / P1
PI-BLD-0010-V03Corner Arcadebuilding / P1
PI-BLD-0011-V01Waterfront Pavilionbuilding / P1
PI-BLD-0011-V02Inner Pavilionbuilding / P1
PI-BLD-0012-V01West Arrival Canopybuilding / P1
PI-BLD-0012-V02East Arrival Canopybuilding / P1
PI-BLD-0013-V01Straight Tallbuilding / P2
PI-BLD-0013-V02Straight Slimbuilding / P2
PI-STR-0001-V01Bridge Spanstructure / P1
PI-STR-0002-V01Bridge Landingstructure / P1
PI-STR-0003-V01Seawall and Promenadestructure / P1
PI-STR-0004-V01Finger Dockstructure / P1
PI-STR-0005-V01Dock Connectionstructure / P1
PI-STR-0006-V01Arcade Bay Modulestructure / P1

Today and next actions

Chris and other joining developers

Quik feedback and evidence

Regenerate and maintain

Edit docs/crown-key-production/R01/PLAN.json, then run python tools/build_crown_team_plan.py and python tools/build_crown_team_plan.py --check. README, onboarding, Claude brief, feedback form and website copies are generated. Commit the source and generated outputs together. The R02 publisher runs after this support page. Geometry/schema/issue validation lives in the merged tools/contracts/ implementation, separate from this publisher.