# Split Complex — H1 C01 proposed candidate

**PI-BLD-0002-V01 · 17 October 2026 · PROPOSED DESIGN · NOT BUILD-READY · NOT ENGINE-VERIFIED**

This package turns the H1 concept into a dimensioned local-space blockout with one arrival lobby, one enclosed gallery and one receiving lounge, plus the left landing. It supplies an editable OBJ, keyed plans, elevations, sections, room and opening schedules, neutral renders, proposed finishes and furniture positions. It is ready for the next authoring pass. It is **not** a completed location: solid core proxies block the ground-to-gallery journey, and the sculptural blade silhouettes remain simplified envelopes.

The working topology is **one enclosed high gallery with a scenic planted roof**. The low arcade canopy is separate. The earlier CB00 two-bridge alternative remains historical; its upper public deck and pool have not been carried into this candidate. H1 selection and dimensions are author proposals, with creator acceptance unrecorded. No named atlas scene is assigned to Split; the lobby/gallery/lounge labels are functional design labels.

## Open these first

1. [Primary 14-page drawing set](derived/PI-BLD-0002-V01_H1-C01-PROPOSED_DRAWING_SET.pdf): seven clean keyed plans, four elevations, two sections and the proposed level schedule. The keyed plans identify physical openings and proxy cores. The older generic per-level SVGs remain supplemental references; most intermediate floors have no authored interior.
2. [Editable neutral OBJ](derived/PI-BLD-0002-V01_H1-C01-PROPOSED.obj) with its [MTL](derived/PI-BLD-0002-V01_H1-C01-PROPOSED.mtl). It is a metre-scale, Z-up candidate generated from the JSON; import settings and actual engine behavior still require testing.
3. [Local room/furnishing diagram](PLAYABLE_SLICE_PLAN.png): proposed route and furniture bounding boxes. This zoning diagram omits walls/openings; use the keyed plans for opening locations.
4. [Building dimensions](BUILDING_DIMENSIONS.json), [room schedule](ROOM_SCHEDULE.json), [route/furnishing schedule](ROUTE_AND_FURNISHING.json) and [saved camera schedule](CAMERA_SCHEDULE.json).
5. [Open issues](ISSUES.json), [topology decision](TOPOLOGY_DECISION.json), [material assignments](MATERIAL_ASSIGNMENTS.json) and [view matrix](VIEW_MATRIX.json).

## Dimensional brief

All values are **proposed metres**, not measurements from the concept images. The frame is X local right, Y local rear, front −Y, Z up. The origin is the ground finished-floor datum at the center of the open tower gap. Site transform, placement ID and district frame remain null.

| Element | Proposed geometry |
| --- | --- |
| Overall foundation bounds | 110 × 44 m; X −52…58, Y −24…20 |
| Left / right roofs | Z 124.8 / 153.2 m |
| Left / right upper tower envelopes | 28 × 36 / 34 × 40 m; extruded proxies |
| Ground lobby | Clear envelope 33.3 × 39.3 m; Z 0 floor; 6.6 m clear height |
| Enclosed gallery | 40 m span; 12 m outside width; 11.3 m internal width; floor Z 88; 6.0 m clear height |
| Gallery portals | Four paired host/bridge openings, each 4.2 × 3.2 m clear |
| Receiving floor | Clear envelope 33.3 × 39.3 m; floor Z 88; 6.6 m clear height |
| Receiving lounge | 21 × 22 m furnishing zone, X 29…50 and Y −16…6; no enclosing partition |
| Front receiving glazing | Y −20; keep Y −19.65…−16 clear for the perimeter route |
| Walls / slabs | 0.35 / 0.40 m proposed |

The left tower has proposed occupied floor assignments only through L25 at Z 117; its upper crown envelope continues unoccupied to Z 124.8. L26–L32 are assigned only to the right tower. The intermediate tower bodies are solid proxies; the schedule does not represent modeled or furnished typical floors.

## Room and route program

| ID | Delivered definition | Remaining work |
| --- | --- | --- |
| SP-L00-LOBBY | Physical hollow shell, entrance/glazing openings, 3 m clear-route reservation, six proposed prop bounding boxes | Reception/detail meshes, lighting, functional core interface |
| SP-L19-LANDING | Physical landing shell and paired gallery portal; core approach | Functional lift/stair arrival and refined vestibule |
| SP-L19-GALLERY | One hollow enclosed crossing, glazing and flat floor, 4 m central keep-clear lane, four proposed prop boxes | Blade/haunch interface, structure intent, roof drainage/planting, detailed finish geometry |
| SP-L19-RECEIVING | Physical receiving shell, front/side glazing, 3 m route, nine proposed lounge prop boxes | Detailed lounge furnishing, refined blade skin, exit/camera tests |

