{
  "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."
    ]
  },
  "schema_version": 1,
  "revision": "R01",
  "date": "2026-10-16",
  "status": "DRAFT_PRODUCTION_PREP",
  "status_notice": "Draft preparation only; not an issued reference pack, shell, approval or construction release. Foundation hold remains in force; preparation does not authorize construction or accept dimensions, placement or engine readiness.",
  "name": "Split Complex",
  "kind": "building",
  "priority": "P2",
  "protocol_revisions": {
    "building": "R05",
    "district": "R05",
    "spatial_imagery": "R01"
  },
  "source_main_commit": "8e9c5949400a528e0e16274e137653584a5560eb",
  "register_tasks": [
    {
      "id": "PI-BLD-0002-V01-01",
      "work": "Confirm parcel/placement and controlling exterior references; reconcile current UE state",
      "status": "pending"
    },
    {
      "id": "PI-BLD-0002-V01-02",
      "work": "Approve envelope, levels, core and dimensions; record scale source and exceptions",
      "status": "pending"
    },
    {
      "id": "PI-BLD-0002-V01-03",
      "work": "Issue dimensioned site/ground/roof plans, distinct-floor plans and necessary sections",
      "status": "pending"
    },
    {
      "id": "PI-BLD-0002-V01-04",
      "work": "Measure the two cores and bridge levels/clearances. Review skybridge egress and shared circulation.",
      "status": "pending"
    },
    {
      "id": "PI-BLD-0002-V01-05",
      "work": "Select enterability and implement only the approved room/kit program: Paired lobbies, reusable office/residential floor, skybridge garden only if selected playable",
      "status": "candidate_scope"
    },
    {
      "id": "PI-BLD-0002-V01-06",
      "work": "Review shell fit and a furnished/player-camera sample; derive actual window/site views",
      "status": "pending"
    },
    {
      "id": "PI-BLD-0002-V01-07",
      "work": "Verify collision, navigation, access, streaming, materials and performance; issue manifest and current commit evidence",
      "status": "pending"
    }
  ],
  "authoritative_dimension_contract": "production/assets/buildings/PI-BLD-0002-V01/BUILDING_DIMENSIONS.json",
  "dimensions_status": "unset",
  "input_record": {
    "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."
      ]
    }
  },
  "source_hash_inventory": [
    {
      "path": "docs/current-decisions.md",
      "sha256": "8001f9a1c613b326b030da3ace10947a3021dc12f9273b7c7fa46d0ade10d382"
    },
    {
      "path": "production/assets/buildings/PI-BLD-0002-V01/BUILDING_DIMENSIONS.json",
      "sha256": "a35e33e05be7ff779653d020f4b6849cc8a14272f780f35926c3e9c1c6fb0c0e"
    },
    {
      "path": "production/assets/buildings/PI-BLD-0002-V01/REFERENCE_INDEX.csv",
      "sha256": "dcfbf6674ded41cab605eab4dea8cf520c466504363d8cc30ae29c8bdb9a595f"
    },
    {
      "path": "production/assets/buildings/PI-BLD-0002-V01/VISUAL_NOTES.md",
      "sha256": "1e3b67375cb121fec292e2949955bd9de3ada2d70a034b99034171bd54cea2d3"
    },
    {
      "path": "production/districts/D02-CrownKey/planning/BUILD_REGISTER.json",
      "sha256": "bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e"
    },
    {
      "path": "production/districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_A.json",
      "sha256": "8193933c210b0cfaa825428aae1a0d1d2b2fbe8f11d6c7befc0db81d7892d2d4"
    },
    {
      "path": "production/districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json",
      "sha256": "52525e0754aee464c84793b3b3cfe2b6ae4c95981fd2bf3e67c2d91c02ada0b9"
    },
    {
      "path": "production/protocols/building/R05/GUIDE.md",
      "sha256": "006818490740b4bd9e3994a428da95390f9f4dd987c6fd6f67a8dd1dbbc24509"
    },
    {
      "path": "production/protocols/building/R05/README.md",
      "sha256": "ecb4c6b0bf144a5da037ba8817528c40cb59ce272bc9ca63b3d187e704dc2715"
    },
    {
      "path": "production/protocols/building/R05/templates/ASSET_BRIEF_TEMPLATE.json",
      "sha256": "d6f80614e4f7d87f7cd569c7b1320cf6ad58c2021fab1955ff274a157d8df054"
    },
    {
      "path": "production/protocols/building/R05/templates/BUILDING_DIMENSIONS.json",
      "sha256": "46fefd72cb9e5bd0b1e98822a1773401f96c35d91ce57fc821d3bbc624e69631"
    },
    {
      "path": "production/protocols/current.json",
      "sha256": "c7be63113d117523e6b2e608149e6b31620f2f50436f4fbbeebdd1ffb005881a"
    },
    {
      "path": "production/protocols/district/R05/README.md",
      "sha256": "f95ad3a6c25f181898fd3be47eac800b39b5f1790387f8e93d5450e75ace5a7d"
    },
    {
      "path": "production/workflows/spatial-imagery/R01/GUIDE.md",
      "sha256": "288df4dc11896d4e606f8dc49f8b1a6969679d1fad50fad7595f3e2c8b9ad173"
    },
    {
      "path": "production/world/SCALE_REGISTER.md",
      "sha256": "f56c19d5dbfd1c9b9228c4f34327f908ebee5c9bc9c9d3db2d617fa802accc8e"
    }
  ]
}
