# Building Asset Protocol R05 PI-PROT-BUILDING · 15 October 2026 · current workflow ## What this release does R05 retains the measurable size contract, developer collections, reusable shells, placement records and current engine evidence introduced after the R03 workflow. It does not alter issued Crown Landmark EXT R06 / INT R02 artwork or approve their proposed dimensions. The complete normative text is `CONSOLIDATED.txt`: this release plus the preserved previous releases and R03 baseline, with R05 taking precedence where they differ. The PDF/DOCX are this release guide; the handoff ZIP includes the baseline and working templates. The stable protocol identity is PI-PROT-BUILDING. Revision R05 is separate from identity. Building IDs, pack revisions and district placements have separate meanings; a protocol revision does not renumber assets. R05 records the creator's Vice Villas name and the authorized production website. R04 remains an archived release. The inherited baseline is preserved; this guide controls current naming and publication rules. ## 1. Brief and reuse before more images Record global asset ID, geometry variant, intended use/era, district context, enterability, developer collection, base shell/revision, interior kit and appearance preset. Keep named source revisions and approval status. Decide whether an existing family fits before creating a new one. Relentless Development is the cutting-edge collection; Vice Villas emphasizes garden neighborhoods; Tidemark Estates emphasizes coastal hospitality. A developer label does not establish story ownership. Cosmetic changes can reuse a reviewed shell. Changes to footprint, core, openings, silhouette or accessible layout need an explicit geometry variant or shell revision. Keep component and actor scale at 1 unless a reviewed exception is recorded. ## 2. References and authority Preserve the controlling master, front/rear/left/right, roof/top, useful elevated views, entrance and defining details. Existing references may cover multiple questions. Keep each image's role, source revision, priority and discrepancy record. Aerials describe design and context; they cannot independently calibrate physical dimensions. Resolve contradictions by naming the controlling view and correcting or deferring the conflicting one. Do not average incompatible silhouettes or move the placed city to fit an interior window background. Preserve global IDs and original file provenance. A camera change or finish variation alone is not a geometry variant. ## 3. Dimension contract before final shell acceptance Supply `BUILDING_DIMENSIONS.json` alongside the asset brief. Record units, width/depth/height, foundation and tower extents, podium levels, floor elevations, floor-to-floor heights, usable clear heights, exterior wall thickness, core/shaft dimensions, roof/crown elevations, entrance clear opening and structural intrusions. Every number has status, source and approver. Unknown values remain null with an owner and resolution task; they are not filled by guesswork. Measured plans require scale, dimensions, north/front convention, level IDs, section cuts and shell revision. Deliver ground/roof plans, each distinct playable floor and a typical-floor plan plus an instance list for repeats. Include at least the sections needed to resolve vertical circulation, floor heights, atria, taper and terraces. Register door, window, room and component schedules. Room dimensions mean usable space after walls, structure and furniture. Record character capsule, camera envelope, furniture clearance, door swing, passage width, stair behavior and lift cab/landing clearance for the chosen gameplay. Test a furnished sample; a visually large room may play small. Do not impose an invented universal room size on every building. ## 4. Shell gate Build a measured shell before accepting interior fit. Test the envelope, floor/core continuity, openings, structure, routes and selected room footprints against the proposed dimensions. Quik provides measured engine/model evidence; the layout/model author supplies candidate drawings; Legend reviews visual intent and accepts the selected scale. Concept approval allows modeling. Shell approval establishes the spatial baseline. Engine acceptance requires its own collision, performance and runtime tests. Interior design may continue against clearly labeled proposed dimensions; final placement and fit remain pending until reviewed. A shell change identifies every affected room, view, window, route and kit instance. ## 5. Interior scope: keep R03's A-E tiers | Tier | Scope | Perspective planning allowance | |---|---|---| | A | Exterior only | 0 interior images | | B | Small enterable space | 2-4 per distinct space | | C | Reusable interior kit | 4-6 per kit | | D | Gameplay building | 6-10 per building | | E | Major story landmark | 10-16 initially per building | These are planning ranges, not quotas or caps. Plans, sections and schedules are outside the perspective-image count. Coverage of actual rooms and routes controls acceptance. A repeated floor references one kit and a level instance list; cosmetic changes do not demand fresh full packs. Every accessible area needs plan/schedule coverage even when it reuses imagery. Separate room identity from image numbering. Use level/room IDs, asset ID, placement ID and shell revision together. Select a short primary build list; keep supporting references indexed. Window backgrounds remain neutral or explicitly provisional until derived from the placed model and actual room/camera position. ## 6. Story-to-space mapping Map current scene/era evidence to PI-LOC, requirement, parcel/placement, global asset, level/room and engine test. Preserve proposed assignments. Atlas image pixels are target zones, not surveyed building coordinates. The Crown Key planning register accounts for every catalog building; only L18/L19 currently establish Crown Key story-space requirements, and their Crown Landmark assignment remains proposed. Creator-authorized planning pages and Black Vault sessions are published separately on the production desk. Keep idea/assignment status visible. Public protocol downloads contain workflow and empty templates; they do not include Vault sessions or grant permission to publish unrelated restricted content. ## 7. Handoff and acceptance Include README/primary build list, asset brief, dimensions, shell source/revision, image index, plans/sections, room/door/window/component schedules, kit and appearance references, story crosswalk where authorized, unresolved decisions, change log, and a SHA-256 manifest. Verify the ZIP and all listed files. A template bundle is not a building model. In the actual project, verify import units, actor/component scale, pivot, orientation, materials, collision, walkability, stairs/doors/lifts, sightlines, lighting, LOD/HLOD, navigation and performance. Record the engine version, commit, map, machine, settings and evidence. Review the complete building in its district and retain its reusable source. Compare a fresh checkout against the issued manifest. District-wide scale changes require a reviewed migration and connection/route/interior impact list. No one resizes an island or room silently. Launcher support is required by the district workflow but remains unverified until a clean-machine run demonstrates it. ## Release contents and authority The handoff contains this guide, consolidated text, unchanged R03 baseline, updated brief/shot-list/crosswalk/checklist, dimensions and reuse templates, scale reconciliation sheet and manifest. It contains no model, district geometry, image library or verified launcher. Use `production/protocols/current.json` to resolve the current family/revision. Historical R02/R03/R04 releases remain intact. ## 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 --- # Building Asset Protocol R04 PI-PROT-BUILDING · 15 October 2026 · current workflow ## What this release does R04 adds a measurable size contract, developer collections, reusable shells, placement records and current engine evidence to the R03 workflow. It does not alter issued Crown Landmark EXT R06 / INT R02 artwork or approve their proposed dimensions. The complete normative text is `CONSOLIDATED.txt`: this release plus the unchanged R03 baseline, with R04 taking precedence where they differ. The PDF/DOCX are this release guide; the handoff ZIP includes the baseline and working templates. The stable protocol identity is PI-PROT-BUILDING. Revision R04 is separate from identity. Building IDs, pack revisions and district placements have separate meanings; a protocol revision does not renumber assets. ## 1. Brief and reuse before more images Record global asset ID, geometry variant, intended use/era, district context, enterability, developer collection, base shell/revision, interior kit and appearance preset. Keep named source revisions and approval status. Decide whether an existing family fits before creating a new one. Relentless Development is the cutting-edge collection; Canopy Works emphasizes garden neighborhoods; Tidemark Estates emphasizes coastal hospitality. A developer label does not establish story ownership. Cosmetic changes can reuse a reviewed shell. Changes to footprint, core, openings, silhouette or accessible layout need an explicit geometry variant or shell revision. Keep component and actor scale at 1 unless a reviewed exception is recorded. ## 2. References and authority Preserve the controlling master, front/rear/left/right, roof/top, useful elevated views, entrance and defining details. Existing references may cover multiple questions. Keep each image's role, source revision, priority and discrepancy record. Aerials describe design and context; they cannot independently calibrate physical dimensions. Resolve contradictions by naming the controlling view and correcting or deferring the conflicting one. Do not average incompatible silhouettes or move the placed city to fit an interior window background. Preserve global IDs and original file provenance. A camera change or finish variation alone is not a geometry variant. ## 3. Dimension contract before final shell acceptance Supply `BUILDING_DIMENSIONS.json` alongside the asset brief. Record units, width/depth/height, foundation and tower extents, podium levels, floor elevations, floor-to-floor heights, usable clear heights, exterior wall thickness, core/shaft dimensions, roof/crown elevations, entrance clear opening and structural intrusions. Every number has status, source and approver. Unknown values remain null with an owner and resolution task; they are not filled by guesswork. Measured plans require scale, dimensions, north/front convention, level IDs, section cuts and shell revision. Deliver ground/roof plans, each distinct playable floor and a typical-floor plan plus an instance list for repeats. Include at least the sections needed to resolve vertical circulation, floor heights, atria, taper and terraces. Register door, window, room and component schedules. Room dimensions mean usable space after walls, structure and furniture. Record character capsule, camera envelope, furniture clearance, door swing, passage width, stair behavior and lift cab/landing clearance for the chosen gameplay. Test a furnished sample; a visually large room may play small. Do not impose an invented universal room size on every building. ## 4. Shell gate Build a measured shell before accepting interior fit. Test the envelope, floor/core continuity, openings, structure, routes and selected room footprints against the proposed dimensions. Quik provides measured engine/model evidence; the layout/model author supplies candidate drawings; Legend reviews visual intent and accepts the selected scale. Concept approval allows modeling. Shell approval establishes the spatial baseline. Engine acceptance requires its own collision, performance and runtime tests. Interior design may continue against clearly labeled proposed dimensions; final placement and fit remain pending until reviewed. A shell change identifies every affected room, view, window, route and kit instance. ## 5. Interior scope: keep R03's A-E tiers | Tier | Scope | Perspective planning allowance | |---|---|---| | A | Exterior only | 0 interior images | | B | Small enterable space | 2-4 per distinct space | | C | Reusable interior kit | 4-6 per kit | | D | Gameplay building | 6-10 per building | | E | Major story landmark | 10-16 initially per building | These are planning ranges, not quotas or caps. Plans, sections and schedules are outside the perspective-image count. Coverage of actual rooms and routes controls acceptance. A repeated floor references one kit and a level instance list; cosmetic changes do not demand fresh full packs. Every accessible area needs plan/schedule coverage even when it reuses imagery. Separate room identity from image numbering. Use level/room IDs, asset ID, placement ID and shell revision together. Select a short primary build list; keep supporting references indexed. Window backgrounds remain neutral or explicitly provisional until derived from the placed model and actual room/camera position. ## 6. Story-to-space mapping Map current scene/era evidence to PI-LOC, requirement, parcel/placement, global asset, level/room and engine test. Preserve proposed assignments. Atlas image pixels are target zones, not surveyed building coordinates. The Crown Key planning register accounts for every catalog building; only L18/L19 currently establish Crown Key story-space requirements, and their Crown Landmark assignment remains proposed. Keep story-bearing plans in the private repo under existing spoiler rules. Public protocol downloads contain workflow and empty templates, not Black Vault sessions or future-story answers. ## 7. Handoff and acceptance Include README/primary build list, asset brief, dimensions, shell source/revision, image index, plans/sections, room/door/window/component schedules, kit and appearance references, story crosswalk where authorized, unresolved decisions, change log, and a SHA-256 manifest. Verify the ZIP and all listed files. A template bundle is not a building model. In the actual project, verify import units, actor/component scale, pivot, orientation, materials, collision, walkability, stairs/doors/lifts, sightlines, lighting, LOD/HLOD, navigation and performance. Record the engine version, commit, map, machine, settings and evidence. Review the complete building in its district and retain its reusable source. Compare a fresh checkout against the issued manifest. District-wide scale changes require a reviewed migration and connection/route/interior impact list. No one resizes an island or room silently. Launcher support is required by the district workflow but remains unverified until a clean-machine run demonstrates it. ## Release contents and authority The handoff contains this guide, consolidated text, unchanged R03 baseline, updated brief/shot-list/crosswalk/checklist, dimensions and reuse templates, scale reconciliation sheet and manifest. It contains no model, district geometry, image library or verified launcher. Use `production/protocols/current.json` to resolve the current family/revision. Historical R02/R03 releases remain intact. --- INCORPORATED HISTORICAL BASELINE The release guide above controls any conflict. Historical dates, page numbers and aliases below are retained for provenance. Paradise Island Building Asset Production Protocol Revision R03 | 13 October 2026 | For Legend and Quik Use this protocol to create reusable buildings for the project. Each asset moves from an approved exterior design to a basic 3D shell, then to interiors that fit that shell. Deliver a coherent building that Quik can model, reuse and review in the game. R03 scales interior references to playable use and reusable kits, with no per-building image quota. Production sequence Asset brief -> exterior reference pack -> shell and scale review -> interior reference pack where needed -> detailed model -> in game review. We establish design targets from the master image, story needs and district parcel. Asa does not need to supply existing geometry. Quik tests those targets in a simple blockout; all definitive geometry views then come from that same model. Responsibilities Owner | Responsibility Legend | Approves appearance, story use, important rooms and changes to the design baseline. Reference author | Produces the brief, consistent visual direction, view index, explicit reference priorities and correction log. Quik | Consolidates the design into one model, checks scale and access, and records modeling and engine requirements. Project constraints Preserve approved island streets, coastline and district layout. Building infrastructure may change within those constraints. Assets are shared across districts; each placement has its own district instance ID. Approval points Approve the design direction before expanding views, the shell before fixing interior layouts, and the assembled model before release. Routine camera exports and packaging checks do not need fresh creative approval. A silhouette, room layout or scale change does. Naming and reference authority Use one stable global asset ID throughout the exterior, interior and model work. Number families globally within each asset type. District names and placement IDs describe instances, not new asset families. Part | Meaning | Example PI | Paradise Island; I is a letter | PI BLD or STR | Building or structure and infrastructure module | BLD 0001 | Four digit family number within its type | 0001 V01 | Deliberate geometry variant | V02 for a compact alternative EXT or INT | Reference scope | INT R01 | Pack revision within its scope | EXT R05 and INT R01 may coexist 01 and descriptor | Stable shot number and actual view | 01_Front B01 and descriptor | Overview board index | B02_Elevations_Corrected Package example: PI-BLD-0001-V01_BuildingName_EXT_R05.zip Image example: PI-BLD-0001-V01_BuildingName_EXT_R05_01_Front.png Placement example: D02-B001 references PI-BLD-0001-V01. A repeated placement reuses the asset; a new camera or file revision does not create a new variant. Revision rules Increase R## for additions, corrections or repackaging. Keep a shot number tied to its role once issued. Append new roles rather than silently reordering an approved set. A role change needs an index entry explaining what was replaced. Avoid Final2 or Latest filenames. Label every image as perspective, oblique, overhead or orthographic according to the actual view. Reserve orthographic for a verified camera projection. Reference image floors and perspective do not establish metric dimensions. Resolve conflicting references Choose one controlling master and one primary image per camera or detail role. The brief states which file controls silhouette, rear, sides, roof and entrance. Mark alternatives as secondary or superseded. Quik follows the stated priorities and logs any remaining conflict before adding detail. Legacy labels stay in a lookup. Preserved source boards may retain embedded older revisions, but their source revision and authority must be stated in the index. The current package revision does not claim that every source image was authored in that revision. Exterior reference coverage Use these twelve roles as the default for new hero buildings. Coverage matters more than count. Simpler assets may omit irrelevant roles with a reason in the index; complex designs may need additional views. An elevated perspective does not satisfy the Top role. Shot | Descriptor | What Quik needs to see 01 | Front | Full height front silhouette and entrance 02 | Rear | Full height rear facade and rear access 03 | Left | Side profile showing depth and podium 04 | Right | Opposite profile and any asymmetric features 05 | Top | Straight down roof and footprint reference 06 | FrontElevated | Tower, roof and podium relationship 07 | RearElevated | Rear massing and terraces 08 | ThreeQuarter | Overall form and depth 09 | SignatureDetail | Crown or asset specific feature 10 | EntranceDetail | Doors, canopy and human scale 11 | GroundEdgeDetail | Podium, terrace, basin or base connection 12 | FacadeDetail | Panel rhythm, glazing, structural joints and materials Camera and image requirements Show the complete building in the core views with unclipped crown and base. Use a neutral background and lighting that reveals form. Keep the same materials, podium tiers, rib arrangement and intended floor rhythm. Identify front by the main entrance; define left and right in the asset brief from a plan orientation. Use the approved master in each design request. Correct the conflicting view rather than regenerating the entire pack. Maintain a reference view without trees, boats, cars or surrounding buildings. Terraces and planters remain core architecture; their planting is separate. Provide important closeups as individual files at their available source resolution. Boards help browsing and must not be the only source of a modeling detail. Record native resolution; do not present an enlarged panel as newly resolved detail. Structures and reusable modules Adapt the roles for bridges, docks and seawalls: include deck and underside, support or foundation, joints, connection ends and repeating module dimensions. Use roof and interior roles only when they apply to the asset. Scale and shell review Before detailed modeling, the asset brief records the intended dimensions and a status for every field: proposed, approved, modeled or measured. The design team can author a baseline; a numerical claim becomes measured only after checking the model. Field | Required record Bounds | Total height to highest tip and footprint width and depth in metres Levels | Podium heights, occupied floor count, floor spacing and roof or crown zone Access | Main and service entrances, door clearance and intended player routes Use | Exterior only, selected rooms enterable or fully enterable Placement | District instance ID, parcel reference and intended entrance direction Signature | Crown, ribs, terraces, basins and other features that define this variant Build one shell Quik builds the tower, podium, crown, structural ribs, entrance and footprint as one coherent blockout. Test the height and width together against the parcel. Resolve floor spacing and access before committing interiors. Scale changes must preserve the intended proportions or be recorded as deliberate design changes. Export front, rear, left, right, top and a three quarter view from that same shell. Include metric bounds, camera orientation and level heights. These renders become the geometry reference for subsequent detail work. Perspective concepts remain useful for materials and design intent. Review observable features Compare crown position and tips, tower to podium proportions, terrace count, rib feet, entrance locations, roof organization and floor levels. Camera tilt can foreshorten a tall tower. A changed podium ratio, missing rib or changed floor rhythm requires a design correction. Record the shell file and revision, approved dimensions and any accepted departures from the concepts. Any shell change that affects an approved interior needs an interior impact check. Keep material and decorative changes separate from geometry decisions. What approval allows An approved exterior concept pack lets modeling begin. An approved shell fixes the spatial baseline for interior work. A completed reference pack does not by itself establish collision, performance, UV quality or successful engine import; those are checked on the model. Interior scope and reference coverage Produce enough references to explain each distinct playable space and its connections. Add an image when it resolves a modeling, gameplay or story question. Reuse approved room kits wherever practical. Image ranges guide planning; they are neither minimum quotas nor hard caps. Choose an interior scope in the asset brief, separately from enterability. A small enterable shop and a fully enterable office can share a reusable kit; a major landmark may expose only selected rooms. The size or height of the building does not determine its image budget. Scope | Typical use | Perspective guidance | Coverage to deliver A Exterior only | Inaccessible buildings and background shells | 0 | Exterior entry treatment and recorded enterability; no INT pack B Small enterable space | Single shop, booth or compact room | 2-4 per space | Controlling main view, useful second angle, access and simple plan C Reusable interior kit | Apartment, office, shop, lobby or corridor repeated across placements | 4-6 per kit | Representative rooms, connections, materials and reusable layout D Gameplay building | Several distinct playable rooms and interactions | 6-10 per building | Playable rooms, connecting routes, interaction clearances and access E Major story landmark | Several signature rooms and complex scene requirements | 10-16 initially per building | Principal rooms, useful reverse angles, circulation and selected details Counts refer to unique perspective references. Overview boards and copies of masters do not add unique views. Plans, sections, schedules and diagrams are technical references outside these ranges. A selected material or fixture closeup can replace a redundant perspective; record its purpose in the shot list. Set scope before expanding views List the distinct playable rooms, gameplay or scene requirements, entry and exit routes, and reusable kits before requesting images. Record the chosen tier, planned unique perspective count and the reason for each proposed shot. Small packs can combine related purposes in one clear image. Add views only where a real question remains unresolved; explain expansion beyond the guidance in the brief. Complete coverage is the test for handoff. A pack with fewer images can pass when all selected spaces, routes and modeling questions are explained. Reaching a numerical target cannot compensate for a conflicting room, missing door or unclear layout. Reusable interior kits Author a kit once, with an approved layout, dimensions, modules and material/component schedule. Link each repeated room or floor to that kit and revision. Vary finishes, furniture and dressing where the shell permits it. Each building still records its own entrance, vertical core, connection to the kit and any placement-specific changes. Fully enterable assets need plan or schedule coverage for every accessible area. Repeated floors may reference one approved typical-floor plan plus an instance list; they do not need separate image sets. A changed door, room geometry, accessible route or shell opening requires a documented layout variant. A finish or camera change alone does not create a new building geometry variant. Select roles by need The roles below are a menu, not a mandatory twelve-image checklist. In the shot-list template, select only roles needed for the chosen scope, then state whether each role is supplied, covered by another view or kit, deferred, or not applicable. An unresolved selected role remains visible as open work. Role | Select when it explains LobbyWide or MainRoomWide | The controlling arrival or principal room and its circulation LobbyReverse or RoomReverse | A second angle resolves doors, furniture, windows or a blind side EntranceIn or EntranceOut | The transition between exterior and interior is not already clear VerticalCore | Lifts or stairs connect the selected playable levels TypicalCorridor | Corridors and repeated door modules need a reference TypicalRoom | An occupied room establishes an approved reusable kit SignatureRoom | A distinct story or gameplay space needs its own controlling design CeilingLighting | Ceiling form or fixture placement needs a separate view MaterialDetail | A finish, joint, door or furnishing needs modeling detail Technical references Every enterable pack supplies a simple dimensioned plan, declared units/orientation, room or kit IDs, access connections and a room schedule appropriate to its scope. A small space can use one annotated plan and a compact schedule. Label author-proposed dimensions distinctly from model measurements. Add sections where atriums, stairs, split levels, ceiling structure or other vertical relationships need explanation. A flat single room does not require a section without a specific need. Provide an access diagram when public, controlled and service routes would otherwise be ambiguous. Reused material/component schedules can be linked by kit ID and revision rather than duplicated. Tie rooms to the shell Define level IDs such as L00 and room IDs such as L00-RM001, separate from image numbers. Store room identity, controlling reference and the shell revision in the index. Where several rooms repeat a shot role, include the room ID in the filename to keep the view identifiable. Example: PI-BLD-0001-V01_BuildingName_INT_R01_L00-RM001_01_LobbyWide.png Keep windows, doors, terrace access, ceiling heights and vertical core positions compatible with the exterior. Reverse views must depict the same room. Plans and model exports control spatial arrangement; generated room perspectives communicate appearance. When no reviewed shell is available, issue an explicit proposed layout for shell review. Final spatial approval follows that review. Record each important room's purpose, occupants, story source and placement status. A proposed story location remains proposed until Legend approves it. Include service or staff access where it affects play or a scene. Furniture and decorative planting should be separately reusable objects where practical. Exterior views through interior windows Use the approved city/district design and the building's intended placement, orientation and room elevation when developing views. Ground-level inland rooms show forecourts, planting, streets and adjacent buildings. Higher rooms may see rooftops, neighboring towers and distant water where the site allows. Nearby room cameras should preserve the same neighborhood, with credible parallax and occlusion. Record window backgrounds as neutral temporary daylight, location-aware concept, or verified model view. A neutral temporary background permits interior design and modeling to proceed before sightlines are resolved. It does not specify frosted glass, remove a window, approve a skyline or change the city design. Track final background integration separately from interior layout review. For verified views, record the placed site model revision, room level, camera position/direction and exported view. Without that evidence, do not label a concept panorama as measured or verified. Correct visible backgrounds without redesigning the room when possible. Primary and supporting references Provide one controlling design for each distinct important room or approved kit and a short primary build list in READ_FIRST. Primary views explain the spaces and their connections. Supporting views show details or additional angles; alternatives and superseded views carry explicit status. The list has no minimum count. Existing large landmark packs may retain their full reference set while a curated primary set guides the first build. A set of about 10-12 primary views can be useful for a complex landmark, but it is a planning suggestion rather than a requirement. Larger coverage is not the default for other buildings. Updating this protocol does not change issued images, geometry, placements or approval status. Packaging and model delivery Reference package structure Use only the folders needed for the issued scope. A larger INT pack may separate plans, components and handoff documents into 04_PlansAndSections, 05_MaterialsAndComponents and 06_Handoff. Small packs may keep the compact structure below, with every file indexed. Overview boards are optional when they do not help navigation. 01_Master contains the controlling design. 02_OverviewBoards contains browsing sheets. 03_IndividualViews contains the indexed source views. 04_Handoff contains the asset brief, modeling brief, naming guide, image index, manifest and change log. Alternatives may be kept in 05_Archive with explicit secondary status. Each index record includes filename, shot role, room or kit and level if relevant, camera type, reference priority, coverage status, source revision and notes. Interior records also state window-background status when relevant. READ_FIRST names the primary build list and any remaining sightline work. The manifest records asset ID, scope, revision and image hashes. Name the controlling files explicitly in READ_FIRST. Reference handoff checklist [ ] Asset ID, scope and revision agree across filenames and documents. [ ] One controlling master and explicit priorities resolve conflicting angles. [ ] Each selected role is supplied or has an explicit reuse, combined-coverage, deferral or not-applicable record; unresolved work is not marked complete. [ ] Scale fields and enterability are recorded with clear approval status. [ ] Core architecture is visible without vegetation or scene clutter. [ ] ZIP opens, all files exist, image hashes match and the change log is accurate. [ ] Approved image numbering is retained; added or replaced roles are explained. Quik model delivery Deliver an editable source scene with named objects, declared units, orientation and origin; agreed exports; texture and material files; and definitive camera renders. Keep the asset ID stable. Separate reusable architecture, foliage, props and placement specific dressing. Record export settings and source application versions. For game release, check player scale, walkable access, stairs and doors, collision, shading, UVs and texture paths in the actual project. Quik sets and records the asset's detail, texture and performance targets for the intended platform. Review the assembled asset in its district and retain a reusable source version. Use explicit release status: concept handoff, shell approved, interior approved, or engine ready. Record who approved what and when. Log missing work so an exterior pack is not mistaken for a finished game asset. Existing reference packs Keep issued asset revisions and their existing design examples intact. A protocol revision changes the workflow for new work; it does not reissue an asset pack. Consult the current asset brief and controlling references for that building's dimensions, materials and approval status. Start each next building Copy the R03 asset brief and shot list templates. Select the interior scope and reuse plan before expanding interior views. Assign the next family ID or existing family variant. Set the name, use, district context, controlling master and proposed scale. Produce the required exterior roles, review the shell, then develop the relevant interiors. Record reusable variants once and link later district placements to them. Files to keep with project sources Keep this protocol DOCX and PDF with project sources, along with the four global ID cards, current asset handoffs and the location atlas. Use the separate EXT and INT role lists in this protocol; the older guide with twelve mixed exterior and interior references is superseded. Repository home: production/protocols/R03/. Current revision pointers live in production/protocols/README.md and production/registry/catalog.json. Basis and revision R03 supersedes R02 for new work. It adds five interior scope levels with planning ranges rather than quotas, reusable-kit coverage, separate technical drawings, primary/supporting reference priorities and explicit window-background status. Asset brief, shot list and checklist templates carry these rules. R03 retains the exterior workflow, global naming, scale review, reference authority and engine checks. R02 remains intact as the source protocol for earlier handoffs and its existing design examples. Story and location evidence remains in the existing project sources; this document supplies production rules. Link story locations to building assets Read the existing location dossier, scene links, minimum spaces, source evidence and open decisions before designing a story-dependent interior. Check current creator decisions and story revisions against dated snapshots. Keep source versions intact and record newer decisions in a working crosswalk. Keep identifier systems distinct An atlas location ID identifies a story location. A PI-BLD-####-V## ID identifies a reusable building design. A district placement ID identifies an instance. A level-room ID identifies a room within its shell. An atlas planning-kit ID does not replace a building or room ID. Link these identifiers in the crosswalk without merging their meanings. Map locations before designing interiors Record the location ID, reusable asset ID, placement ID and shell revision together. Map pins in a concept image do not establish parcel or engine coordinates. Assign proposed level and room IDs for shell review, then reconcile them against the reviewed shell. Preserve required adjacency, independent access, service routes and window/terrace connections. Track the story requirement, placement approval and build status separately. A story event may be established while its building assignment remains proposed. Record a specific assignment only after the creator decision and shell-fit review. Refresh coverage when story revisions add, remove or move a scene.