{
  "schema_version": 1,
  "status": "DRAFT_PRODUCTION_PREP",
  "assets": [
    {
      "asset_id": "PI-BLD-0001-V01",
      "purpose": "Coordinate a bounded review of the issued exterior/interior packs and C01 candidate, preserving all source artwork and room layout while preparing explicit shell-fit decisions.",
      "scope_basis": "P0; proposed Tier E. EXT R06 and INT R02 are issued; the register marks the shell pending and the L18/L19 host assignment proposed. C01 is an editable review candidate with an independent fit audit, not a design, shell, placement, or engine approval.",
      "components": [
        {
          "name": "R06 exterior target envelope",
          "role": "The C01 audit reports its candidate matches R06 authored 240 m height and 160 × 120 m foundation targets; the targets remain proposal basis, not accepted placement scale.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_DesignTargets.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/MODEL_MEASUREMENTS.json"
          ],
          "open_questions": [
            "Does Legend accept the C01 interpretation beyond the authored R06 targets, especially the unprovided upper-envelope transitions?"
          ]
        },
        {
          "name": "Six principal ribs and podium",
          "role": "R06 identifies the master/front and 02_Rear as controlling visual authorities; C01 contains editable interpretations of these features.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_DesignTargets.json",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/01_Master/PI-BLD-0001-V01_CrownLandmark_EXT_R06_Master_Tall.jpeg",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/03_IndividualViews/PI-BLD-0001-V01_CrownLandmark_EXT_R06_01_Front.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/03_IndividualViews/PI-BLD-0001-V01_CrownLandmark_EXT_R06_02_Rear.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL_SPEC.json"
          ],
          "open_questions": [
            "Which qualitative deviations in C01 ribs, podium fascia, crown, and rear treatment need a revised candidate before any shell review?"
          ]
        },
        {
          "name": "L25 council and L26 diplomacy planning zones",
          "role": "The existing INT R02 layout and schedules are preserved; the independent C01 audit flags three L26 source rectangles against its stated proposed perimeter allowance.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L25_Fit_Review.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L26_Fit_Review.png"
          ],
          "open_questions": [
            "Resolve the private office, secured records, and private vestibule fit finding jointly with envelope/recess/structure review; do not silently shrink or move the source rooms."
          ]
        },
        {
          "name": "Arrival, core, atrium and circulation",
          "role": "INT R02 describes lobby, atrium/gallery, lifts, stairs, service access, and separate diplomacy access as a design proposal; C01 is not a complete entrance/core assembly.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL_SPEC.json"
          ],
          "open_questions": [
            "What selected rooms/routes must be included in the first shell-fit review, and which remain deferred?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Freeze source baseline",
          "action": "Record hashes/revisions for R06, INT R02, the C01 GLB/OBJ and its fit report; leave C01, source rooms, approvals and hold status unchanged.",
          "gate": "Review must identify the exact unchanged candidate and source inputs before interpreting fit.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_DesignTargets.json",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/PI-BLD-0001-V01_CrownLandmark_SHELL_C01.glb",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/PI-BLD-0001-V01_CrownLandmark_SHELL_C01.obj",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md"
          ]
        },
        {
          "step": 2,
          "title": "Compare C01 with R06 authority",
          "action": "Use named front, rear and overhead views from the same C01 mesh. Treat artwork comparison as qualitative because camera calibration is not established; use R06 authored targets only for the dimensions explicitly supplied there.",
          "gate": "Report target checks separately from visual-design acceptance; 02_Rear remains the rear authority.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_DesignTargets.json",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/01_Master/PI-BLD-0001-V01_CrownLandmark_EXT_R06_Master_Tall.jpeg",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/03_IndividualViews/PI-BLD-0001-V01_CrownLandmark_EXT_R06_01_Front.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/03_IndividualViews/PI-BLD-0001-V01_CrownLandmark_EXT_R06_02_Rear.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_13_RoofFootprintPlan.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_front.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_rear.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_top.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json"
          ]
        },
        {
          "step": 3,
          "title": "Reconcile INT R02 fit findings",
          "action": "Review the reported L25/L26 planning-zone containment and exact L26 flags against the unchanged INT R02 source, then list envelope/recess/structure and layout options without editing either source.",
          "gate": "Legend selects any revision direction; a limited rectangle audit is not furnished, rib, access, or engine acceptance.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L25_Fit_Review.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L26_Fit_Review.png"
          ]
        },
        {
          "step": 4,
          "title": "Prepare a scoped revision decision",
          "action": "If requested, write a change-impact list for envelope, room zones, access, sightlines, and reusable components; do not implement changes under this prep record.",
          "gate": "No changes to C01, room layout, design approvals, or construction hold without explicit review.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json"
          ]
        },
        {
          "step": 5,
          "title": "Return review evidence",
          "action": "Return source hashes, named-view comparisons, audit limitations, unresolved decisions and the exact candidate revision. Keep placement, UE import, collision, and runtime claims open.",
          "gate": "Separate creator visual review, shell acceptance, placement and engine acceptance.",
          "source_paths": [
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/MODEL_MEASUREMENTS.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL_SPEC.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "C01 front against R06 master/front",
          "purpose": "Review broad silhouette and entrance qualitatively from the same candidate mesh; do not claim pixel-calibrated dimensional agreement.",
          "source_paths": [
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_front.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/01_Master/PI-BLD-0001-V01_CrownLandmark_EXT_R06_Master_Tall.jpeg",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/03_IndividualViews/PI-BLD-0001-V01_CrownLandmark_EXT_R06_01_Front.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json"
          ]
        },
        {
          "view": "C01 rear against R06 02_Rear",
          "purpose": "Check the controlling crossed-gold rear treatment and record differences without substituting the secondary B02 comparison.",
          "source_paths": [
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_rear.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/03_IndividualViews/PI-BLD-0001-V01_CrownLandmark_EXT_R06_02_Rear.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt"
          ]
        },
        {
          "view": "True overhead footprint",
          "purpose": "Compare C01 top view to the R06 roof-footprint schematic; distinguish the authored target from unapproved shell acceptance.",
          "source_paths": [
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_top.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_13_RoofFootprintPlan.png",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/05_ScaleAndPlan/PI-BLD-0001-V01_CrownLandmark_EXT_R06_DesignTargets.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json"
          ]
        },
        {
          "view": "L25 and L26 source-zone fit review",
          "purpose": "Inspect existing overlays and the exact audit flags, keeping the interior source rectangles unchanged pending a decision.",
          "source_paths": [
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L25_Fit_Review.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L26_Fit_Review.png",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json"
          ]
        },
        {
          "view": "C01 elevated/side views",
          "purpose": "Review candidate crown, rib, podium and envelope interpretations before deciding whether a new candidate revision is needed.",
          "source_paths": [
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/VIEWS/C01_elevated.png",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL_SPEC.json",
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LANDMARK",
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-PROPS"
      ],
      "dependencies": [],
      "decision_queue": [
        {
          "question": "Should C01 remain a review candidate as modeled, or should an explicitly scoped new exterior candidate address named qualitative mismatches?",
          "owner": "Legend",
          "resolution_evidence": "Recorded creator review against R06 master/front/02_Rear and documented change-impact list; C01 itself is not approval.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/EXT/R06/04_Handoff/MODELING_BRIEF.txt",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/README.md",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json"
          ]
        },
        {
          "question": "How should the three flagged L26 planning rectangles be reconciled with the candidate shell/recess/structure while preserving the INT R02 layout until a decision?",
          "owner": "Legend with layout author; Quik supplies candidate measurements",
          "resolution_evidence": "Joint review of unchanged INT R02 layout, C01 section evidence, and an approved revision instruction if any.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/SHELL-C01/MODEL/FIT_REVIEW.json",
            "production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/SPATIAL_REVIEW/L26_Fit_Review.png"
          ]
        },
        {
          "question": "Which selected-room routes and rooms are required in the first shell-fit sample, including independent L26 access?",
          "owner": "Legend",
          "resolution_evidence": "A scoped enterability decision linked to the existing room/access plan and a reviewed route/clearance plan.",
          "source_paths": [
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/MODELING_BRIEF.txt",
            "production/assets/buildings/PI-BLD-0001-V01/INT/R02/06_Handoff/EditableLayout/INTERIOR_LAYOUT.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "What exact project branch/map and UE checks will establish later engine evidence for this candidate?",
          "owner": "Quik",
          "resolution_evidence": "Current-project report naming branch/commit, engine version, map, measured import state, and separately scoped runtime tests.",
          "source_paths": [
            "production/protocols/building/R05/GUIDE.md",
            "production/world/SCALE_REGISTER.md",
            "docs/current-decisions.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Hash and inspect the existing C01 candidate, R06 source, INT R02 layout, and independent fit audit without modifying any of them.",
          "Prepare a review packet for the existing L25/L26 overlays and named C01/R06 views, with fit limits and open decisions clearly separated."
        ],
        "requires_decision": [
          "Legend direction on C01 visual deviations and any new candidate revision.",
          "A jointly reviewed response to the L26 perimeter findings; no room-layout or C01 edits under this prep record.",
          "Quik project/branch/map evidence and any engine execution plan; this prep does not lift the construction hold."
        ],
        "return_evidence": [
          "Exact model/source hashes and rerun fit-audit output if independently reproduced.",
          "Annotated R06/C01 comparisons and L25/L26 fit issue list that preserves the audit limitations.",
          "Any approved follow-up instruction as a separate revision/task; no shell, placement, or engine-ready claim."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0002-V01",
      "purpose": "Prepare a two-core complex brief that tests the paired-lobby and skybridge relationships before choosing interior scope or shell dimensions.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register gives optional everyday-life use and no named story assignment.",
      "components": [
        {
          "name": "Paired lobbies",
          "role": "The proposed program explicitly calls for one lobby at each block.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "How do each lobby and the shared circulation connect to the two cores?"
          ]
        },
        {
          "name": "Two service cores",
          "role": "The register specifically calls for measuring two cores; their sizes and positions are unset.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What separation, core continuity, lift/stair content, and service interfaces are required?"
          ]
        },
        {
          "name": "Skybridge and garden",
          "role": "The register describes a skybridge garden only if selected playable.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Is the bridge garden enterable, a visual connector, or deferred? What level/egress relationship must be tested?"
          ]
        },
        {
          "name": "Typical office/residential floor",
          "role": "Reusable office/residential floor is proposed; the balance and precise kit boundary are undecided.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which one typical floor is the first candidate kit, and which of its clearances must be proven?"
          ]
        },
        {
          "name": "Asymmetric blade towers and open-gap bridge",
          "role": "The notes describe two non-mirror towers with an open gap and a bridge; the card reads one slim arched level while the location render notes describe a two-level arrangement with planted upper deck. Card/render massing, podium and planting also conflict. These are concept observations, not dimensions.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0002-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0002-V01/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Which side is front and which source controls the different tower profiles?",
            "Is the bridge one level or two, and how does it meet the two cores?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Compare visual conflicts",
          "action": "Use the notes and index to keep the card/render alternatives explicit: non-mirror silhouettes, bridge level count, podium continuity and planting boundary. Do not average conflicting concepts.",
          "gate": "Legend selects reference authority and resolves bridge/podium alternatives before geometry interpretation.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0002-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0002-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Map core and bridge interfaces",
          "action": "Prepare a dimensionless relationship sketch for both cores, bridge endpoints, public routes and service routes.",
          "gate": "No bridge level, span, or clearance is locked without authored dimensions and review.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 3,
          "title": "Choose candidate enterability",
          "action": "Separate lobby, typical office/residential floor and optional skybridge garden scopes; identify only the representative sample needed for review.",
          "gate": "Tier C remains proposed until Legend selects scope.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Prepare floor and section requirements",
          "action": "List the plans/sections needed to evaluate two-core continuity, shared circulation, bridge access and egress.",
          "gate": "Plan dimensions, floor levels and access evidence must be sourced before blockout acceptance.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return the fit question set",
          "action": "Deliver open interface questions and a proposed shell/kit review sequence for the designer and Quik.",
          "gate": "No shell or placement acceptance from concept prep alone.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md",
            "production/world/SCALE_REGISTER.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Open-gap paired-tower elevation",
          "purpose": "Show the two different tower profiles, sweeping blade fins and bridge gap from the selected front; notes flag orientation and bridge-level ambiguity.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0002-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0002-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Core and bridge relationship plan",
          "purpose": "Locate the two cores, bridge endpoints, lobby entries and candidate public/service paths.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Bridge/core vertical section",
          "purpose": "Expose candidate bridge level, headroom, attachment, shared circulation and egress questions without assuming values.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Lobby and typical-floor plan",
          "purpose": "Test whether the proposed reusable office/residential floor can connect to both lobby/core systems.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-OFFICE",
        "CK-KIT-RESIDENCE",
        "CK-KIT-SERVICE"
      ],
      "dependencies": [],
      "decision_queue": [
        {
          "question": "Which side is front and which tower/podium profile controls where the card and render disagree?",
          "owner": "Legend",
          "resolution_evidence": "Named visual authority plus annotated elevation; preserve the bridge-level and planting conflicts until resolved.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0002-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0002-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "What measured relationship should control the two cores, bridge levels, and bridge clearances?",
          "owner": "Legend accepts design scale; design/layout author supplies candidate dimensions",
          "resolution_evidence": "Dimensioned plan and section with named source, status, owner, and approval; no pixel-derived values.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/world/SCALE_REGISTER.md"
          ]
        },
        {
          "question": "Which typical office/residential kit is the first candidate for this family?",
          "owner": "Legend",
          "resolution_evidence": "An asset brief selecting program and reuse scope, plus a representative plan.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "question": "How will shared circulation and bridge egress be demonstrated?",
          "owner": "Quik with layout author",
          "resolution_evidence": "Reviewed access route plus later measured blockout/engine evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Review notes for the asymmetric blade towers and record the one-versus-two-level bridge and podium/planting conflicts.",
          "Create a source-backed reference/variant question list and a non-metric blockout checklist for review."
        ],
        "requires_decision": [
          "Creator review of controlling visual references, proposed enterability, and any candidate dimensions before shell acceptance or placement."
        ],
        "return_evidence": [
          "Source paths and revisions, annotated plan/section checklist, unresolved questions with owners, and the exact model/source revision if any candidate blockout is later authorized."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0003-V01",
      "purpose": "Prepare a stepped-residential shell and kit brief that tests terrace usability, core continuity, and planting interfaces without assigning dimensions from the concept.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Proposed optional world-life program, with no named story assignment.",
      "components": [
        {
          "name": "Stepped slab sequence",
          "role": "The register identifies stepped slabs as the form-specific coordination issue.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which slab/terrace transitions define this variant and which are occupied versus visual?"
          ]
        },
        {
          "name": "Core continuity",
          "role": "A continuing core through the stepped envelope is explicitly called out.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "How does the core remain continuous across the proposed level changes?"
          ]
        },
        {
          "name": "Terrace dwelling kit",
          "role": "A typical terrace dwelling kit is proposed; its fit to each edge condition is unverified.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which representative unit plan and balcony/terrace condition should anchor the kit?"
          ]
        },
        {
          "name": "Waterproofing and planting zones",
          "role": "The register requires these interfaces to be resolved, but supplies no technical details.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Where are planted zones separated from playable unit and circulation areas?"
          ]
        },
        {
          "name": "Rounded tower and wavy stepped terraces",
          "role": "Notes describe a rounded glass tower beside a lower stepped mass with soft S-curved slab edges. The visible terrace count is a card observation, not a floor schedule; front, smaller glass-volume connection, plan shape and roof use remain open.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Are the tower and stepped mass connected, and which side is front?",
            "What authored terrace sequence and tower plan shape control?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Record the curved terrace signature",
          "action": "Use the notes/index to preserve the soft S-edge terrace expression and lopsided tower/block relationship; do not convert visible bands into a floor schedule.",
          "gate": "No dimensions or floor count are inferred from the concept card.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Draw stepped envelope and core section",
          "action": "Prepare a section diagram of slab steps, core continuity, dwelling access, and planting/waterproofing interfaces.",
          "gate": "All floor heights, terrace depths and core dimensions remain proposed/null until sourced and reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Plan one representative dwelling kit",
          "action": "Map usable room zones, doors, furniture clearance and exterior terrace access for a selected typical unit.",
          "gate": "Do not assume one scaled unit fits every step or edge.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Review terrace and planting separation",
          "action": "Mark candidate circulation, shared terrace, planting and service interfaces separately.",
          "gate": "Legend selects shared/playable terrace scope before detailed modeling.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return a blockout evidence plan",
          "action": "List the named views and measurements required to test core continuity, terrace usability and candidate kit reuse.",
          "gate": "No final shell/scale status until measured and reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Tower and stepped-block three-quarter view",
          "purpose": "Show the rounded glass tower, lower wavy terrace mass and smaller glass volume; the notes identify only a single concept view.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Core and slab section",
          "purpose": "Expose floor-to-floor relations, terrace transitions, core continuity and planting interfaces.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Typical dwelling/terrace plan",
          "purpose": "Show clear usable room areas, openings and access to the selected terrace condition.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Shared-terrace access view",
          "purpose": "Check whether the selected shared terrace connects to public circulation without crossing private units.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-RESIDENCE",
        "CK-KIT-GARDEN",
        "CK-KIT-PROPS"
      ],
      "dependencies": [],
      "decision_queue": [
        {
          "question": "Are the rounded tower and stepped terrace block connected or separate, and which side is front?",
          "owner": "Legend",
          "resolution_evidence": "Creator-selected orientation and annotated massing plan/elevation.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0003-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0003-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "What slab/terrace geometry and core path are supported by the controlling source references?",
          "owner": "Design/layout author; Legend approves visual intent",
          "resolution_evidence": "Dimensioned section with source revision and explicit proposed/approved status.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which unit plan is reusable, and where does the stepped shell require a distinct layout?",
          "owner": "Legend with layout author",
          "resolution_evidence": "Representative furnished unit plan plus a family fit comparison.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "How are planted/wet zones separated from terrace access and the building shell?",
          "owner": "Design/layout author; Quik tests later integration",
          "resolution_evidence": "Annotated section/plan and subsequent collision/waterproofing interface review.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Use the card notes to preserve the wavy curved terrace edges and contrast with the rounded tower; list unseen side and roof questions.",
          "Create a source-backed reference/variant question list and a non-metric blockout checklist for review."
        ],
        "requires_decision": [
          "Creator review of controlling visual references, proposed enterability, and any candidate dimensions before shell acceptance or placement."
        ],
        "return_evidence": [
          "Source paths and revisions, annotated plan/section checklist, unresolved questions with owners, and the exact model/source revision if any candidate blockout is later authorized."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0004-V01",
      "purpose": "Prepare the Twist Tall variant-specific envelope/core/facade questions and a single typical rotated-floor kit candidate.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register says Tall and Compact are distinct envelopes; proposed program is lobby plus one typical rotated-floor office/residential kit.",
      "components": [
        {
          "name": "Rotated floor expression",
          "role": "Tall variant: document the rotation sequence and stable-core relationship across the taller expression; do not infer a floor count from the name. The register requires the floor rotation to be documented.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What is the rotation sequence and which reference controls each transition?"
          ]
        },
        {
          "name": "Stable service core",
          "role": "The register requires a stable core to be documented alongside the rotation.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Does the core remain fixed through the sequence, and how do stairs/lifts/services connect?"
          ]
        },
        {
          "name": "Facade-to-room fit",
          "role": "The register identifies facade-to-room fit as a family-specific test.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "How do windows/openings align with usable room zones on rotated floors?"
          ]
        },
        {
          "name": "Usable corner space",
          "role": "Corner-space usability is explicitly called out; no room dimensions are supplied.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which corner conditions remain usable after structure, facade and furniture are accounted for?"
          ]
        },
        {
          "name": "Typical office/residential floor",
          "role": "A single reusable typical-floor kit is proposed for review, not approved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which use and room arrangement anchors the first kit?"
          ]
        },
        {
          "name": "Tall spiral ribbons and cylindrical glass body",
          "role": "Notes describe a slender cylindrical glass body wrapped by cream spiral ribbons. The card reads as braided/crossing ribbons while the location render reads as parallel decks; ribbon depth, support, front and terminations remain unresolved.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Are ribbons crossing or parallel, and which reference controls?",
            "Are they walkable balconies, and where do they start/end?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Keep braid/deck conflict open",
          "action": "Use the notes/index to document the crossing-card versus parallel-deck-render readings; prepare a path/termination diagram without choosing geometry.",
          "gate": "Legend review is required before ribbon geometry or walkability is modeled.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Document rotation and core",
          "action": "Create a floor-to-floor relationship diagram for rotation, core continuity, and facade orientation.",
          "gate": "Rotation values and levels remain unset until authored source evidence supports them.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Fit one typical room kit",
          "action": "Place only a schematic office/residential kit against the candidate rotated floor and flag facade/corner conflicts.",
          "gate": "Usable clear dimensions require a sourced plan and reviewed character/camera assumptions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Prepare variant-specific shell views",
          "action": "Request matching front, top/typical-floor and vertical-section views for this asset and its sibling.",
          "gate": "Use views to compare geometry; do not infer measurements from perspective.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return open decisions",
          "action": "List envelope, rotation, stable-core and interior-kit questions with evidence needed to resolve each.",
          "gate": "No shell or room kit is accepted by this prep record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Twist Tall front/three-quarter view",
          "purpose": "Resolve the card’s braided ribbon reading against the render’s parallel spiral-deck reading from selected authority.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical-floor plan from above",
          "purpose": "Show the rotated facade, core, room zones and corner usability.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Vertical core/facade section",
          "purpose": "Test whether the core remains stable while the floor/facade expression changes.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Typical-room/player-height view",
          "purpose": "Reveal usable corners, opening placement and camera sightline after the room kit is selected.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-TWIST",
        "CK-KIT-OFFICE",
        "CK-KIT-RESIDENCE"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0004-V02",
          "relationship": "Sibling-family comparison: register requires Tall and Compact to be treated as distinct envelopes; this is not a scale or geometry authority.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V02/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Are the Tall ribbons a crossing braid or stacked spiral decks, and are they walkable around the tower?",
          "owner": "Legend",
          "resolution_evidence": "Named reference authority, annotated ribbon path, and selected balcony enterability.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "Which typical office/residential layout is selected, and which corner zones are usable?",
          "owner": "Legend",
          "resolution_evidence": "Representative furnished plan with door, structure, furniture, camera and access checks.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which differences from PI-BLD-0004-V02 require distinct geometry or a separate shell revision?",
          "owner": "Legend",
          "resolution_evidence": "Side-by-side reference comparison and an explicit reuse/geometry-change record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "What levels, core vertical connections and openings must be verified before shell approval?",
          "owner": "Quik with design/layout author",
          "resolution_evidence": "Measured shell and core/clearance evidence from the actual candidate, reviewed against the accepted dimension contract.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Preserve the card/render difference between crossing ribbons and parallel deck-like ribbons; list support, termination and walkability questions.",
          "Prepare a schematic core/facade/typical-floor coordination sheet without reusing one sibling as the other’s scale."
        ],
        "requires_decision": [
          "Legend selection of controlling references and the variant geometry differences to preserve.",
          "Reviewed rotation/core/floor schedule and chosen interior scope before producing a dimensioned shell or room kit."
        ],
        "return_evidence": [
          "Variant comparison showing Twist Tall separately from PI-BLD-0004-V02, with source provenance.",
          "Dimensioned typical-floor and section proposal with statuses, open items, and candidate camera/player clearance tests."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0004-V02",
      "purpose": "Prepare the Twist Compact variant-specific envelope/core/facade questions and a single typical rotated-floor kit candidate.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register says Tall and Compact are distinct envelopes; proposed program is lobby plus one typical rotated-floor office/residential kit.",
      "components": [
        {
          "name": "Rotated floor expression",
          "role": "Compact variant: document the rotation sequence and stable-core relationship for this distinct envelope; do not scale down the Tall shell by name. The register requires the floor rotation to be documented.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What is the rotation sequence and which reference controls each transition?"
          ]
        },
        {
          "name": "Stable service core",
          "role": "The register requires a stable core to be documented alongside the rotation.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Does the core remain fixed through the sequence, and how do stairs/lifts/services connect?"
          ]
        },
        {
          "name": "Facade-to-room fit",
          "role": "The register identifies facade-to-room fit as a family-specific test.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "How do windows/openings align with usable room zones on rotated floors?"
          ]
        },
        {
          "name": "Usable corner space",
          "role": "Corner-space usability is explicitly called out; no room dimensions are supplied.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which corner conditions remain usable after structure, facade and furniture are accounted for?"
          ]
        },
        {
          "name": "Typical office/residential floor",
          "role": "A single reusable typical-floor kit is proposed for review, not approved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which use and room arrangement anchors the first kit?"
          ]
        },
        {
          "name": "Compact broad-ribbon drum and podium wing",
          "role": "Notes describe a squat rounded glass drum with broader spiral ribbons and an oversized curved podium wing. This is a distinct family expression, not a scale-derived copy; front, podium plan, ribbon pattern and roof use remain unresolved.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V02/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Which side is front and what is the podium-wing plan?",
            "How does the ribbon pattern differ from Twist Tall?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Preserve the Compact expression",
          "action": "Use the notes to distinguish the broad-ribbon drum and oversized podium wing from Twist Tall; keep all relative proportions non-metric.",
          "gate": "Do not scale the Tall shell to create Compact.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Document rotation and core",
          "action": "Create a floor-to-floor relationship diagram for rotation, core continuity, and facade orientation.",
          "gate": "Rotation values and levels remain unset until authored source evidence supports them.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Fit one typical room kit",
          "action": "Place only a schematic office/residential kit against the candidate rotated floor and flag facade/corner conflicts.",
          "gate": "Usable clear dimensions require a sourced plan and reviewed character/camera assumptions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Prepare variant-specific shell views",
          "action": "Request matching front, top/typical-floor and vertical-section views for this asset and its sibling.",
          "gate": "Use views to compare geometry; do not infer measurements from perspective.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return open decisions",
          "action": "List envelope, rotation, stable-core and interior-kit questions with evidence needed to resolve each.",
          "gate": "No shell or room kit is accepted by this prep record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Twist Compact front/three-quarter view",
          "purpose": "Show the squat drum, broad ribbons and podium wing; notes identify orientation and podium plan as open questions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical-floor plan from above",
          "purpose": "Show the rotated facade, core, room zones and corner usability.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Vertical core/facade section",
          "purpose": "Test whether the core remains stable while the floor/facade expression changes.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Typical-room/player-height view",
          "purpose": "Reveal usable corners, opening placement and camera sightline after the room kit is selected.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-TWIST",
        "CK-KIT-OFFICE",
        "CK-KIT-RESIDENCE"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0004-V01",
          "relationship": "Sibling-family comparison: register requires Tall and Compact to be treated as distinct envelopes; this is not a scale or geometry authority.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V01/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "What ribbon pattern and podium-wing geometry distinguish Compact from Twist Tall?",
          "owner": "Legend",
          "resolution_evidence": "Side-by-side concept comparison and selected authority; no scale-copy.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0004-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0004-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "Which typical office/residential layout is selected, and which corner zones are usable?",
          "owner": "Legend",
          "resolution_evidence": "Representative furnished plan with door, structure, furniture, camera and access checks.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which differences from PI-BLD-0004-V01 require distinct geometry or a separate shell revision?",
          "owner": "Legend",
          "resolution_evidence": "Side-by-side reference comparison and an explicit reuse/geometry-change record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "What levels, core vertical connections and openings must be verified before shell approval?",
          "owner": "Quik with design/layout author",
          "resolution_evidence": "Measured shell and core/clearance evidence from the actual candidate, reviewed against the accepted dimension contract.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Compare the broad ribbons and podium wing with Twist Tall; log front, roof and termination questions without assigning proportions.",
          "Prepare a schematic core/facade/typical-floor coordination sheet without reusing one sibling as the other’s scale."
        ],
        "requires_decision": [
          "Legend selection of controlling references and the variant geometry differences to preserve.",
          "Reviewed rotation/core/floor schedule and chosen interior scope before producing a dimensioned shell or room kit."
        ],
        "return_evidence": [
          "Variant comparison showing Twist Compact separately from PI-BLD-0004-V01, with source provenance.",
          "Dimensioned typical-floor and section proposal with statuses, open items, and candidate camera/player clearance tests."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0005-V01",
      "purpose": "Prepare the Garden Canyon open-space/terrace, bridge, shade and dwelling-kit questions before setting an envelope.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register proposes a lobby, garden court and typical dwelling/workspace kit, and requires section review of canyon/terraces, planting voids, bridges, shade and circulation.",
      "components": [
        {
          "name": "Garden court / signature opening",
          "role": "Review the named canyon/opening as this variant’s signature space; the register says to preserve the signature opening.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which portions of the opening remain open through the shell, and which routes cross or frame it?"
          ]
        },
        {
          "name": "Terraces and planting voids",
          "role": "The register calls for a section through terraces and planting voids; geometry is not dimensioned.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "How do planted voids align with occupied floors and accessible terrace edges?"
          ]
        },
        {
          "name": "Bridge and circulation links",
          "role": "Bridges and circulation are named coordination issues, not approved connections.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which bridges are required for access, and where do they meet the core and open space?"
          ]
        },
        {
          "name": "Lobby and core",
          "role": "A lobby is proposed; the register does not define its location or the core arrangement.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What entrance, vertical circulation and service path supports the selected kit?"
          ]
        },
        {
          "name": "Typical dwelling/workspace kit",
          "role": "A reusable dwelling/workspace kit is proposed, with fit to the open-space edge still unresolved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which representative room kit and facade/opening condition should be tested?"
          ]
        },
        {
          "name": "Slab tower with open canyon slot",
          "role": "Notes describe a straight slab tower with a deep front slot, two glass wings and curved-rail balconies along the slot’s back wall. Slot sky/roof/ground termination and balcony arrangement remain unresolved.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V01/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Is the slot open to sky, roofed or bridged, and does it reach ground?",
            "Do balconies stay on the back wall or alternate?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Preserve the slot as the signature",
          "action": "Use the notes/index to section the straight slab and open slot with back-wall balconies; do not fill the opening with planting or structure without direction.",
          "gate": "Slot termination and balcony access remain decisions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Draw the open-space section",
          "action": "Diagram the signature opening, terraces, planting voids, shade surfaces and candidate bridge routes.",
          "gate": "Keep opening/terrace dimensions unset until they have a source and owner.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Map access and core",
          "action": "Show the candidate lobby, vertical circulation, bridge connections and usable terrace circulation.",
          "gate": "Legend selects which garden/terrace areas are playable or decorative.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Fit a representative room kit",
          "action": "Test a schematic dwelling/workspace plan at the open-space edge and flag conflicts with structure, openings and circulation.",
          "gate": "No repeated unit is accepted until a furnished sample is checked against a measured candidate shell.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return source-backed comparison",
          "action": "Provide the variant comparison, open-space section/view list and unresolved decision queue.",
          "gate": "A family resemblance does not authorize scaled-copy geometry.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Front slot/canyon elevation",
          "purpose": "Show the deep open slot and two wings; notes identify stacked back-wall balconies as must-preserve concept intent.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Section through opening and terraces",
          "purpose": "Reveal open-to-sky/courtyard voids, planting zones, bridges, shade and circulation relationships.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Garden circulation plan",
          "purpose": "Trace lobby/core to bridges, garden court, shared terrace and representative dwelling access.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Typical dwelling/workspace edge view",
          "purpose": "Check room openings and usable room/terrace boundary against the candidate open-space arrangement.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-RESIDENCE",
        "CK-KIT-GARDEN",
        "CK-KIT-PROPS"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0005-V02",
          "relationship": "Sibling-family comparison: both variants share the register coordination checklist, but each needs its own envelope/open-space review.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Is the slot open to sky, roofed or bridged, and how does it terminate at ground?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Selected concept interpretation and a dimensioned section; no card-derived dimensions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "Which bridge/circulation links and core interfaces are necessary to reach the garden court and representative rooms?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Dimensioned access plan and section with all unresolved points assigned.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "How does this variant differ from its sibling in open-space sequence and geometry?",
          "owner": "Legend",
          "resolution_evidence": "Source-backed variant comparison; no scaled-copy assumption.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which dwelling/workspace kit is the first sample, and how will its clear room area be tested?",
          "owner": "Legend; Quik supplies later player/camera evidence",
          "resolution_evidence": "Furnished room plan over a reviewed candidate shell with dimension/status provenance.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Use the notes to preserve the open vertical slot and back-wall balconies; list sky/ground termination and balcony-route options.",
          "List candidate section/plan cuts for opening, bridge, shade, planting and room access."
        ],
        "requires_decision": [
          "Legend direction on the preserved opening and which terraces/garden routes are shared/playable.",
          "A dimensioned envelope/core and selected dwelling/workspace kit before room fit can be accepted."
        ],
        "return_evidence": [
          "Variant-specific plan and section proposal, reference provenance, open items and route diagram.",
          "Later candidate-shell fit views with separate plant, bridge, room and clearance checks."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0005-V02",
      "purpose": "Prepare the Terraced Garden open-space/terrace, bridge, shade and dwelling-kit questions before setting an envelope.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. The register proposes a lobby, garden court and typical dwelling/workspace kit, and requires section review of canyon/terraces, planting voids, bridges, shade and circulation.",
      "components": [
        {
          "name": "Stepped terrace mass",
          "role": "The variant notes describe rectilinear planted terraces narrowing upward above a broad podium. Preserve this stepped mass rather than importing Garden Canyon’s open slot.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Do the terraces step on the unseen sides, and how does the stepped mass meet the broad podium?"
          ]
        },
        {
          "name": "Terraces and planting voids",
          "role": "The register calls for a section through terraces and planting voids; geometry is not dimensioned.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "How do planted voids align with occupied floors and accessible terrace edges?"
          ]
        },
        {
          "name": "Bridge and circulation links",
          "role": "Bridges and circulation are named coordination issues, not approved connections.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which bridges are required for access, and where do they meet the core and open space?"
          ]
        },
        {
          "name": "Lobby and core",
          "role": "A lobby is proposed; the register does not define its location or the core arrangement.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What entrance, vertical circulation and service path supports the selected kit?"
          ]
        },
        {
          "name": "Typical dwelling/workspace kit",
          "role": "A reusable dwelling/workspace kit is proposed, with fit to the open-space edge still unresolved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which representative room kit and facade/opening condition should be tested?"
          ]
        },
        {
          "name": "Stepped terrace pyramid and diagonal blade",
          "role": "Notes describe rectilinear planted terraces narrowing upward, a glass spine and a tall cream diagonal blade with a shorter brace. This differs from Garden Canyon’s open slot; blade endpoints and spine/core relationship remain open.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Where does the blade meet ground, terraces and roof?",
            "Is the glass spine a separate tower or the stepped mass’s core?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Preserve the stepped/blade identity",
          "action": "Use the notes to distinguish the stepped terrace stack and diagonal blade from the Canyon slot; map blade/spine questions without transferring sibling geometry.",
          "gate": "Variant envelopes remain distinct.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Draw the terrace and spine section",
          "action": "Diagram the stepped terrace stack, glass spine, diagonal blade, planting zones and shade. Test which family-level garden or bridge circulation proposals are selected for this variant.",
          "gate": "Terrace, blade and core dimensions stay unset until sourced and reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Map access and core",
          "action": "Show the candidate lobby, vertical circulation, bridge connections and usable terrace circulation.",
          "gate": "Legend selects which garden/terrace areas are playable or decorative.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Fit a representative room kit",
          "action": "Test a schematic dwelling/workspace plan at the open-space edge and flag conflicts with structure, openings and circulation.",
          "gate": "No repeated unit is accepted until a furnished sample is checked against a measured candidate shell.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return source-backed comparison",
          "action": "Provide the variant comparison, open-space section/view list and unresolved decision queue.",
          "gate": "A family resemblance does not authorize scaled-copy geometry.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Stepped mass and diagonal-blade elevation",
          "purpose": "Show the terrace stack, glass spine and diagonal blade; resolve unseen blade foot and roof conditions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Section through terraces, planting and spine",
          "purpose": "Reveal the terrace-to-spine and planting relationships; distinguish any selected garden/bridge routes from the Canyon sibling’s open slot.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Garden circulation plan",
          "purpose": "Trace lobby/core to bridges, garden court, shared terrace and representative dwelling access.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Typical dwelling/workspace edge view",
          "purpose": "Check room openings and usable room/terrace boundary against the candidate open-space arrangement.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-RESIDENCE",
        "CK-KIT-GARDEN",
        "CK-KIT-PROPS"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0005-V01",
          "relationship": "Sibling-family comparison: both variants share the register coordination checklist, but each needs its own envelope/open-space review.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V01/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Where does the diagonal blade land, and how does the glass spine relate to the stepped mass?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Selected concept interpretation and dimensioned plan/section.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0005-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0005-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "Which bridge/circulation links and core interfaces are necessary to reach the garden court and representative rooms?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Dimensioned access plan and section with all unresolved points assigned.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "How does this variant differ from its sibling in open-space sequence and geometry?",
          "owner": "Legend",
          "resolution_evidence": "Source-backed variant comparison; no scaled-copy assumption.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which dwelling/workspace kit is the first sample, and how will its clear room area be tested?",
          "owner": "Legend; Quik supplies later player/camera evidence",
          "resolution_evidence": "Furnished room plan over a reviewed candidate shell with dimension/status provenance.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Compare the stepped/blade concept to the sibling slot concept; list blade, spine and terrace-side questions without assigning levels.",
          "List candidate section/plan cuts for terraces, blade, spine, shade, planting and room access; bridge links remain unselected."
        ],
        "requires_decision": [
          "Legend direction on the stepped terraces, diagonal blade and which garden routes are shared or playable.",
          "A dimensioned envelope/core and selected dwelling/workspace kit before room fit can be accepted."
        ],
        "return_evidence": [
          "Variant-specific plan and section proposal, reference provenance, open items and route diagram.",
          "Later candidate-shell fit views with separate plant, bridge, room and clearance checks."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0006-V01",
      "purpose": "Prepare the Frame Tall frame/core/floor-kit coordination record and identify which shared parts can be tested across the height family.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Register program is lobby, typical office kit and selected shared meeting room; each height variant requires its own exoframe, intrusion, clear-height and service-core check.",
      "components": [
        {
          "name": "Exoframe bay",
          "role": "The register requires the structural bay to be coordinated, but gives no span or module dimensions.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which source reference controls bay rhythm and where does it join slabs/façade?"
          ]
        },
        {
          "name": "Structural intrusions and clear floor",
          "role": "The register calls out intrusions and clear floor height as explicit fit checks.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which structure zones reduce usable room/circulation clearance in this variant?"
          ]
        },
        {
          "name": "Service core",
          "role": "A service core is in the proposed program and must be coordinated with the frame.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What core location/continuity is supported by the controlling references?"
          ]
        },
        {
          "name": "Office / meeting room kit",
          "role": "Typical office and selected shared meeting room are proposed, not selected/approved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which representative meeting space is needed and how does it connect to the core?"
          ]
        },
        {
          "name": "Variant envelope",
          "role": "Check the tall variant’s exoframe/core/clear-floor relationships independently across its proposed stack.",
          "evidence_kind": "proposed_design",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What dimensions distinguish this variant, and which parts are genuinely reusable across siblings?"
          ]
        },
        {
          "name": "Tall taper and crossing exoframe",
          "role": "Notes describe a tapered glass body and large crossing diagonals. The card shows several members while the close render reads as one dominant A; the apparent taper also differs. These remain concept conflicts.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V01/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Which frame layout and faces control?",
            "Is the taper genuine or a perspective effect?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Record A-frame/taper conflicts",
          "action": "Use the notes/index to list the multiple-diagonal versus dominant-A reading and taper question without resolving geometry.",
          "gate": "Legend chooses authority before frame geometry is modeled.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Diagram exoframe and core",
          "action": "Prepare a section/elevation with frame bays, floor lines, core zones and known structural intrusions; leave values blank where no source exists.",
          "gate": "Every numeric value requires a source, status, owner and reviewer.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Check one office/meeting kit",
          "action": "Place a schematic typical office and selected meeting-room zone against the frame/core diagram.",
          "gate": "Clear dimensions and circulation are candidates until the shell is measured and furnished-player reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Compare variant reuse boundaries",
          "action": "Classify candidate repeat parts versus variant-specific frame/envelope/core geometry.",
          "gate": "Do not turn a cosmetic/material reuse candidate into geometry reuse without compatible interfaces.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return variant evidence plan",
          "action": "List each required plan/section and return measurement, route, collision and player-camera evidence needed later.",
          "gate": "No shell or engine acceptance is implied.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Frame Tall front/three-quarter view",
          "purpose": "Show the tapered body and frame pattern against selected authority; notes flag a card/render disagreement.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical floor/core plan",
          "purpose": "Show the office kit, service core and structural intrusions relative to the candidate clear room zone.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Frame/core vertical section",
          "purpose": "Show level relationships, clear-height questions, frame continuity and service-core stack.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Meeting-room sample view",
          "purpose": "Test one selected shared meeting room against the frame and player/camera envelope after scope is chosen.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-OFFICE",
        "CK-KIT-SERVICE",
        "CK-KIT-EXOFRAME",
        "CK-KIT-PROPS"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0006-V02",
          "relationship": "Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md"
          ]
        },
        {
          "asset_id": "PI-BLD-0006-V03",
          "relationship": "Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Which frame pattern controls, and is the glass body actually tapered?",
          "owner": "Legend",
          "resolution_evidence": "Named authority, annotated elevation and candidate plan/section; perspective alone does not resolve taper.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "What clear floor height and structural intrusion zones must the office kit preserve?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Measured section and furnished clear-room plan, followed by candidate-shell fit evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "What is the service-core arrangement and how does it connect to the lobby and typical floors?",
          "owner": "Legend; Quik provides later measured engine evidence",
          "resolution_evidence": "Reviewed core/access plan and shell continuity evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which frame parts can actually be reused across Tall, Mid and Compact without changing geometry?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Side-by-side variant interface comparison and an R05 reuse record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Keep the multiple-diagonal/card versus dominant-A/render and taper conflicts open; request frame-foot, balcony and roof-end sections.",
          "Identify candidate office/meeting kit interfaces and mark the frame, intrusion and clear-height values still missing."
        ],
        "requires_decision": [
          "Legend review of each variant envelope and the proposed shared meeting-room scope.",
          "Approved/sourced frame, core and clear-height dimensions before a shell can be accepted."
        ],
        "return_evidence": [
          "Independent Frame Tall plan/section plus comparison against PI-BLD-0006-V02, PI-BLD-0006-V03 with all source revisions named.",
          "Later shell-fit and player/camera evidence for frame intrusion, clear floor, core continuity and the selected meeting room."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0006-V02",
      "purpose": "Prepare the Frame Mid frame/core/floor-kit coordination record and identify which shared parts can be tested across the height family.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Register program is lobby, typical office kit and selected shared meeting room; each height variant requires its own exoframe, intrusion, clear-height and service-core check.",
      "components": [
        {
          "name": "Exoframe bay",
          "role": "The register requires the structural bay to be coordinated, but gives no span or module dimensions.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which source reference controls bay rhythm and where does it join slabs/façade?"
          ]
        },
        {
          "name": "Structural intrusions and clear floor",
          "role": "The register calls out intrusions and clear floor height as explicit fit checks.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which structure zones reduce usable room/circulation clearance in this variant?"
          ]
        },
        {
          "name": "Service core",
          "role": "A service core is in the proposed program and must be coordinated with the frame.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What core location/continuity is supported by the controlling references?"
          ]
        },
        {
          "name": "Office / meeting room kit",
          "role": "Typical office and selected shared meeting room are proposed, not selected/approved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which representative meeting space is needed and how does it connect to the core?"
          ]
        },
        {
          "name": "Variant envelope",
          "role": "Check the mid variant’s exoframe bay, core and typical-floor relationship as its own envelope.",
          "evidence_kind": "proposed_design",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What dimensions distinguish this variant, and which parts are genuinely reusable across siblings?"
          ]
        },
        {
          "name": "Mid curved/faceted body and dominant A-frame",
          "role": "Notes describe a curved left glass half, faceted right face and dominant A-frame with roof spikes. No location render is listed; plan shape, front, frame feet and roof box remain unresolved.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V02/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Is the left half curved in plan, and what is the overall plan?",
            "Where do A-frame feet land, and what is the roof box?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Resolve Mid silhouette questions",
          "action": "Use the card-only notes to preserve the curved/faceted body and dominant A-frame as hypotheses; request the unseen plan/front and roof relationship.",
          "gate": "No missing face or frame endpoint is invented.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Diagram exoframe and core",
          "action": "Prepare a section/elevation with frame bays, floor lines, core zones and known structural intrusions; leave values blank where no source exists.",
          "gate": "Every numeric value requires a source, status, owner and reviewer.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Check one office/meeting kit",
          "action": "Place a schematic typical office and selected meeting-room zone against the frame/core diagram.",
          "gate": "Clear dimensions and circulation are candidates until the shell is measured and furnished-player reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Compare variant reuse boundaries",
          "action": "Classify candidate repeat parts versus variant-specific frame/envelope/core geometry.",
          "gate": "Do not turn a cosmetic/material reuse candidate into geometry reuse without compatible interfaces.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return variant evidence plan",
          "action": "List each required plan/section and return measurement, route, collision and player-camera evidence needed later.",
          "gate": "No shell or engine acceptance is implied.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Frame Mid front/three-quarter view",
          "purpose": "Show the curved/faceted body and dominant A-frame from creator-selected front.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical floor/core plan",
          "purpose": "Show the office kit, service core and structural intrusions relative to the candidate clear room zone.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Frame/core vertical section",
          "purpose": "Show level relationships, clear-height questions, frame continuity and service-core stack.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Meeting-room sample view",
          "purpose": "Test one selected shared meeting room against the frame and player/camera envelope after scope is chosen.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-OFFICE",
        "CK-KIT-SERVICE",
        "CK-KIT-EXOFRAME",
        "CK-KIT-PROPS"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0006-V01",
          "relationship": "Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md"
          ]
        },
        {
          "asset_id": "PI-BLD-0006-V03",
          "relationship": "Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Is the left body curved in plan, where do frame feet land, and what roof structure sits between the spikes?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Source-backed plan and dimensioned section resolving the card-only questions.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "What clear floor height and structural intrusion zones must the office kit preserve?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Measured section and furnished clear-room plan, followed by candidate-shell fit evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "What is the service-core arrangement and how does it connect to the lobby and typical floors?",
          "owner": "Legend; Quik provides later measured engine evidence",
          "resolution_evidence": "Reviewed core/access plan and shell continuity evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which frame parts can actually be reused across Tall, Mid and Compact without changing geometry?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Side-by-side variant interface comparison and an R05 reuse record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Use the card-only notes to distinguish Mid’s curved/faceted body and dominant A-frame; request plan, feet and roof evidence.",
          "Identify candidate office/meeting kit interfaces and mark the frame, intrusion and clear-height values still missing."
        ],
        "requires_decision": [
          "Legend review of each variant envelope and the proposed shared meeting-room scope.",
          "Approved/sourced frame, core and clear-height dimensions before a shell can be accepted."
        ],
        "return_evidence": [
          "Independent Frame Mid plan/section plus comparison against PI-BLD-0006-V01, PI-BLD-0006-V03 with all source revisions named.",
          "Later shell-fit and player/camera evidence for frame intrusion, clear floor, core continuity and the selected meeting room."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0006-V03",
      "purpose": "Prepare the Frame Compact frame/core/floor-kit coordination record and identify which shared parts can be tested across the height family.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Register program is lobby, typical office kit and selected shared meeting room; each height variant requires its own exoframe, intrusion, clear-height and service-core check.",
      "components": [
        {
          "name": "Exoframe bay",
          "role": "The register requires the structural bay to be coordinated, but gives no span or module dimensions.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which source reference controls bay rhythm and where does it join slabs/façade?"
          ]
        },
        {
          "name": "Structural intrusions and clear floor",
          "role": "The register calls out intrusions and clear floor height as explicit fit checks.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which structure zones reduce usable room/circulation clearance in this variant?"
          ]
        },
        {
          "name": "Service core",
          "role": "A service core is in the proposed program and must be coordinated with the frame.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What core location/continuity is supported by the controlling references?"
          ]
        },
        {
          "name": "Office / meeting room kit",
          "role": "Typical office and selected shared meeting room are proposed, not selected/approved.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which representative meeting space is needed and how does it connect to the core?"
          ]
        },
        {
          "name": "Variant envelope",
          "role": "Check the compact variant’s exoframe intrusions and clear-floor relationship without shrinking another variant.",
          "evidence_kind": "proposed_design",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What dimensions distinguish this variant, and which parts are genuinely reusable across siblings?"
          ]
        },
        {
          "name": "Compact low-wide body and roof-level frame",
          "role": "Notes describe a low wide box with diagonals across its upper face; unlike the taller variants, the frame stays near roof height. The broad podium/pool-or-planter and terrace connection remain open.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V03/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Does the frame rise above the roof?",
            "Is the podium feature water or a planter?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Preserve roof-level frame expression",
          "action": "Use the note/index comparison to distinguish Compact’s low-wide frame from its taller siblings; keep the roof line and podium-water interpretation open.",
          "gate": "Do not extend frame members above roof without source/design direction.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V03/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Diagram exoframe and core",
          "action": "Prepare a section/elevation with frame bays, floor lines, core zones and known structural intrusions; leave values blank where no source exists.",
          "gate": "Every numeric value requires a source, status, owner and reviewer.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Check one office/meeting kit",
          "action": "Place a schematic typical office and selected meeting-room zone against the frame/core diagram.",
          "gate": "Clear dimensions and circulation are candidates until the shell is measured and furnished-player reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Compare variant reuse boundaries",
          "action": "Classify candidate repeat parts versus variant-specific frame/envelope/core geometry.",
          "gate": "Do not turn a cosmetic/material reuse candidate into geometry reuse without compatible interfaces.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return variant evidence plan",
          "action": "List each required plan/section and return measurement, route, collision and player-camera evidence needed later.",
          "gate": "No shell or engine acceptance is implied.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Frame Compact front/three-quarter view",
          "purpose": "Show the low-wide body, upper-face frame and broad podium as distinct from tower-like siblings.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V03/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical floor/core plan",
          "purpose": "Show the office kit, service core and structural intrusions relative to the candidate clear room zone.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Frame/core vertical section",
          "purpose": "Show level relationships, clear-height questions, frame continuity and service-core stack.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Meeting-room sample view",
          "purpose": "Test one selected shared meeting room against the frame and player/camera envelope after scope is chosen.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-OFFICE",
        "CK-KIT-SERVICE",
        "CK-KIT-EXOFRAME",
        "CK-KIT-PROPS"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0006-V01",
          "relationship": "Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V01/VISUAL_NOTES.md"
          ]
        },
        {
          "asset_id": "PI-BLD-0006-V02",
          "relationship": "Sibling-height comparison only; the register requires verifying each height variant and does not authorize scaled copies.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V02/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Does the frame rise above the roof, and is the podium feature a pool or planter?",
          "owner": "Legend",
          "resolution_evidence": "Selected concept interpretation and building/landscape section.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0006-V03/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0006-V03/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "What clear floor height and structural intrusion zones must the office kit preserve?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Measured section and furnished clear-room plan, followed by candidate-shell fit evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "What is the service-core arrangement and how does it connect to the lobby and typical floors?",
          "owner": "Legend; Quik provides later measured engine evidence",
          "resolution_evidence": "Reviewed core/access plan and shell continuity evidence.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which frame parts can actually be reused across Tall, Mid and Compact without changing geometry?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Side-by-side variant interface comparison and an R05 reuse record.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Use notes to preserve the low-wide body and frame near roof height; list pool/planter and terrace-access alternatives.",
          "Identify candidate office/meeting kit interfaces and mark the frame, intrusion and clear-height values still missing."
        ],
        "requires_decision": [
          "Legend review of each variant envelope and the proposed shared meeting-room scope.",
          "Approved/sourced frame, core and clear-height dimensions before a shell can be accepted."
        ],
        "return_evidence": [
          "Independent Frame Compact plan/section plus comparison against PI-BLD-0006-V01, PI-BLD-0006-V02 with all source revisions named.",
          "Later shell-fit and player/camera evidence for frame intrusion, clear floor, core continuity and the selected meeting room."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0013-V01",
      "purpose": "Prepare the Straight Tall envelope, facade-grid, core and typical-floor questions without legacy label or sibling-scale assumptions.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Proposed scope is lobby, typical office/residential floor kit and service core; the register explicitly rejects legacy H/LM mapping by name.",
      "components": [
        {
          "name": "Straight envelope",
          "role": "The register names Tall/Slim as separate variants and requires their envelopes to be established.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What authored evidence distinguishes this envelope from its sibling?"
          ]
        },
        {
          "name": "Facade grid",
          "role": "The facade grid is a specific coordination item; no module size is provided.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What grid controls opening rhythm, room frontage and repeat bay boundaries?"
          ]
        },
        {
          "name": "Service core",
          "role": "Service core is included in the proposed program.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What core location, access route and stack are supported by source plans?"
          ]
        },
        {
          "name": "Typical office/residential floor",
          "role": "A reusable office/residential floor kit is proposed but not yet selected.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which room arrangement and entry/core connection should be used as the first sample?"
          ]
        },
        {
          "name": "Lobby and appearance variation",
          "role": "Lobby is proposed; appearance changes may be separate from geometry only after compatibility review.",
          "evidence_kind": "proposed_design",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which finishes are cosmetic and which openings/core changes require geometry revision?"
          ]
        },
        {
          "name": "Straight Tall shaft and shallow stepped top",
          "role": "Notes describe a plain rectangular glass shaft with corner/face fins, shallow top step and larger-looking podium than Slim. Visible card bands are not a floor count.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V01/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Is the plan square or rectangular?",
            "Are fins structural, and what controls the top?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Preserve the quiet straight-tower expression",
          "action": "Use notes to distinguish Tall’s plain shaft and shallow stepped top from Slim’s upper setback; do not derive scale or floors from visible bands.",
          "gate": "No legacy H/LM mapping by name.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Establish envelope and facade grid",
          "action": "Prepare an annotated elevation/plan showing candidate grid, openings, core and shell boundary.",
          "gate": "Grid/envelope values stay unset until supported by a source and reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Plan typical floor and service core",
          "action": "Identify one reusable office/residential floor candidate and show its service-core connection.",
          "gate": "Room clear dimensions are measured after walls, structure, furniture and access are considered.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Compare sibling geometry and reuse",
          "action": "Compare this variant to its sibling and classify cosmetic versus geometry differences.",
          "gate": "Do not scale one shell to create the other; footprint/core/opening changes require explicit variant/revision review.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return scope and measurement requests",
          "action": "Provide the selected view/plan/section list and unresolved envelope, grid, core and enterability questions.",
          "gate": "No shell approval or placement without measured/reviewed inputs.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Straight Tall elevation",
          "purpose": "Show shaft, facade fins, shallow stepped top and podium relationship from selected front.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical-floor plan",
          "purpose": "Show a representative office/residential kit, core and usable facade frontage.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Core/facade vertical section",
          "purpose": "Expose repeated floor relationship and service-core continuity without assigning a floor count.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Lobby-to-typical-floor route",
          "purpose": "Check entrance, lobby, core and representative room connection once enterability is selected.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-OFFICE",
        "CK-KIT-RESIDENCE",
        "CK-KIT-SERVICE"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0013-V02",
          "relationship": "Sibling-variant comparison only; register requires distinct Tall/Slim envelope and facade-grid definition.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V02/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "What plan shape and top treatment control Tall, and are its fins structural or applied?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "Selected reference authority plus annotated plan/elevation/section.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V01/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V01/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "Which typical office/residential kit and lobby enterability are selected for the first sample?",
          "owner": "Legend",
          "resolution_evidence": "Asset brief scope plus a representative plan and room schedule.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which differences are cosmetic, and which require a geometry variant or shell revision?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "R05 reuse record tied to the actual geometry/opening/core comparison.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "How will legacy H/LM labels be handled without implying identity or scale?",
          "owner": "Legend / catalog owner",
          "resolution_evidence": "Source-backed crosswalk or explicit unresolved status; no name-only mapping.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/districts/D02-CrownKey/planning/README.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Compare the plain Tall shaft/shallow top to Slim’s setback and record front, plan-shape and facade-fin questions.",
          "List facade-grid, opening, core and typical-floor questions plus the first drawing set needed."
        ],
        "requires_decision": [
          "Legend review of controlling references, selected enterability and the variant geometry boundary.",
          "Sourced/reviewed envelope and facade grid before shell dimensions or reusable geometry are locked."
        ],
        "return_evidence": [
          "Variant-specific annotated elevation, floor plan and section with reference provenance and open dimensions.",
          "R05 reuse comparison recording which parts are genuinely shared and which are asset-specific."
        ]
      }
    },
    {
      "asset_id": "PI-BLD-0013-V02",
      "purpose": "Prepare the Straight Slim envelope, facade-grid, core and typical-floor questions without legacy label or sibling-scale assumptions.",
      "scope_basis": "P2; proposed Tier C. Catalog concept only; no dedicated pack, placement, shell revision or engine evidence. Proposed scope is lobby, typical office/residential floor kit and service core; the register explicitly rejects legacy H/LM mapping by name.",
      "components": [
        {
          "name": "Straight envelope",
          "role": "The register names Tall/Slim as separate variants and requires their envelopes to be established.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What authored evidence distinguishes this envelope from its sibling?"
          ]
        },
        {
          "name": "Facade grid",
          "role": "The facade grid is a specific coordination item; no module size is provided.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What grid controls opening rhythm, room frontage and repeat bay boundaries?"
          ]
        },
        {
          "name": "Service core",
          "role": "Service core is included in the proposed program.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "What core location, access route and stack are supported by source plans?"
          ]
        },
        {
          "name": "Typical office/residential floor",
          "role": "A reusable office/residential floor kit is proposed but not yet selected.",
          "evidence_kind": "source_record",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which room arrangement and entry/core connection should be used as the first sample?"
          ]
        },
        {
          "name": "Lobby and appearance variation",
          "role": "Lobby is proposed; appearance changes may be separate from geometry only after compatibility review.",
          "evidence_kind": "proposed_design",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json"
          ],
          "open_questions": [
            "Which finishes are cosmetic and which openings/core changes require geometry revision?"
          ]
        },
        {
          "name": "Straight Slim shaft and upper setback",
          "role": "Notes describe a narrower shaft with a clearer upper setback and compact-looking podium. Exact setback sides, roof element, front and pool/landscape boundary remain unresolved; visible bands are not a floor count.",
          "evidence_kind": "source_notes",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V02/REFERENCE_INDEX.csv"
          ],
          "open_questions": [
            "Which sides set back and by how much?",
            "Is base water building content or landscape?"
          ]
        }
      ],
      "modeling_sequence": [
        {
          "step": 1,
          "title": "Preserve the Slim setback expression",
          "action": "Use notes to distinguish Slim’s upper setback from Tall’s shallow stepped top; do not derive scale or floors from visible bands.",
          "gate": "No legacy H/LM mapping by name.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "step": 2,
          "title": "Establish envelope and facade grid",
          "action": "Prepare an annotated elevation/plan showing candidate grid, openings, core and shell boundary.",
          "gate": "Grid/envelope values stay unset until supported by a source and reviewed.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "step": 3,
          "title": "Plan typical floor and service core",
          "action": "Identify one reusable office/residential floor candidate and show its service-core connection.",
          "gate": "Room clear dimensions are measured after walls, structure, furniture and access are considered.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 4,
          "title": "Compare sibling geometry and reuse",
          "action": "Compare this variant to its sibling and classify cosmetic versus geometry differences.",
          "gate": "Do not scale one shell to create the other; footprint/core/opening changes require explicit variant/revision review.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "step": 5,
          "title": "Return scope and measurement requests",
          "action": "Provide the selected view/plan/section list and unresolved envelope, grid, core and enterability questions.",
          "gate": "No shell approval or placement without measured/reviewed inputs.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "required_views": [
        {
          "view": "Straight Slim elevation and upper-setback section",
          "purpose": "Show the narrow shaft and setback sides from selected authority; resolve roof and podium boundary.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "view": "Typical-floor plan",
          "purpose": "Show a representative office/residential kit, core and usable facade frontage.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json"
          ]
        },
        {
          "view": "Core/facade vertical section",
          "purpose": "Expose repeated floor relationship and service-core continuity without assigning a floor count.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json"
          ]
        },
        {
          "view": "Lobby-to-typical-floor route",
          "purpose": "Check entrance, lobby, core and representative room connection once enterability is selected.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        }
      ],
      "candidate_kit_ids": [
        "CK-KIT-LOBBY",
        "CK-KIT-CORE",
        "CK-KIT-OFFICE",
        "CK-KIT-RESIDENCE",
        "CK-KIT-SERVICE"
      ],
      "dependencies": [
        {
          "asset_id": "PI-BLD-0013-V01",
          "relationship": "Sibling-variant comparison only; register requires distinct Tall/Slim envelope and facade-grid definition.",
          "status": "proposed",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V01/VISUAL_NOTES.md"
          ]
        }
      ],
      "decision_queue": [
        {
          "question": "Which sides have the upper setback, and what roof element controls?",
          "owner": "Legend",
          "resolution_evidence": "Creator-selected authority and annotated section/elevation.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/assets/buildings/PI-BLD-0013-V02/VISUAL_NOTES.md",
            "production/assets/buildings/PI-BLD-0013-V02/REFERENCE_INDEX.csv"
          ]
        },
        {
          "question": "Which typical office/residential kit and lobby enterability are selected for the first sample?",
          "owner": "Legend",
          "resolution_evidence": "Asset brief scope plus a representative plan and room schedule.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "Which differences are cosmetic, and which require a geometry variant or shell revision?",
          "owner": "Legend with design/layout author",
          "resolution_evidence": "R05 reuse record tied to the actual geometry/opening/core comparison.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/protocols/building/R05/GUIDE.md"
          ]
        },
        {
          "question": "How will legacy H/LM labels be handled without implying identity or scale?",
          "owner": "Legend / catalog owner",
          "resolution_evidence": "Source-backed crosswalk or explicit unresolved status; no name-only mapping.",
          "source_paths": [
            "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
            "production/districts/D02-CrownKey/planning/README.md"
          ]
        }
      ],
      "friday_work": {
        "can_prepare": [
          "Compare Slim’s upper setback/compact podium to Tall’s shaft and record exact setback sides and base-water questions.",
          "List facade-grid, opening, core and typical-floor questions plus the first drawing set needed."
        ],
        "requires_decision": [
          "Legend review of controlling references, selected enterability and the variant geometry boundary.",
          "Sourced/reviewed envelope and facade grid before shell dimensions or reusable geometry are locked."
        ],
        "return_evidence": [
          "Variant-specific annotated elevation, floor plan and section with reference provenance and open dimensions.",
          "R05 reuse comparison recording which parts are genuinely shared and which are asset-specific."
        ]
      }
    }
  ]
}