The intended sequence is entrance → lobby → left lift/stair → landing → gallery → receiving lounge → return. **The lift/stair segment is blocked by CORE_L.** CORE_R is also a solid future reservation. Neither the route polyline nor an analytical opening pass proves full traversal. The gallery roof is scenic, with no authored public access. The right base remains an undeveloped interior beyond its visible thresholds.

## Appearance and materials

The existing H1 exterior, bridge, lobby and gallery concepts are linked in [VIEW_MATRIX.json](VIEW_MATRIX.json). The new [receiving lounge concept](../images/split-receiving-lounge-r01.webp) communicates palette and furnishing intent. Its curved glazing/columns and glossy stone exceed or differ from this orthogonal candidate. **The JSON, keyed drawings and same-input neutral renders govern the current geometry.** No image grants creator acceptance, site placement or measured geometry.

Finishes use exact IDs from [the shared material library](../materials/material_library.json): ivory mineral surfaces, honed stone floors, restrained champagne bronze, lagoon glass, warm timber accents and pale linen. The candidate OBJ retains technical category materials; finished PBR assignments are proposed. The [19 proposed prop positions](ROUTE_AND_FURNISHING.json) reference six types in [the shared prop bill](../materials/prop_bill.json). These are bounding boxes, not delivered detailed props.

Distinct appearance gaps remain: a finished rear/opposite-side view, targeted entrance detail and receiving reverse/exit view. The neutral rear and reverse cameras already exist; refine the underlying blade geometry before presenting future images as coherent model evidence.

## Validation and limits

- Upstream schema analysis reports COMPLETE with zero errors, warnings or missing entries. That status describes supported input coverage only.
- The sealed fallback OBJ contains 456 closed primitives / 4,432 triangles. Mesh checks report positive primitive volumes, no nonmanifold primitives and no duplicate upward floor areas.
- All 18 opening-center probes match expected passability: eight doors/portals clear, ten glazed windows blocked. All 24 threshold stations satisfy the declared check; the two exterior front-entry approach stations are explicitly not required because site paving is unplaced.
- [FURNISHING_CHECK.json](FURNISHING_CHECK.json) checks all 19 prop bounding boxes against host bounds, six keep-clear zones, core proxies and each other; shared material/prop references resolve. It does not test actual prop meshes, moving cameras, door swings, accessibility or egress compliance.
- Nine neutral images use the saved camera/model data. No Blender export/round-trip or Unreal import was executed. OBJ export and CPU renders are the available fallback evidence. [REBUILD_BLENDER.sh](derived/REBUILD_BLENDER.sh) is a replay entry point, not proof of execution.
- The issue gate deliberately returns `issuable: false`: this is a candidate under `docs/`, not an issued production contract. Do not move the file into production solely to bypass that gate.

## Next authoring pass

Replace CORE_L with a real clear shaft/cabin/doors and a modeled stair/landing route; verify the complete ground-to-L19 journey. Refine both distinct catalog blade silhouettes, the low arcade and the gallery underside while retaining the proposed doorway and walking-floor datums. Resolve bridge bearings/movement and roof planting build-up. Then dress the bounded rooms, apply actual materials, import with Quik's player/camera and record observed collision/traversal evidence. Site placement and district approach need the district frame before any world-facing doorway or view can be accepted.

Work in a new candidate revision if geometry changes. Preserve this input and its sealed outputs so the review remains reproducible. The existing canonical per-asset dimension contract was not modified.

## Reproduction and authority

Baseline repository commit: `d88c6658de0439be2256b546e37bac03718b5ed6`. Source roles and byte hashes are in [SOURCE_RECORD.json](SOURCE_RECORD.json). The exact source JSON byte SHA-256 is `30c2423b92ef008ab725f938f04d90a3926223baaff899a92c9f6e95bcfedc8c`.

`build_candidate_inputs.py` recreates the authored source records; `build_supplement.py` recreates supplemental schedules and the zoning SVG; `verify_candidate.py` runs the disclosed reference/AABB checks. The toolchain owns the derived generation. [derived/MANIFEST.json](derived/MANIFEST.json) records its source and tool hashes, output inventory and execution limits; [PACKAGE_MANIFEST.json](PACKAGE_MANIFEST.json) inventories this complete candidate and shared dependencies. Do not run a generator while another writer is sealing the package.
