# District Production Protocol R05 PI-PROT-DISTRICT · 19 October 2026 · CURRENT WORKFLOW — supersedes District R04 ## Identity and revision Use the existing stable family **PI-PROT-DISTRICT**, revision **R05**. This is a revision of the District Production Protocol, not a second protocol. The current pointer names R05 following Legend's 19 October publication instruction. D01-D21 identify districts; old D01 protocol aliases remain historical and no district is renumbered. R05 retains R04's twelve stages, Gates A/B/C, four build-package groups, scale reconciliation, building handoffs and shared world requirements. It makes the construction-reference authoring sequence and its completion evidence explicit. The new coverage gate applies before a district reference kit can be called complete. It does not approve any geometry or release paused construction. `CONSOLIDATED.txt` contains this guide followed by the unchanged R04 consolidated baseline. R05 controls current workflow conflicts; the previous consolidated release is retained as historical baseline. Earlier releases remain unchanged. A protocol working ZIP contains workflow documents and templates; a populated district build kit is a separate deliverable. Engine playability is neither a prerequisite to author that kit nor evidence that missing references are complete. ## The twelve-stage sequence | Step | Required work | Acceptance evidence | |---|---|---| | 01 | Intake and atlas | Current district/scene/location extract, source revisions, selected/deferred requirements | | 02 | Shared world frame | Boundary, datum, axes, origin, controls and neighbor connections | | 03 | Identity and modernization | Architecture, landscape, culture, mobility and selected era behavior | | 04 | Master and context | Controlling master, aerial/orbit coverage and player-height views; Gate A | | 05 | Authored layout | Measured roads, parcels, placements and exact spatial exports | | 06 | Topography | Ground/edge references, elevations and sections; Gate B | | 07 | Asset kit | Existing global families, developer collections, new-shell justification and reuse plan | | 08 | Building handoffs | the current Building Protocol exterior/interior scope, dimensions, shell dependencies and crosswalk | | 09 | Engine handoff | Versioned package inventory, launcher preflight and reproducible build order | | 10 | Blockout and sample | Connected measured blockout, representative playable building/street; Gate C | | 11 | Expand and verify | Kit rollout, selected interiors, connections, streaming, navigation and performance | | 12 | Release and publish | Source/evidence, atlas status, registry, manifests, current web guide and downloads | Design and rough layout can iterate together. Detailed rollout follows the accepted sample. Concept, layout, shell, engine and publication status are distinct. A template's presence does not pass a gate. ## Gate A: identity and visual blueprint Legend accepts the exact master and identity revision. Preserve the approved composition, shore, bridges, signature silhouettes, height intent and material language. Record modernization choices and any disagreement among views. An image is authoritative for its approved visual intent; metric coordinates come from a reviewed layout calibrated to that intent. Required coverage is named by role: clean overall/overhead and separate ID overlay; front/arrival context; rear/opposite context; east and west orbits; a typical player-height street; signature place/entrance; night or observable behavior when relevant; shared-border/bridge and cross-water sightlines. Select roles by the district's terrain and use. A role can be covered by an existing approved image or explicitly marked not applicable with a reason. A critical unresolved connection/view stays open. Every reference record names district, ID, camera role, file/hash, revision, era, assets/locations, authority and discrepancies. Include master/layout references in every new image request. Avoid redesigning the district independently at each camera angle. For Crown Key, the existing `/CrownKey/reference/` aerial/orbit set is part of the visual evidence, not optional decoration. ## Four build-package groups | Group | What it must explain | Crown Key historical example | |---|---|---| | A. Design references | Master, aerials/orbits, streets, entrances, identity and discrepancies | Current reference register and separate original images | | B. Authored measured layout | Editable coastline, roads, bridges, parcels/placements, units and source frame | Unreal References v01 ZIP: 7 files including layout JSON, clean/labeled plan exports and build script | | C. Exact layout views | Plan and two useful spatial views derived from the SAME layout revision/hash | Exact Layout Views v01 ZIP: 7 files; overhead and SE/SW views | | D. Terrain and edges | Topography/shore intent, sections, slopes, retaining walls, water interfaces and calibrated height data when used | Topo References v01 ZIP: 5 PNGs and README | Yes: the three named ZIPs supplied three complementary build-input groups. None replaces the design aerials, and none by itself proves a build is correct. Exact views must match the layout revision actually being built. The historical topo images are visual intent, not a calibrated elevation raster. The protocol handoff ZIP contains templates/instructions, not those three district-source ZIPs. `PACKAGE_INVENTORY.json` records role, revision, path/URL, hash, availability, authority, compatible layout hash and validator evidence. For each required group, supply valid inputs or explicitly record why it is blocked/not applicable. A recoverable local original is not a published download. Do not send a broken link as a complete handoff. ## Gate B: measured layout, terrain and scale Design units are metres; Unreal uses centimetres. Record actual axes, origin, north, sea-level datum, map transform and at least three non-collinear shared controls. Verify conversion in the real import path. Pin coastline, roads, grades, bridge endpoints/widths/clearances, parcel extents and placement transforms. Districts share one frame and the same connection records at both ends. Compare original source, current source and current engine measurements in `SCALE_RECONCILIATION.csv`. Inspect imported mesh dimensions and actor/component/baked scale. Record intended changes rather than inferring them from filenames or old captions. Crown Key's v01/v02 discrepancy remains unresolved by this release; it is not permission to shrink or enlarge the island again. Release blockout only with a named accepted layout and documented conditions. Mark incomplete terrain calibration explicitly. Never infer metres-per-pixel from a perspective aerial. Keep clean overhead, ID overlay, exact views and source JSON/model on the same revision. A later change lists effects on neighbors, bridges, parcels, buildings, interiors, skyline and travel times. ## Atlas, story and reusable architecture Read current creator decisions and the current working atlas before selecting rooms or building scope. Preserve PI-LOC IDs, scene/era status, routes, conceptual AK kit links and unresolved questions. Map requirement to placement, global asset, shell, level/room and test. Do not promote illustrative map pins or a proposed tower assignment to approved geography. Use developer collections and a limited number of shell families. Separate geometry variants from appearance presets and district placements. Author typical rooms/floors once, then identify their instances. A district does not need a unique building for every location or a complete interior in every tower. the current Building Protocol's A-E tiers control coverage and keep technical plans separate from perspective counts. ## Gate C: connected playable sample Build a representative route, exterior and selected interior at the candidate scale. Test character/camera, furnished room clearances, roads/bridges, collision, navigation, access, water, neighboring sightlines and streaming. Compare matched engine captures to the controlling images. Legend accepts visual conformance; Quik accepts the measured technical approach. Record conditions and remaining issues. The architecture direction is one project and one authoritative World Partition world with shared coordinates, externally stored actors and reusable assets. Load work regions in the editor. Staging maps are allowed for authoring/tests; independent district saves linked by ordinary level travel are not the default connected-city design. Choose the actual integration map after inspecting current content. Hundreds of users in a persistent city is a design target. World Partition is spatial streaming, not multiplayer capacity or a persistence service. Test dedicated-server networking, crowded and distributed loads, NPC budgets and durable state separately. Preserve cross-water vistas through an appropriate distant representation; do not assume all distant detailed geometry remains resident. ## Engine handoff, launcher and release Specify engine/project/map version, required plugins, source paths, build/import order, deterministic seeds if used, backups, data/asset dependencies and clean-machine reproduction. The launcher is required infrastructure and remains unverified until it can resolve versions, check files/hashes, run supported jobs, surface errors and reproduce a sample. Do not claim a template implements an importer or launcher. Release a README with gate states, package inventory, current source and screenshots/tests. Include brief, frame, connections, layout, terrain records, atlas mapping, reuse/placements, building links, shot list, approvals/change log, conformance sheet and engine/launcher QA. Update the registry, manifests and site from the current pointer. Preserve earlier revisions and source art. Only add a future district as a completed case study after it has followed these gates. The companion shared-world brief gives Quik the integration and daily workflow. Creator-authorized Black Vault sessions, developer collections and building programs are published separately on the production desk, with status intact. This exception does not authorize unrelated Studio-only material or credentials. Workflow publication is not proof of current world readiness. ## Companion pages [Production desk](/production/desk/) · [Quik's brief](/protocols/world/) · [Developer collections](/production/developers/) · [Crown Key work plan](/production/crown-key/) · [Grove image plan](/production/grove/) · [Scale register](/production/scale/) · [Black Vault](/black-vault/). ## Construction-reference sequence within stages 01–09 The recovered Crown workflow is a method: analyze the controlling compact aerial, author a coordinated layout, derive its views, then author location-tied ground and shoreline references. Its historic dimensions were deliberate proposals. Copying a Crown scale, transplanting an old tracing made from another source, or assigning the same section titles to unrelated imagery does not reproduce this method. | Step | Required authored result | Objective evidence | |---|---|---| | CR1 · source and scope | Approved source hierarchy; exact districts, boundary authority and exclusions; current appearance versus metric sources | Source ID, revision, SHA256, bytes, approval locator, role, supersession and discrepancy resolution; boundary/neighbor records | | CR2 · observations | Trace visible coastline, road margins, junctions, bridge landings, buildings and block/open-space structure; stop at occlusion | Editable vectors tied to original image coordinates; per-feature source and evidence/inference labels; coverage checklist and unresolved areas | | CR3 · coordinated authored layout | JSON/SVG/model for shore, roads and widths, connected intersections, bridges, blocks, parcels, footprints, placements and massing intent | One revision/hash; reconciled scale/frame/controls; proposed dimensions separately marked and reviewed; stable feature IDs and shared connection endpoints | | CR4 · coordinated exports | Clean and labeled overhead, plus overhead/SE/SW massing views derived from that same geometry | Layout/model hash, camera pose/projection, renderer/version, build command and output hashes; geometry parity check and visual comparison | | CR5 · ground and shoreline | Location-tied beach/shallows, seawall/promenade, building-to-water edge, bridge landing and park/beach studies as applicable; needed sections | Each image/section names layout location/feature, camera or section line, grade/datum, source versus proposal, dimensions and compatible layout hash | | CR6 · populated build kit | Actual district references, layout exports, model/massing, terrain studies, dimension decisions and build instructions | Files and working downloads, manifest/hashes, archive CRC/member checks, package-reference validation, coverage gate report and review conditions | | CR7 · separate implementation | Quik receives the accepted scoped kit; native/import return and later actual engine test | Handoff receipt, native/export checks, measured import reconciliation and matched engine captures tracked separately from reference completion | CR2 may begin in image coordinates when calibration is missing. A vector drawing in an oblique image frame is a source observation study, not a north-up measured overhead. An authored north-up proposal must name its assumptions and approval; a measured reconstruction needs a defensible registration. Do not silently turn perspective pixels into uniform metres or invent hidden streets, footprints, ground elevations or viewpoints. Deliberate design of hidden geometry is permitted in the separate authored proposal layer. Give each proposed footprint, block, road continuation and dimension its rationale, source constraints, affected connections and review state. Preserve observed evidence and compare the proposal against it; never describe an authored choice as observed or verified. Unresolved source visibility is a design decision to record, not a prohibition on progressing toward a usable proposed layout. For same-scale orthographic comparison, record orthographic span, output dimensions, viewport and pixels per metre, and verify their relationship. Record lens/FOV for perspective cameras instead; they cannot claim a uniform pixel scale. All views still share one layout/model revision. ## Source hierarchy and trace evidence Populate `SOURCE_HIERARCHY.json` before tracing. Give each source a role: controlling appearance/geography, accepted layout/frame, supplemental close-up, historical method, or framing intent only. Resolve discrepancies explicitly. Record exact source bytes in the application; an attractive replacement image or a filename is not source acceptance. A superseded source can remain historical evidence but cannot silently control new geography. Each feature records ID, source ID/hash, source coordinates, geometry, visible versus inferred evidence, occlusion, confidence/author tolerance, proposed dimensions, unresolved decisions and later layout correspondence. Roof envelopes and visible facades must be distinguished from ground footprints. Trace both visible road margins where present; a centerline alone does not establish road width or junction geometry. Record block/building coverage across the full agreed district boundary, not only a photogenic crop. Preserve source pixels and immutable historical records. Three non-collinear shared controls are a minimum frame record, not sufficient calibration of an arbitrary perspective image. State the camera/registration model, residuals and terrain assumptions appropriate to the source. Retain a common world frame, north, origin, water datum, axis/units, neighbor boundaries and bridge connections. Do not use a local warp to conceal conflicts. Historical Crown v0.1, R07 proposals and other scenario dimensions remain separate until reconciled. ## Coverage and hard reference gate Populate `CONSTRUCTION_COVERAGE.json`. Every required coverage row has an identified inspection domain, expected item count or auditable area/length denominator, observed/authored count, uncovered/occluded regions, evidence paths/hashes, reviewer and disposition. Include the same fields separately for every district in `district_coverage`; aggregate counts cannot hide an uncovered district. Percentages require a recorded denominator; unknown totals remain unknown. Counts alone never prove a complete district. All district IDs in the agreed scope must appear in the coverage ledger, including explicitly unresolved boundaries. The required rows are source/scope freshness; coast and water edge; road margins; junctions; bridges/neighbor connections; building ground footprints and block coverage; frame and scale; coordinated layout; clean/labeled overhead and same-geometry massing views; location-tied ground/shore/sections; populated kit; validated downloads and references; and creator review. A genuinely inapplicable shore type or bridge needs an explicit reviewed reason. Essential source, frame, layout, buildings/blocks, downloads and review cannot be waived to manufacture readiness. | Reject condition | Gate consequence | Required correction | |---|---|---| | Same labels but unrelated images or absent geometry | Reference gate fails | Supply feature correspondence and shared layout/model evidence | | Sparse road schematic with missing buildings, blocks or district coverage | Whole-district readiness fails | Complete the agreed coverage or obtain an explicit narrower partial scope | | Stale-source tracing or unresolved appearance/geography conflict | Source gate fails | Retrace from the controlling bytes or record an accepted source change | | Unmarked speculative dimensions or uniform scale inferred from perspective | Frame/layout gate fails | Label proposals, reconcile controls and record review | | Overhead/SE/SW independently generated or inconsistent geometry | Coordinated-views gate fails | Regenerate all views from one layout/massing revision and verify camera/model records | | Shore studies not tied to layout locations or missing sections | Terrain-reference gate fails | Identify locations/section lines and compatible layout/datum | | Missing downloads, LFS pointers served as files, hash/CRC mismatch or unvalidated references | Package gate fails | Supply recoverable bytes, working delivery and exact inventory validation | | Native/export success or engine run used to excuse missing kit content | Reference gate remains failed | Finish and validate the reference kit separately | `tools/verify_district_construction.py` validates application structure, local file integrity, current source hashes, coverage evidence and the hard readiness conditions. Its negative tests exercise stale sources, schematic-only coverage, speculative scale, mismatched camera/model geometry, missing downloads and invalid package members. A passing partial-draft integrity check is not a passing readiness gate. Human visual/source review remains required; software cannot certify a tracing is faithful merely because hashes match. The review ZIP contains the guide/templates, not the repository verifier and regression-test source. The regression tests are owner-run evidence. Independent reproduction requires the matching repository tools/test revision; the ZIP alone does not reproduce them. ## Partial work and separate acceptance states Partial work requires an explicit agreement locator and precise scope, exclusions, missing evidence and next step. Label images, package and status as partial. Do not call a four-district study a completed district because one selected region is detailed. A local observation draft may legitimately have unknown scale, missing footprints and no massing views; it must keep the reference gate blocked. Its validation should succeed for honest record integrity while returning `reference_kit_ready: false` and concrete blockers. Track these independently: visual modernization; source observation coverage; authored layout/scale acceptance; complete pre-development reference kit; native/export readiness; actual Unreal playability. No automatic promotion occurs between them. The kit can be completed before engine access. A successful engine launch proves only the tested build and interactions, not every reference requirement or live behavior. The first application is `docs/sw-source-layout/R01/`: D03 The Grove, D04 South Beach, D20 Sunset Bay and D21 Genesis Campus, using the original WC-REF-005. It begins with source observations, not a measured or ready handoff. The D20/D21 split, exact district limits, calibrated frame, building ground contacts, blocks and terrain are open. The historical R05 clean-map tracing and R07 scale proposals are not current WC005 geometry. ## Development phases and honest progress Record a whole-region foundation pass before detailed density. Divide the accepted planning arrangement into stable zone IDs without silently accepting new district boundaries. For each zone identify source-mapped planning slots, candidate programs/assets, prerequisite shared routes, proposed phase, deliverable, evidence and owner. A slot ID is not a shell/global asset assignment. Unknown mappings stay unresolved. Track planning acceptance, foundation, exterior shells, selected interiors, world integration and playtest independently. A concept image, placeholder massing or published protocol does not complete those later stages. Use `DEVELOPMENT_PHASES.json`; retain null counts and `not_verified` when actual placement evidence is absent. Do not invent zero or a completion percentage from missing evidence. Name every percentage and its denominator: selected slots / slots in this exact planning revision is planned allocation; verified placed slots / that revision is placement coverage; zones passing a specified route test / scoped zones is exploration coverage. These describe different things. Whole-region completion is not an unweighted average of differently sized zones or stages; report evidence-based milestones until agreed effort weights and acceptance criteria exist. The SW R02 denominator of 58 is not the whole island. Recommended SW ordering: SW-00 foundation across all nine zones; SW-01 Crown-facing arrival/civic core; SW-02 marina/west waterfront; SW-03 southern spine and beach circuit; SW-04 northern branch; SW-05 playtest-led density. The separate SW schedule is a recommendation; protocol publication does not dispatch Quik or accept runtime results. ## Release and validation R05 is the current District Production workflow. Generate documents, manifests, bundles and branded pages through `tools/build_protocols.py`; validate the populated application separately with `tools/verify_district_construction.py`. The protocol ZIP is a workflow kit, not a complete SW construction package. Keep R04 source documents and downloads available from protocol history. The recovered R01 SW evidence and original R02 geometry remain dated source layers. Legend accepted the R02 arrangement for planning on 19 October; metric calibration, ground/shoreline detail, Crown/world alignment, complete reference coverage and engine gates remain open. The accepted planning arrangement is not rejected merely because its metre frame remains uncalibrated. The review page links that scoped acceptance and the proposed nine-zone development schedule. --- UNCHANGED PREVIOUS RELEASE / HISTORICAL BASELINE --- # District Production Protocol R04 PI-PROT-DISTRICT · 15 October 2026 · current workflow ## Identity and revision The old D01 label named a protocol document, not District 01. It collided with D01 Atlantis. Use the stable family **PI-PROT-DISTRICT** and revision **R04** for the workflow; keep D01-D21 for actual districts, including D02 Crown Key and D03 The Grove. Old D01 R02 filenames and URLs remain historical aliases; no geographic district is renumbered. R04 retains aerial coverage, the four build-package groups, scale reconciliation, reusable developer collections and the shared world requirements. `CONSOLIDATED.txt` contains this release, the preserved R03 guide and the unchanged D01 R02 baseline; R04 controls conflicts. The PDF/DOCX are this release guide. The ZIP is a protocol working kit, not a ready-to-import district. R04 adds the human-facing project brief and authorized planning-site links. R03 remains archived. Required aerial, scale, package and review gates are retained. ## The twelve-stage sequence | Step | Required work | Acceptance evidence | |---|---|---| | 01 | Intake and atlas | Current district/scene/location extract, source revisions, selected/deferred requirements | | 02 | Shared world frame | Boundary, datum, axes, origin, controls and neighbor connections | | 03 | Identity and modernization | Architecture, landscape, culture, mobility and selected era behavior | | 04 | Master and context | Controlling master, aerial/orbit coverage and player-height views; Gate A | | 05 | Authored layout | Measured roads, parcels, placements and exact spatial exports | | 06 | Topography | Ground/edge references, elevations and sections; Gate B | | 07 | Asset kit | Existing global families, developer collections, new-shell justification and reuse plan | | 08 | Building handoffs | the current Building Protocol exterior/interior scope, dimensions, shell dependencies and crosswalk | | 09 | Engine handoff | Versioned package inventory, launcher preflight and reproducible build order | | 10 | Blockout and sample | Connected measured blockout, representative playable building/street; Gate C | | 11 | Expand and verify | Kit rollout, selected interiors, connections, streaming, navigation and performance | | 12 | Release and publish | Source/evidence, atlas status, registry, manifests, current web guide and downloads | Design and rough layout can iterate together. Detailed rollout follows the accepted sample. Concept, layout, shell, engine and publication status are distinct. A template's presence does not pass a gate. ## Gate A: identity and visual blueprint Legend accepts the exact master and identity revision. Preserve the approved composition, shore, bridges, signature silhouettes, height intent and material language. Record modernization choices and any disagreement among views. An image is authoritative for its approved visual intent; metric coordinates come from a reviewed layout calibrated to that intent. Required coverage is named by role: clean overall/overhead and separate ID overlay; front/arrival context; rear/opposite context; east and west orbits; a typical player-height street; signature place/entrance; night or observable behavior when relevant; shared-border/bridge and cross-water sightlines. Select roles by the district's terrain and use. A role can be covered by an existing approved image or explicitly marked not applicable with a reason. A critical unresolved connection/view stays open. Every reference record names district, ID, camera role, file/hash, revision, era, assets/locations, authority and discrepancies. Include master/layout references in every new image request. Avoid redesigning the district independently at each camera angle. For Crown Key, the existing `/CrownKey/reference/` aerial/orbit set is part of the visual evidence, not optional decoration. ## Four build-package groups | Group | What it must explain | Crown Key historical example | |---|---|---| | A. Design references | Master, aerials/orbits, streets, entrances, identity and discrepancies | Current reference register and separate original images | | B. Authored measured layout | Editable coastline, roads, bridges, parcels/placements, units and source frame | Unreal References v01 ZIP: 7 files including layout JSON, clean/labeled plan exports and build script | | C. Exact layout views | Plan and two useful spatial views derived from the SAME layout revision/hash | Exact Layout Views v01 ZIP: 7 files; overhead and SE/SW views | | D. Terrain and edges | Topography/shore intent, sections, slopes, retaining walls, water interfaces and calibrated height data when used | Topo References v01 ZIP: 5 PNGs and README | Yes: the three named ZIPs supplied three complementary build-input groups. None replaces the design aerials, and none by itself proves a build is correct. Exact views must match the layout revision actually being built. The historical topo images are visual intent, not a calibrated elevation raster. The protocol handoff ZIP contains templates/instructions, not those three district-source ZIPs. `PACKAGE_INVENTORY.json` records role, revision, path/URL, hash, availability, authority, compatible layout hash and validator evidence. For each required group, supply valid inputs or explicitly record why it is blocked/not applicable. A recoverable local original is not a published download. Do not send a broken link as a complete handoff. ## Gate B: measured layout, terrain and scale Design units are metres; Unreal uses centimetres. Record actual axes, origin, north, sea-level datum, map transform and at least three non-collinear shared controls. Verify conversion in the real import path. Pin coastline, roads, grades, bridge endpoints/widths/clearances, parcel extents and placement transforms. Districts share one frame and the same connection records at both ends. Compare original source, current source and current engine measurements in `SCALE_RECONCILIATION.csv`. Inspect imported mesh dimensions and actor/component/baked scale. Record intended changes rather than inferring them from filenames or old captions. Crown Key's v01/v02 discrepancy remains unresolved by this release; it is not permission to shrink or enlarge the island again. Release blockout only with a named accepted layout and documented conditions. Mark incomplete terrain calibration explicitly. Never infer metres-per-pixel from a perspective aerial. Keep clean overhead, ID overlay, exact views and source JSON/model on the same revision. A later change lists effects on neighbors, bridges, parcels, buildings, interiors, skyline and travel times. ## Atlas, story and reusable architecture Read current creator decisions and the current working atlas before selecting rooms or building scope. Preserve PI-LOC IDs, scene/era status, routes, conceptual AK kit links and unresolved questions. Map requirement to placement, global asset, shell, level/room and test. Do not promote illustrative map pins or a proposed tower assignment to approved geography. Use developer collections and a limited number of shell families. Separate geometry variants from appearance presets and district placements. Author typical rooms/floors once, then identify their instances. A district does not need a unique building for every location or a complete interior in every tower. the current Building Protocol's A-E tiers control coverage and keep technical plans separate from perspective counts. ## Gate C: connected playable sample Build a representative route, exterior and selected interior at the candidate scale. Test character/camera, furnished room clearances, roads/bridges, collision, navigation, access, water, neighboring sightlines and streaming. Compare matched engine captures to the controlling images. Legend accepts visual conformance; Quik accepts the measured technical approach. Record conditions and remaining issues. The architecture direction is one project and one authoritative World Partition world with shared coordinates, externally stored actors and reusable assets. Load work regions in the editor. Staging maps are allowed for authoring/tests; independent district saves linked by ordinary level travel are not the default connected-city design. Choose the actual integration map after inspecting current content. Hundreds of users in a persistent city is a design target. World Partition is spatial streaming, not multiplayer capacity or a persistence service. Test dedicated-server networking, crowded and distributed loads, NPC budgets and durable state separately. Preserve cross-water vistas through an appropriate distant representation; do not assume all distant detailed geometry remains resident. ## Engine handoff, launcher and release Specify engine/project/map version, required plugins, source paths, build/import order, deterministic seeds if used, backups, data/asset dependencies and clean-machine reproduction. The launcher is required infrastructure and remains unverified until it can resolve versions, check files/hashes, run supported jobs, surface errors and reproduce a sample. Do not claim a template implements an importer or launcher. Release a README with gate states, package inventory, current source and screenshots/tests. Include brief, frame, connections, layout, terrain records, atlas mapping, reuse/placements, building links, shot list, approvals/change log, conformance sheet and engine/launcher QA. Update the registry, manifests and site from the current pointer. Preserve earlier revisions and source art. Only add a future district as a completed case study after it has followed these gates. The companion shared-world brief gives Quik the integration and daily workflow. Creator-authorized Black Vault sessions, developer collections and building programs are published separately on the production desk, with status intact. This exception does not authorize unrelated Studio-only material or credentials. Workflow publication is not proof of current world readiness. ## Companion pages [Production desk](/production/desk/) · [Quik's brief](/protocols/world/) · [Developer collections](/production/developers/) · [Crown Key work plan](/production/crown-key/) · [Grove image plan](/production/grove/) · [Scale register](/production/scale/) · [Black Vault](/black-vault/). --- INHERITED PREVIOUS RELEASE / CURRENT GUIDE CONTROLS CONFLICTS --- # District Production Protocol R03 PI-PROT-DISTRICT · 15 October 2026 · current workflow ## Identity and revision The old D01 label named a protocol document, not District 01. It collided with D01 Atlantis. Use the stable family **PI-PROT-DISTRICT** and revision **R03** for the workflow; keep D01-D21 for actual districts, including D02 Crown Key and D03 The Grove. Old D01 R02 filenames and URLs remain historical aliases; no geographic district is renumbered. R03 makes aerial coverage, the four build-package groups, scale reconciliation, reusable developer collections and the shared world explicit. `CONSOLIDATED.txt` contains this release and the unchanged D01 R02 baseline; R03 controls conflicts. The PDF/DOCX are this release guide. The ZIP is a protocol working kit, not a ready-to-import district. ## The twelve-stage sequence | Step | Required work | Acceptance evidence | |---|---|---| | 01 | Intake and atlas | Current district/scene/location extract, source revisions, selected/deferred requirements | | 02 | Shared world frame | Boundary, datum, axes, origin, controls and neighbor connections | | 03 | Identity and modernization | Architecture, landscape, culture, mobility and selected era behavior | | 04 | Master and context | Controlling master, aerial/orbit coverage and player-height views; Gate A | | 05 | Authored layout | Measured roads, parcels, placements and exact spatial exports | | 06 | Topography | Ground/edge references, elevations and sections; Gate B | | 07 | Asset kit | Existing global families, developer collections, new-shell justification and reuse plan | | 08 | Building handoffs | Building R04 exterior/interior scope, dimensions, shell dependencies and crosswalk | | 09 | Engine handoff | Versioned package inventory, launcher preflight and reproducible build order | | 10 | Blockout and sample | Connected measured blockout, representative playable building/street; Gate C | | 11 | Expand and verify | Kit rollout, selected interiors, connections, streaming, navigation and performance | | 12 | Release and publish | Source/evidence, atlas status, registry, manifests, current web guide and downloads | Design and rough layout can iterate together. Detailed rollout follows the accepted sample. Concept, layout, shell, engine and publication status are distinct. A template's presence does not pass a gate. ## Gate A: identity and visual blueprint Legend accepts the exact master and identity revision. Preserve the approved composition, shore, bridges, signature silhouettes, height intent and material language. Record modernization choices and any disagreement among views. An image is authoritative for its approved visual intent; metric coordinates come from a reviewed layout calibrated to that intent. Required coverage is named by role: clean overall/overhead and separate ID overlay; front/arrival context; rear/opposite context; east and west orbits; a typical player-height street; signature place/entrance; night or observable behavior when relevant; shared-border/bridge and cross-water sightlines. Select roles by the district's terrain and use. A role can be covered by an existing approved image or explicitly marked not applicable with a reason. A critical unresolved connection/view stays open. Every reference record names district, ID, camera role, file/hash, revision, era, assets/locations, authority and discrepancies. Include master/layout references in every new image request. Avoid redesigning the district independently at each camera angle. For Crown Key, the existing `/CrownKey/reference/` aerial/orbit set is part of the visual evidence, not optional decoration. ## Four build-package groups | Group | What it must explain | Crown Key historical example | |---|---|---| | A. Design references | Master, aerials/orbits, streets, entrances, identity and discrepancies | Current reference register and separate original images | | B. Authored measured layout | Editable coastline, roads, bridges, parcels/placements, units and source frame | Unreal References v01 ZIP: 7 files including layout JSON, clean/labeled plan exports and build script | | C. Exact layout views | Plan and two useful spatial views derived from the SAME layout revision/hash | Exact Layout Views v01 ZIP: 7 files; overhead and SE/SW views | | D. Terrain and edges | Topography/shore intent, sections, slopes, retaining walls, water interfaces and calibrated height data when used | Topo References v01 ZIP: 5 PNGs and README | Yes: the three named ZIPs supplied three complementary build-input groups. None replaces the design aerials, and none by itself proves a build is correct. Exact views must match the layout revision actually being built. The historical topo images are visual intent, not a calibrated elevation raster. The protocol handoff ZIP contains templates/instructions, not those three district-source ZIPs. `PACKAGE_INVENTORY.json` records role, revision, path/URL, hash, availability, authority, compatible layout hash and validator evidence. For each required group, supply valid inputs or explicitly record why it is blocked/not applicable. A recoverable local original is not a published download. Do not send a broken link as a complete handoff. ## Gate B: measured layout, terrain and scale Design units are metres; Unreal uses centimetres. Record actual axes, origin, north, sea-level datum, map transform and at least three non-collinear shared controls. Verify conversion in the real import path. Pin coastline, roads, grades, bridge endpoints/widths/clearances, parcel extents and placement transforms. Districts share one frame and the same connection records at both ends. Compare original source, current source and current engine measurements in `SCALE_RECONCILIATION.csv`. Inspect imported mesh dimensions and actor/component/baked scale. Record intended changes rather than inferring them from filenames or old captions. Crown Key's v01/v02 discrepancy remains unresolved by this release; it is not permission to shrink or enlarge the island again. Release blockout only with a named accepted layout and documented conditions. Mark incomplete terrain calibration explicitly. Never infer metres-per-pixel from a perspective aerial. Keep clean overhead, ID overlay, exact views and source JSON/model on the same revision. A later change lists effects on neighbors, bridges, parcels, buildings, interiors, skyline and travel times. ## Atlas, story and reusable architecture Read current creator decisions and the current working atlas before selecting rooms or building scope. Preserve PI-LOC IDs, scene/era status, routes, conceptual AK kit links and unresolved questions. Map requirement to placement, global asset, shell, level/room and test. Do not promote illustrative map pins or a proposed tower assignment to approved geography. Use developer collections and a limited number of shell families. Separate geometry variants from appearance presets and district placements. Author typical rooms/floors once, then identify their instances. A district does not need a unique building for every location or a complete interior in every tower. Building R04's A-E tiers control coverage and keep technical plans separate from perspective counts. ## Gate C: connected playable sample Build a representative route, exterior and selected interior at the candidate scale. Test character/camera, furnished room clearances, roads/bridges, collision, navigation, access, water, neighboring sightlines and streaming. Compare matched engine captures to the controlling images. Legend accepts visual conformance; Quik accepts the measured technical approach. Record conditions and remaining issues. The architecture direction is one project and one authoritative World Partition world with shared coordinates, externally stored actors and reusable assets. Load work regions in the editor. Staging maps are allowed for authoring/tests; independent district saves linked by ordinary level travel are not the default connected-city design. Choose the actual integration map after inspecting current content. Hundreds of users in a persistent city is a design target. World Partition is spatial streaming, not multiplayer capacity or a persistence service. Test dedicated-server networking, crowded and distributed loads, NPC budgets and durable state separately. Preserve cross-water vistas through an appropriate distant representation; do not assume all distant detailed geometry remains resident. ## Engine handoff, launcher and release Specify engine/project/map version, required plugins, source paths, build/import order, deterministic seeds if used, backups, data/asset dependencies and clean-machine reproduction. The launcher is required infrastructure and remains unverified until it can resolve versions, check files/hashes, run supported jobs, surface errors and reproduce a sample. Do not claim a template implements an importer or launcher. Release a README with gate states, package inventory, current source and screenshots/tests. Include brief, frame, connections, layout, terrain records, atlas mapping, reuse/placements, building links, shot list, approvals/change log, conformance sheet and engine/launcher QA. Update the registry, manifests and site from the current pointer. Preserve earlier revisions and source art. Only add a future district as a completed case study after it has followed these gates. The companion shared-world brief gives Quik the integration and daily workflow. Story brainstorms and spoiler-bearing building programs stay in the private repository. Workflow publication is not proof of current world readiness. --- INCORPORATED HISTORICAL BASELINE The release guide above controls any conflict. Historical dates, page numbers and aliases below are retained for provenance. IMMORTAL LEGEND STUDIOS / PRODUCTION MANUAL District Protocols. Design the place. Hand over the decisions. Build it to the approved specification. D01 / R02 - REVISED FIRST DRAFT Atlas-led design. Modernized worldbuilding. A repeatable reference-to-Unreal workflow for all 21 districts. Crown Key is the worked production reference. Future district case studies enter this manual after they have followed the protocol. 14 October 2026 / Prepared for Legend and Quik Workflow proposal. Individual designs, placements and runtime readiness retain their own approval and evidence. THE COMPLETE PRODUCTION SEQUENCE PROTOCOLS / DISTRICT | D01 R02 | 02 The complete production sequence R02 turns the first draft into an operating manual. Follow the sequence, fill the records, and carry the exact revisions into engine. Every step has an output and a readiness check. Step | Work | Required output | Page 01 | Intake + atlas | Brief; atlas extract; scene/location requirements | 4-5 02 | World frame | Boundary, datum, transforms and neighbor connections | 9 03 | Identity + modernization | District-specific look and behavior brief | 6 04 | Master + context | Master card, aerials and player-height views / Gate A | 7-8 05 | Authored layout | Roads, parcels, placement and measured spatial exports | 9 06 | Topography | Ground/edge references and sections / Gate B | 10 07 | Asset kit | Reuse plan, global IDs and model tasks | 11 08 | Building handoffs | Selected R03 exteriors/interiors; shell dependencies | 12 09 | Engine handoff | Versioned package, launcher preflight and build order | 13-14 10 | Blockout + sample | Measured blockout; playable quality sample / Gate C | 15 11 | Expand + verify | Approved kit rollout, selected interiors and QA | 16 12 | Release + publish | Source, evidence, atlas/registry/page updates | 16-17 Design and rough layout may iterate together. Detailed expansion starts after Gate C. Building-shell and interior checks still follow Building R03. A source mismatch becomes an assigned issue before affected work proceeds. Use tonight: begin with the district intake on page 18, then the atlas and modernization pages. Establish the design inputs before generating the reference set. Working templates mirror these steps. They are planning records; the existing engine import schemas and launcher jobs require their own implementation and verification. BUILD TO THE SPECIFICATION PROTOCOLS / DISTRICT | D01 R02 | 03 Build to the specification An approved district brief, reference set and layout are the build contract. Implementation must carry their decisions into engine. Missing information is recorded and resolved; it does not silently become a new creative direction. Decision | Controlling source Story and era | Latest creator decisions, canon and current selected game edition; unresolved conflicts remain visible. Required places and scenes | Versioned atlas plus creator-approved placement/scope decisions. District identity | Approved master card, modernization brief and controlling reference images. Geometry and placement | Approved measured layout, shared frame and reviewed building shells. Technical implementation | Engine lead sets agreed import, collision, runtime and reproducibility targets. Built and tested claims | Dated evidence at the named commit, map, machine and settings. • Every requirement receives an ID, source revision, owner and acceptance evidence. Link it to the asset, placement or route that implements it. • Any change to identity, footprint, road, bridge, skyline, story assignment or era needs a recorded change decision before affected work expands. • Routine technical fixes may proceed within the approved envelope. If a fix changes the design or geography, record the impact and obtain the relevant decision. • Existing work receives a conformance review: retain, revise, replace or unverified, with reasons. Presence in a scene does not establish design acceptance. • Compare matched concept and engine views. Log each discrepancy; show the correction before accepting that requirement. Three district gates A / Identity: Legend accepts the brief, modernization and visual direction with preliminary asset scope. B / Layout: the measured layout, topology and shared connections are released for blockout. C / Sample: Legend accepts the look in engine; Quik accepts the technical approach. Publication, launcher readiness and building approvals are separate records. Record conditions and unresolved items beside each gate. 01 / START WITH THE ATLAS PROTOCOLS / DISTRICT | D01 R02 | 04 01 / Start with the atlas The atlas helped connect story needs to Crown Key development. It is a required production input, reviewed before the district look, layout or building scope is finalized. Read from the atlas | Carry into production District record + location IDs | Extract every location associated with the district. Keep the stable PI-LOC ID and map label. Scenes + game coverage | List linked scenes, era, characters if specified, intended activity, source evidence and edition status. Subspaces + placement questions | Translate rooms, access, privacy and view requirements into build tasks. Keep proposed assignments proposed. Routes | Identify cross-district dependencies, entry/exit, movement mode, sequence and access/sightline checks. AK kits + future behavior | Use the kit components, visual direction, sound, deliverables and acceptance notes to scope assets and modernization. Issues + nonphysical sets | Assign relevant open issues. Keep memory/virtual sets separate from physical island geography. Required operation Start with: The versioned atlas, latest creator decisions, district board and current game edition. Do: Filter by district and location IDs; include all touching scenes and routes, linked kits and relevant issues. Mark each requirement selected, deferred or unresolved, with a reason. Do not turn historical or alternative scenes into mandatory scope. Deliver: ATLAS_REQUIREMENTS.json; ATLAS_BUILD_MAP.csv; requirement IDs linked to sources. Ready when: Every associated location is accounted for, and selected scenes have explicit spaces, access and asset needs. Coordinate rule: the inspected atlas anchors are illustrative image pixels. They locate a target zone; they do not provide surveyed parcels, engine coordinates or building dimensions. Resolve those through the authored layout. Status rule: Established, Placement proposed and Built are independent. Approved district boards do not automatically approve a scene placement or interior. Preserve source statuses; use current engine evidence for current build claims. Evidence: S13 - Current V2.1 story-location atlas (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/the-island/development/atlas/atlas.json) / S21 - Crown Key atlas integration builder (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/crownkey/build.mjs) ATLAS TO BUILDING TO PLAYABLE SPACE PROTOCOLS / DISTRICT | D01 R02 | 05 Atlas to building to playable space Crown Key shows why the atlas belongs at the start. Its two story locations require specific spaces and routes. Their exact building assignments still require a placement and shell check. Atlas requirement | Design / model task | Placement and engine check L18 / PI-LOC-018 - council and vote suite | Vote room, waiting space, celebration room, empty corridor and view window. Select linked novel/game scenes by edition. | Map the actual asset and parcel; verify access, room adjacency and the repeated meeting route. L19 / PI-LOC-019 - diplomacy office / private lounge | Breakfast room, private office, lounge and secured records. Preserve independent access where the selected scene needs it. | Check candidate relationship to L18, privacy and circulation in the reviewed shell. Crown Landmark INT R02 | The issued pack proposes council on L25 and diplomacy on L26. It is a design/production candidate. | Confirm the asset-to-location mapping, parcel, entrance direction and floor fit before final assignment or window views. The required mapping Scene ID + era → PI-LOC → requirement ID → parcel + placement → global building variant → floor/room IDs → route or interaction → engine evidence. Each row must retain placement status, chosen scope, source revision, owner and open questions. One location may occupy several rooms; several locations may share a building. Assigning a location never requires a new exterior by default. The atlas AK identifiers represent conceptual production kits. PI-BLD and PI-STR identify reusable architectural assets. District placement IDs identify instances. Room IDs identify spaces. Preserve these distinctions in the mapping. Views: assign the building and orientation first; derive final window backgrounds from the placed model and room elevation. Neutral backgrounds remain valid during interior development. Evidence: S05 - Crown Landmark EXT R06 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/EXT/R06/README.md) / S06 - Crown Landmark INT R02 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/INT/R02/README.md) / S13 - Current V2.1 story-location atlas (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/the-island/development/atlas/atlas.json) 03 / MODERNIZE WITH PURPOSE PROTOCOLS / DISTRICT | D01 R02 | 06 03 / Modernize with purpose Each district needs an intentional Lost Souls era treatment. A familiar reference image is only a starting point; the approved brief must describe how this place belongs to the universe. Layer | Decision to make | Evidence to commission Architecture | Signature forms, climate response, local density, materials, age and maintenance. | Master card and typical player-height frontage. Public realm | Walkability, shade, planting, street furniture, drainage and shoreline transitions. | Street / edge view plus measured section where needed. Mobility + services | How people, vehicles, boats, utilities and deliveries move through the approved geography. | Route diagram and practical access checks. Technology | Choose specific adaptive, access, energy or surveillance behavior appropriate to this district and era. | Behavior note: trigger, visible/audio response, consequence and build scope. Culture + occupation | Local work, music, fashion, hospitality, institutions, signage and activity. | Signature place with meaningful occupation and dressing. Paradise + control | Decide how invitation, comfort, restriction and unease appear here, where supported by canon. | Lighting, sound and access references tied to selected scenes. Modernization brief Start with: Approved district identity, selected atlas AK notes, scene/era requirements and island-wide systems. Do: Write preserve / upgrade / avoid decisions. Define 3-5 recognizable design traits and 1-3 observable behaviors as a planning allowance. Separate visual treatment from working gameplay systems. Deliver: MODERNIZATION.json; palette/material notes; behavior requirements. Ready when: Someone can explain the district at street height and in the chosen era, and each selected behavior has an owner and test. Do not invent a new chronology through image captions. Resolve era conflicts against creator decisions. An earlier or later state is a separately scoped variant with its own references and approval. Evidence: S01 - Current creator decisions (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/docs/current-decisions.md) / S13 - Current V2.1 story-location atlas (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/the-island/development/atlas/atlas.json) 04 / BUILD THE MASTER REFERENCE PROTOCOLS / DISTRICT | D01 R02 | 07 04 / Build the master reference The master card establishes the visual identity. Keep it readable as a browsing board, and retain each useful image separately at its original quality for modeling and review. Master card Start with: The brief, selected atlas program, modernization notes, island crop, rough layout and current approved district art. Do: Select a controlling overhead/context image; add a typical street, signature place and relevant edge/arrival. Label identity, materials and key location candidates without declaring unsurveyed geometry. Deliver: Current master card; individual source images; REFERENCE_SHOT_LIST.csv with roles, revisions and controlling status. Ready when: The overhead and ground views share building language, material character, vegetation, era and district role. Gate A records the exact accepted revision. Crown Key / Crown Landmark arrival reference. A player-height image resolves entrance scale and material character that an aerial cannot. Design reference; engine conformance requires a matched capture. Consistency review: compare repeated silhouettes, shorelines, bridge count, landmark position, height intent, signage and light. If generated views disagree, identify the controlling source and correct/defer the conflicting view. Record the discrepancy; do not average incompatible geometry. Evidence: S03 - Crown Key design render register (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/references/references.json) / S05 - Crown Landmark EXT R06 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/EXT/R06/README.md) 04 / AERIALS, STREETS AND SHOT ROLES PROTOCOLS / DISTRICT | D01 R02 | 08 04 / Aerials, streets and shot roles Reproduce the coverage that made Crown Key understandable from multiple viewpoints. Counts below guide commissioning; every needed role must be supplied, covered by reuse, deferred or marked not applicable with a reason. Role | Question the image must answer | Typical coverage Overall / label-free | What is the district composition without labels obscuring the scene? Keep a separate ID overlay. | 1 controlling overall + overlay Arrival / front context | How does the district connect, and what is encountered first? | 1 view Opposite / rear context | What happens on the less visible shore or backside? | 1 view East / west orbits | Does the visual language hold from both sides? Are landmarks and edges understood? | 2 useful views Typical player-height street | What does an ordinary route feel like at human scale? | 1-2 scenes Signature place / entrance | What makes the district recognizable, and how is its main place accessed? | 1-2 scenes Night / behavior | How does the district function and feel when lighting or occupancy changes? | 1-2 views if relevant Measured exports | Where are roads, parcels, buildings and heights actually located? | Plan + 2 views from one model Crown Key currently has a master card and 13 context renders, including location close-ups and aerial/orbit coverage. New districts need equivalent decision coverage at their own density and terrain; existing approved art may already satisfy some roles. Every image record includes district ID, reference ID, role, source file, revision, era, linked locations/assets, authority and known discrepancies. A new camera angle does not create a new asset variant. Authoring instruction: provide the selected master, identity notes and controlling layout in each new image request. Name the camera role and the unresolved build question. Avoid re-inventing the district with each prompt. Evidence: S03 - Crown Key design render register (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/references/references.json) 02 + 05 / MAKE THE LAYOUT BUILDABLE PROTOCOLS / DISTRICT | D01 R02 | 09 02 + 05 / Make the layout buildable World frame Start with: Approved island boundary and neighboring geometry; source image dimensions; existing measured data. Do: Record metres, axes, origin, rotation and sea datum. Define a transform for each source crop. Validate at least three shared control points and both ends of every district connection. Deliver: WORLD_FRAME.json; CONNECTIONS.json; control-point evidence. Ready when: Units and shared endpoints agree across districts. Perspective artwork has not been treated as survey data. Authored layout Start with: The verified frame, accepted visual direction, atlas access requirements and preliminary kit. Do: Author coastline, road classes/widths, parcels, footprints, heights, entrances, public space and service routes. Assign placement IDs and link candidate story locations. Export north-up plan and two aerials from the same layout/model. Deliver: LAYOUT.json or compatible existing schema; PLACEMENTS.csv; measured overhead and spatial exports. Ready when: Every footprint has scale and access; selected story programs can fit; shared connections and ground transitions can be checked. Release through Gate B after topography review. Crown Key lesson | Required response Several construction generations exist | Select a baseline explicitly. Keep traced concepts, authored v0.1/v0.2 and newer visual references distinguishable. v0.2 scale metadata disagrees | Reconcile scale_vs_v01 2.0 versus the x1.8 status text using actual dimensions. Y conversion conventions differ | Record and test the current local-to-engine conversion; do not copy a stale formula into the next district. Use local-metre data with an explicitly stated frame. Ordinary geographic GeoJSON should not silently contain local metres. Planning templates must be adapted to the project importer; filling them alone does not import a district. Evidence: S09 - Brickell development history (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/docs/PROGRESS.md) / S12 - Brickell layout v0.2 (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/data/districts/brickell_layout_v02.json) 06 / GROUND, SHORE AND TRANSITIONS PROTOCOLS / DISTRICT | D01 R02 | 10 06 / Ground, shore and transitions A flat plan does not describe the ground. The Crown Key topography set answered five distinct construction questions; commission the equivalent questions for each district. Crown Key reference role | Required information Beach + shallows | Sand-to-water transition, depth character, reef/rock patches and accessible shore. Seawall + promenade | Wall height, cap, walking surface, rails and the relationship to water. Waterfront edge | Road-to-building-to-water section, setback, curb, slope and usable frontage. Bridge landing | Deck-to-road transition, abutment, approach slope and pedestrian continuity. Park / green edge | Terrain rise/fall, path, planting layers and adjacent street/building transitions. Topography pack Start with: Approved layout, water datum, edge types, access modes and relevant existing reference kits. Do: Create one clear reference per unresolved edge type and dimensioned sections where needed. Substitute cliff, forest or industrial conditions when relevant. Record which aspects are visual intent and which are measured geometry. Deliver: Ground/edge pack; section drawings; terrain material and planting notes; annotated problem locations. Ready when: The engine lead can build vertical transitions and test walk/drive/water access without inferring them from a flat aerial. Historical Crown Key ground/edge reference set. Current architecture and layout are governed separately. Gate B checks frame, roads/parcels, shared connections and terrain transitions together. Source, preview and download availability are tracked separately in the reference registry. Evidence: S08 - Reference-page catalog and availability (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/CrownKey/reference/catalog.json) / S09 - Brickell development history (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/docs/PROGRESS.md) 07 / BUILD THE DISTRICT ASSET KIT PROTOCOLS / DISTRICT | D01 R02 | 11 07 / Build the district asset kit Catalog and reuse Start with: Accepted visual direction, authored layout, atlas AK components and existing asset registry. Do: Inventory reusable families first. Scope new geometry only where the district identity or program needs it. Separate architectural assets, infrastructure, foliage, ground materials, street props, vehicles/vessels and interior kits. Deliver: KIT_AND_REUSE.json; global-ID cards/lookup; asset task queue; dimensional envelopes; source/export records. Ready when: Every planned placement links to an existing asset or an owned task. Reference art, generated model, reviewed model and engine-ready state are distinguishable. Record type | Purpose / example PI-BLD / PI-STR | Stable reusable family and geometry variant, including existing global catalog IDs. District placement | One instance: asset variant, parcel, coordinates, orientation, entrance and layout revision. PI-LOC / scene ID | Narrative location and selected scenes; linked through the atlas build map. Room / door IDs | Building-level spaces and connections; issued under the applicable building pack. AK kit | Atlas conceptual kit scope; resolve its components to real asset IDs or tasks. • Record dimensions, units, up axis, pivot and modular connection points. Approve technical budgets with Quik per category and project target. • Keep editable source, agreed exports, texture paths, source application/version and provenance. Record allowed storage and release destinations. • Suggested model path: reference → scoped generation/manual model → dimensional cleanup → inspection → validation → engine import → tested placement. Use the actual approved tools and mark unsupported automation unimplemented. • An attractive catalog card is a design reference. A usable kit also needs measured models, materials, source files and verified import behavior. Evidence: S04 - Global asset family and variant lookup (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/catalog/Legacy_Label_Lookup.json) / S18 - Launcher + District Kit build plan v2 (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/launcher/plan-v2.md) 08 / CHOOSE BUILDING DEPTH UNDER R03 PROTOCOLS / DISTRICT | D01 R02 | 12 08 / Choose building depth under R03 Building Protocol R03 remains the building-level authority. Set scope per building and selected gameplay program, then commission only the views that answer useful questions. R03 scope | Perspective guidance | Required coverage A / Exterior only | 0 interior views | Exterior treatment, scale, access classification and placement. B / Small enterable space | 2-4 per space | Principal view, useful reverse angle, access and simple plan. C / Reusable interior kit | 4-6 per kit | Typical rooms, connections, dimensions and component schedule. D / Gameplay building | 6-10 per building | Distinct playable rooms, routes and interaction/access clearances. E / Major story landmark | 10-16 initially | Principal rooms, circulation and selected details; justify expansion. Exterior and interior handoffs Start with: Asset and placement IDs, selected atlas rooms/scenes, dimensioned envelope and R03 scope. Do: Prepare exterior coverage, plan/scale references and selected interiors. Include room/door schedules and intended circulation. Review the shell before final interior fit. Use typical floor kits where repeated. Deliver: Revisioned EXT/INT packs; room/door records; atlas-to-room mapping; shell-fit issues. Ready when: The geometry can fit the intended program and access. Window views are neutral/conceptual until site orientation and elevation are verified. Crown Landmark EXT R06 and INT R02 are a deep landmark example. Its 25 individual interior views are an issued package, not a universal district requirement. Plans and schedules sit outside perspective counts. Evidence: S05 - Crown Landmark EXT R06 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/EXT/R06/README.md) / S06 - Crown Landmark INT R02 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/INT/R02/README.md) / S07 - Building Protocol R03 (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/protocols/R03/Paradise_Island_Building_Asset_Protocol_R03.txt) 09 / HAND OVER A COMPLETE BUILD TASK PROTOCOLS / DISTRICT | D01 R02 | 13 09 / Hand over a complete build task A contributor should be able to open one entry point and understand the approved target, source files, build order and checks. Record missing information before the affected task starts. Handoff component | Must be explicit Entry point + source versions | District brief, protocol revision, approval register, frame/layout revisions and source commits. Reference authority | Controlling master and per-role images; atlas requirements and unresolved discrepancies. Placement + assets | Measured placement data, global IDs, asset sources, import settings and model readiness. Build order | Terrain/datum → connections → roads → shells → ground/materials → dressing → selected interiors/systems. Execution path | Launcher/job versions and local config if verified; otherwise exact reviewed commands and logs. Acceptance evidence | Matched capture cameras, selected scene/route tests, performance conditions and discrepancy register. Copy-ready instruction for Quik or another engine contributor Build district [ID/name] from handoff [revision] at source [commit]. Read the brief, atlas extract, modernization notes, approved references and frame/layout first. Report missing or conflicting inputs. Use the placement and asset records; keep unresolved assignments unassigned. Follow the documented build order. Create the measured blockout, compare the plan and matched views, and log deviations. Produce the agreed representative sample. Run the specified access, collision, route and performance checks. Attach logs/captures and identify the exact map and revisions. Expand after the recorded sample gate. Changes to approved design or geography go through the change record. Return: source commit; map/project path; actor/placement crosswalk; implemented requirements; failed/unverified checks; dated evidence; open decisions; next task. Do not equate a successful script exit, attractive render or published page with a tested district. 09 / LAUNCHER READINESS IS A DEPENDENCY PROTOCOLS / DISTRICT | D01 R02 | 14 09 / Launcher readiness is a dependency Status: required / unverified. The user reports that the launcher has not been used or proven. The repo contains a build plan; this manual does not claim a working desktop runner or a passing launch. The plan describes a local desktop companion that runs registered Unreal/Blender jobs, reports pass/fail with evidence and keeps history. It also proposes district manifests, asset standards and batch production. These are execution capabilities, separate from the protocol website. Proof required | Acceptance evidence Local setup / preflight | Record machine, project, Unreal/Blender/Python paths, tool versions, source revision and district manifest resolution. Registered jobs only | Validate parameters and supported district; prevent arbitrary command execution and accidental fallback to Brickell paths. Successful actual job | Run a small reviewed non-destructive job on a named district; retain complete log, structured/legacy result and expected output artifacts. Failure is reported correctly | Exercise a bad path or controlled job failure; distinguish PASS, FAIL and ERROR. Exit code 0 alone is insufficient. Process safety | Declare editor-closing behavior. Prove cancel/timeout handling, no orphan processes and restoration of affected config/backups. Repeatability + portability | Repeat the passing job; test district selection and machine-specific config. Prove a second district before claiming scale. History + target map | Retain job/district/commit/parameters/result/evidence. Where a job loads a map, show the intended district loaded. Until proof exists, design and reference production can proceed. Reviewed direct commands with logs can support engine work. Launcher-dependent automation remains blocked/unverified; launch buttons and a plan page do not verify execution. The 9 October plan includes historical paths, legacy IDs, provisional technical budgets and old build-state claims. Reconcile them with the current project and global asset registry before implementation. Credentials must stay out of logs and source. Evidence: S18 - Launcher + District Kit build plan v2 (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/launcher/plan-v2.md) 10 / PROVE THE BLOCKOUT AND SAMPLE PROTOCOLS / DISTRICT | D01 R02 | 15 10 / Prove the blockout and sample Measured blockout Start with: Gate B layout/frame, topography, asset envelopes, connections and engine handoff. Do: Build terrain and crossings, road network and simple shells. Verify control points, entrances, heights, player scale and intended access. Compare the measured plan plus two spatial views. Deliver: Blockout map/revision; matched captures; requirement conformance records. Ready when: Spatial fit and movement work. Deviations have a disposition and owner before detailed repetition. Representative playable sample Start with: The checked blockout, accepted visual direction and scoped assets/materials. Do: Finish a connected route containing an arrival, ordinary frontage and signature place. Add day/night when relevant. Test the selected atlas access/scene requirements and chosen modernization behavior. Deliver: Playable sample; matched captures; route/access logs; performance evidence on the agreed machine/settings. Ready when: Gate C records Legend's visual acceptance and Quik's technical acceptance at the same sample revision. Review lens | Check in engine Identity + modernization | The district is recognizable at street height; selected era behavior is observable or explicitly deferred. Human scale + routes | Doors, sidewalks, stairs, slopes and transitions support the intended player/vehicle/vessel access. Finish + atmosphere | Silhouette, material depth, planting, signs, lighting, sound and occupation agree with the accepted reference. Technical viability | Collision/navigation, frame time, memory and loading behavior meet the agreed sample targets. Sample length follows the district and approved route. Stop expansion when the sample misses the agreed quality or technical target; record the fix, repeat the affected check, and then continue. 11 + 12 / EXPAND, VERIFY AND RELEASE PROTOCOLS / DISTRICT | D01 R02 | 16 11 + 12 / Expand, verify and release Expand the accepted approach Start with: Gate C sample, measured layout and approved kits. Do: Apply the accepted modules, materials and planting logic across scoped placements. Add selected R03 interiors and systems. Recheck affected rooms/routes as shells become final. Deliver: Updated scene, placement and asset states; implemented requirements; QA register. Ready when: Each planned item is built, deferred or out of scope with a recorded reason. No unreviewed district-wide design substitution has occurred. Release check | Evidence Spec conformance | Approved requirement → implementation → matched capture/test. Every discrepancy has a disposition. Atlas / gameplay | Selected scene spaces, arrival/exit routes, privacy, sightlines and movement work at the intended era. Technical quality | Collision, NPC navigation where scoped, materials/textures, intended movement and streaming/loading checked. Performance | Hardware, resolution, settings, route, frame time/FPS, memory and loading observations recorded. Sources / reproduction | Source commit, engine/project version, editable files, exports, textures, build order and dependencies. Publication | Manifest and links valid; district page, production registry, atlas build status and archive reflect the released revision. Use separate statuses: design-approved; layout-approved; shell-approved; interior-approved; engine-tested; published. Keep launcher verification separate. A deferred system must not be presented as working. Refresh atlas build evidence through a reviewed update; preserve narrative/proposed placement statuses unless an explicit decision changes them. Keep release history and allow recovery of the prior revision. ONE PACKAGE. ONE REVISION. CLEAR OWNERS. PROTOCOLS / DISTRICT | D01 R02 | 17 One package. One revision. Clear owners. District folder / record | Purpose README + DISTRICT_BRIEF | Current revision, owners, approved inputs, scope and open decisions. atlas + requirements | Versioned extract, source links, build mapping and conformance checks. frame + layout | Measured geometry, source transforms, connections, placements and spatial exports. references + catalog | Keep current paths compatible. Master, image index, modernization notes and reuse links. engine + qa | Build order, launcher readiness, map paths, captures, logs and performance results. approvals + release | Revision-specific gates, changes, dependencies and release manifest. District root: production/districts/D##-Name/. Shared buildings remain under production/assets/buildings/. The protocol has one canonical revision under production/protocols/D01/. Quik's branch references that revision and commit with an engine companion for its actual paths/jobs. Owner | Responsibility Legend | District identity, modernization, relevant story/placement decisions and creative acceptance. Reference / layout authors | Atlas extraction, coherent references, measured plan and ready handoff records. Quik / engine lead | Technical targets, implementation, execution safety, launcher verification and test evidence. Catalog maintainer | IDs, sources, revision links, district/atlas/production status and publication. Change impact: a moved parcel reopens affected access, views and connections; silhouette changes reopen design/shell checks; material changes reopen the affected visual/sample checks; scene additions reopen relevant spatial/interior scope. Avoid restarting unaffected approved work. START A DISTRICT DESIGN SESSION PROTOCOLS / DISTRICT | D01 R02 | 18 Start a district design session Use this entry sequence before commissioning the first new image. It is suitable for tonight's design work and for every later district. Prepare | Record 01 / Resolve the source set | District ID/name; approved board and island crop; latest decisions; atlas version; selected game edition. 02 / Extract requirements | All linked locations; selected scenes/subspaces; routes; kits; open issues; required interactions. 03 / Establish boundaries | Approved geography and neighboring endpoints; frame status; known scale/geometry questions. 04 / Describe identity | Mood, culture, signature forms/materials, vegetation, signs, public space and excluded directions. 05 / Specify modernization | Preserve/upgrade/avoid; selected era; observable behaviors and visual treatment versus implementation. 06 / Plan the reference run | Master → aerial/orbits → player height → topography → kit → scoped building packs. 07 / Review the master | Use the brief and atlas requirements for Gate A. Record the exact accepted version before extending the image set. Copy-ready design-session prompt Design district [ID/name] using protocol D01 R02. Start by listing the controlling sources and extracting its atlas locations, selected scenes, rooms, routes, AK kits and open questions. Preserve approved geography and existing accepted identity decisions. Keep proposed placements explicit. Prepare a district brief and modernization brief for [era]. Explain architecture, public realm, culture, lighting, materials and selected adaptive/control behavior. List unresolved questions with owners. Plan the master card and reference shot list. Produce the master first; extend the references from its recorded approval. Then develop the authored layout and measured exports, ground/edge studies, asset reuse catalog and selected R03 building handoffs. Keep image intent separate from measured geometry. Return source files, IDs, requirements, dependencies and checks needed for the engine handoff. CROWN KEY: THE PRODUCTION REFERENCE PROTOCOLS / DISTRICT | D01 R02 | 19 Crown Key: the production reference Crown Key supplies the worked reference for coverage and handoff. Its development evolved through several generations; its reference library is ahead of the audited engine building state. Layer | Verified evidence / replication lesson Layout development | 29 Sep: traced 42-building concept, then authored v0.1 with 14 footprints. 30 Sep: enlarged v0.2 with 47 footprints. Preserve generations and select a baseline. Atlas contribution | L18 council and L19 diplomacy programs, scenes, access, room needs and kit links help scope selected interiors. Exact placements remain proposed. District look | V3 master plus 13 context renders cover location close-ups and aerial/orbits. Retain full images and ID tags. Shared architecture | 13 building families / 25 variants plus 6 structure modules on global-ID cards. Placement instances remain separate. Crown Landmark exterior | EXT R06: 12 numbered views, 4 detail extracts, roof/footprint plan and scale card. Shell acceptance remains separate. Crown Landmark interior | INT R02: 25 individual views, 4 room masters, plans, 81 room and 102 door records. Landmark depth is scoped, not universal. Engine revision | 13 Oct e2e610a removes 47 building meshes and other structures; marina/infrastructure remain. Historic renders do not establish the current map state. Release/navigation | District hub, reference page, production registry and archive connect the records. Refresh their version and availability independently. Open Crown Key tasks: reconcile the frame/scale metadata and legacy-to-global placement mapping; review the landmark shell/parcel; verify final room views; repair topography publication availability; resolve artwork-era caption conflicts through creator decisions. Only completed protocol applications should become future case studies. The current manual contains no other district implementation example or endorsement. Evidence: S02 - Crown Key hub data and archive inventory (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/CrownKey/data.json) / S03 - Crown Key design render register (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/references/references.json) / S04 - Global asset family and variant lookup (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/catalog/Legacy_Label_Lookup.json) / S05 - Crown Landmark EXT R06 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/EXT/R06/README.md) / S06 - Crown Landmark INT R02 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/INT/R02/README.md) / S09 - Brickell development history (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/docs/PROGRESS.md) / S13 - Current V2.1 story-location atlas (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/the-island/development/atlas/atlas.json) REPEAT ACROSS ALL 21 DISTRICTS PROTOCOLS / DISTRICT | D01 R02 | 20 Repeat across all 21 districts Use one sequence for every district. The atlas counts below are location associations, not building or interior quotas. Zero associations still requires an intentional look, layout, traversal and release scope. ID | District | Atlas | Start 01 | Atlantis | 3 | Link approved board; run stages 01-12 02 | Crown Key | 2 | Link approved board; run stages 01-12 03 | The Grove | 4 | Link approved board; run stages 01-12 04 | South Beach | 0 | Link approved board; run stages 01-12 05 | Harbor View | 1 | Link approved board; run stages 01-12 06 | The Commons | 0 | Link approved board; run stages 01-12 07 | Pinetree | 1 | Link approved board; run stages 01-12 08 | North Ridge | 10 | Link approved board; run stages 01-12 09 | West Point | 1 | Link approved board; run stages 01-12 10 | Edgeview | 2 | Link approved board; run stages 01-12 11 | Port of Atlantis | 3 | Link approved board; run stages 01-12 12 | Bayview | 0 | Link approved board; run stages 01-12 13 | Paradise Key | 0 | Link approved board; run stages 01-12 14 | East Hills | 0 | Link approved board; run stages 01-12 15 | Channel District | 0 | Link approved board; run stages 01-12 16 | South Point | 0 | Link approved board; run stages 01-12 17 | Verdant Isle | 0 | Link approved board; run stages 01-12 18 | Whisper Keys | 0 | Link approved board; run stages 01-12 19 | Ocean View | 1 | Link approved board; run stages 01-12 20 | Sunset Bay | 4 | Link approved board; run stages 01-12 21 | Genesis Campus | 9 | Link approved board; run stages 01-12 Existing approved boards carry forward; link their exact source revisions. This tracker records the new workflow's evidence without revoking past creative approvals or inventing engine acceptance. Share infrastructure and suitable asset kits across districts. Keep each district's architecture, cultural program, terrain and level of playable depth explicit. Evidence: S01 - Current creator decisions (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/docs/current-decisions.md) / S13 - Current V2.1 story-location atlas (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/the-island/development/atlas/atlas.json) PROTOCOL LIBRARY: BRAND AND PUBLICATION PROTOCOLS / DISTRICT | D01 R02 | 21 Protocol library: brand and publication The revised manual establishes a visual and content system for the planned protocol library. Website construction and deployment follow this document pass. Planned route | Purpose /protocols/ | Branded index: District is the first protocol. Future Characters and other categories appear when content is ready. /districtprotocols/ | Direct entry to District D01: version, stage navigation, atlas, modernization, reference coverage, launcher readiness and downloads. Existing project routes | Link /CrownKey/, /CrownKey/reference/, /the-island/development/atlas/, /production/, /assets/ and /launcher/. Keep paths compatible. Visual system Token | Use #04080C / #0D1118 | Deep night background and restrained panels. #F3EAD8 / #E9C785 | Ivory reading text and gold hierarchy / accepted reference emphasis. #2FE6D8 / #FF2E9A | Lagoon links/stage markers and sparse pink attention accents. Project wordmark + actual art | Existing Lost Souls wordmark and Crown Key reference imagery. Label design versus engine evidence. Type hierarchy | Editorial serif titles, readable sans body, mono labels. Site families: Bodoni Moda / Instrument Sans / Martian Mono; embedded PDF equivalents. The future site should present one step at a time with a persistent stage index, clear inputs/outputs/checks, searchable terms and accessible downloads. On mobile, use readable stacked content. Motion should be restrained and respect reduced-motion preferences. Publish the same protocol revision as the PDF and handoff kit. Display source date, revision, status and change notes. Keep launcher execution in the verified local companion; a website link is navigation, not a proof of execution. Evidence: S19 - Crown Key hub brand palette (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/crownkey/style.css) / S20 - Lost Souls site wordmark (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/img/wordmark.png) SOURCES, SCOPE AND REVISION NOTES PROTOCOLS / DISTRICT | D01 R02 | 22 Sources, scope and revision notes R02 adds the full step sequence, explicit atlas extraction/mapping, modernization, build conformance, launcher proof requirements and universe branding. It removes the prior next-district pilot/example material. Current audit facts retain their pinned source revisions. Audit scope: complete recursive trees and relevant recent history for main c4562c4 and unreal-island-archipelago e2e610a; current supplied Crown Key district/building/layout/topography references. The archive lists 849 files and 183 previews; 63 previews were retrieved and visually reviewed, 120 larger preview bytes were unavailable. Live URL access and a fresh Unreal run were unavailable. Launcher execution has not been verified. S01 Current creator decisions (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/docs/current-decisions.md) S02 Crown Key hub data and archive inventory (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/CrownKey/data.json) S03 Crown Key design render register (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/references/references.json) S04 Global asset family and variant lookup (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/districts/D02-CrownKey/catalog/Legacy_Label_Lookup.json) S05 Crown Landmark EXT R06 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/EXT/R06/README.md) S06 Crown Landmark INT R02 navigation/status (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/assets/buildings/PI-BLD-0001-V01/INT/R02/README.md) S07 Building Protocol R03 (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/production/protocols/R03/Paradise_Island_Building_Asset_Protocol_R03.txt) S08 Reference-page catalog and availability (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/CrownKey/reference/catalog.json) S09 Brickell development history (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/docs/PROGRESS.md) S10 District 3 engine handoff (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/docs/DISTRICT3.md) S11 West region rebuild and corrections (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/docs/WEST2_REBUILD.md) S12 Brickell layout v0.2 (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/data/districts/brickell_layout_v02.json) S13 Current V2.1 story-location atlas (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/the-island/development/atlas/atlas.json) S14 Asset archive scope and refresh process (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lsassets/README.md) S15 21-district album review metadata (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/maps/paradise-islands/district-albums/v2-review/README.md) S16 Unreal branch agent instructions (https://github.com/215GrandAve/lost-souls/blob/e2e610a90038ef080663320cb7fc00ba4aaa8426/AGENTS.md) S17 Crown Key page build and publishing rules (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/crownkey/README.md) S18 Launcher + District Kit build plan v2 (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/launcher/plan-v2.md) S19 Crown Key hub brand palette (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/crownkey/style.css) S20 Lost Souls site wordmark (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/lostsouls-world/dist/img/wordmark.png) S21 Crown Key atlas integration builder (https://github.com/215GrandAve/lost-souls/blob/c4562c41bb1452729a9bab616e4a4c0318681e5c/web/crownkey/build.mjs) The source register includes historical district docs used by the earlier audit. Their inclusion is provenance, not a protocol-compliant case study. Full paths/commits and image coverage are in audit/. This handoff provides planning templates; it does not implement district importers, validators, a launcher or a live site.