# Split Complex · first design direction R01

PI-BLD-0002-V01 · Codex recommendation · 16 October 2026 · **CONCEPT / NOT TO SCALE**

**Recommend H1: keep the catalog's asymmetric blade towers and one dominant elevated connection; develop that connection as an enclosed gallery with a planted roof.** Keep the left tower shorter and slimmer, the right taller and broader, and the central slot visibly open. Carry the close garden render's curved glazing, amber interiors and planting into this simpler connection story.

This is the author-selected hypothesis for the first coherent visual package. Legend has not selected H1, enterability or dimensions. It is not a shell, placement, engine or construction release. Building R05, District R04, Spatial Imagery R01 and the Foundation hold remain in force. The existing per-asset dimension contract stays unchanged and unset.

## Reference authority by purpose

| Source | What was observed | Recommended use in H1 | Limit |
| --- | --- | --- | --- |
| Original catalog ZIP, `02_Towers_and_Variants_Global_IDs.png`, row 1 column 2 | Named Split Complex; shorter/thinner left blade, taller/wider right sail, large gap, one dominant slim bridge and low arched base | Whole-building identity, tower hierarchy, silhouette and base character | Concept; explicitly not to common scale; vegetation separate |
| Original `25-Twin-Blade-Towers-and-Garden-Bridge-4.png` | Close perspective; planted upper span with pool/shade elements and a lower arched partly enclosed span; curved inner balconies, warm glass and ivory fins | Material/detail vocabulary, planted atmosphere and gallery junction character | Cropped base and inconsistent massing/bridge readings; not a measurement or placement source |
| Original `28-Crown-Landmark-Amber-Atrium-Entrance-1.png` | Refined warm ivory, blue glass, amber light, planting and reflected finish | Craft and lighting benchmark | Another asset; its crown, monumental portal and atrium do not become Split Complex geometry |
| Prior `split-complex-concept-a-r01.png` | Generated one-bridge asymmetric study with an expanded base and heavy planting | Comparison and continuity | No independent authority over the originals, dimensions or creator selection |
| Existing `SPLIT_REFERENCE_REVIEW.md` | Correctly records unresolved source conflicts and Candidate A | Preserve the conflict history | H1 is a new bounded recommendation, not a retroactive approval of Candidate A |

All four images were opened and visually inspected. The original ZIP was preserved; the catalog sheet was extracted for inspection. Upload prefix 25 and repository prefix 26 refer to a matching subject, but their bytes have not been established as identical. Exact upload hashes, asset-record Git blobs and source roles are in [REFERENCE_DECISIONS.json](REFERENCE_DECISIONS.json).

The partial local snapshot did not contain the asset originals, and its served asset JSON mirrors were empty. The asset README, brief, visual notes, dimension contract and preparation README were therefore read directly from repository commit `565ec6ab58f6fa08879c682fcb953a2c658b7687`. They establish a concept-only asset, proposed Tier C, paired-lobby/two-core questions, optional garden access and unselected office/residential kit work.

## Observation, interpretation and proposal

**Observed:** the catalog and close render share two different blade profiles, blue curved glazing, ivory sweeps, amber light, an open gap and a bridge. They disagree about tower proportions and bridge expression. The close render visibly contains more than the catalog's simple bridge band; it does not settle a single accepted topology.

**Interpreted:** the named complete catalog card is the best identity guide, while the location render is the better local finish reference. A garden above a warm glazed arched connector is a useful shared theme. Neither source proves floor counts, matching floor levels, structural support or exact dimensions.

**New proposal H1:** compress that theme into one connection body and one candidate accessible crossing datum. Put the gallery inside the body; place scenic planting on its roof. This is a deliberate design synthesis to test, rather than a claim that the two images already describe identical geometry.

## Selected massing and base

Use the open-gap catalog side as the provisional comparison front. Left and right always mean a viewer facing that side; they are not compass directions. District front, north and placement remain unset.

- **Left tower:** shorter and slimmer, with its distinct wrapping ivory ribbon and a low stepped outer shoulder. Preserve a scooped sail character at the top; avoid making it a small copy of the right tower.
- **Right tower:** taller and broader, with a sharper high sail crest and long sweeping outer-right edge. Keep the blue glass body legible within the ivory blade.
- **Central slot:** retain open sky above the bridge and a large open void below it, down to the low base. Balconies and planting must not fill the slot or obscure the endpoints.
- **Podium:** one low shared arcade ribbon at the tower feet, separate lobby thresholds and a generous open central ground passage. Warm glazed bays can occupy the tower bases. Do not turn the podium into an enclosed shopping mall or a second high connector.
- **Landscape:** use restrained planters on inner terraces, bridge roof and low base. Keep vegetation as a separate dressing scope. Dense palms must not conceal the architecture being reviewed.

No tower-height ratio, podium dimension, floor count or fin structural role is selected. Apparent floor bands are visual rhythm until a level schedule exists.

## One bridge connection story

The gallery has one level walking surface between short recessed landing vestibules on the inner faces of the two towers. Both landings meet the same proposed crossing datum; this does not imply the same numbered floor in two different towers. Keep the clear route visibly free of balcony rails, fin intrusions and ornamental objects.

The ivory body has curved haunches and an arched underside. The walking floor does not follow that arch. Glazed sides reveal an amber-lit sheltered crossing. A shallow planted roof provides the garden silhouette without making a second public bridge deck. Roof maintenance access is deferred and does not create a playable route in R01.

The roof/build-up, enclosed headroom and curved underside may compete for space. The first section must test whether the compact silhouette can contain them. If it cannot, revise the authored bridge design and every affected view; do not silently thicken it in one image or curve the walking floor to hide the problem. Bearing, movement, loads, support and technical egress remain unresolved.

Exclude the close render's pool, shade-sail amenity deck and second independently accessible span from this pass. These could be a later explicit alternative, but are not the recommendation.

## Bounded entry and interior route

Recommend one left arrival lobby and core journey, the enclosed bridge and a right receiving landing with an integral compact overlook. Return by the same route. This is a candidate selection for review; the production brief's Tier C remains proposed and unchanged. Its paired-lobby program is source context, not a commitment to develop both lobbies in R01.

| Candidate space/interface | Purpose | Boundary |
| --- | --- | --- |
| One left arrival lobby | Establish the selected entrance under the arcade and a reusable finish family | One compact arrival space; right lobby interior deferred |
| Left core journey/interface | Link the left lobby with its bridge landing | Actual shafts, dimensions, lift/stair continuity and operation await measured plans and engine tests |
| Left bridge landing and right receiving landing | Make the crossing datum and endpoints legible | Right core/egress reserved for later technical design; no second developed core journey |
| Enclosed bridge gallery | One sheltered cross-tower route with a view | One candidate accessible level |
| Right landing overlook bay | Small pause area beside the through-route | Part of the landing; no separate lounge, venue or roof destination |

Candidate route: left arcade threshold → left lobby → left core journey/interface → left bridge landing → gallery → right receiving landing/overlook → return through the gallery, left core and left lobby. This relationship diagram is not proof that a lift, stair, protected route or compliant egress has been designed.

Reserve the cores toward the inner/rear side of each tower so short branches can reach the bridge without putting a core across the front glass. Their exact locations must follow the later shell and clearance study. Develop only the left journey in the first route study; the right core and egress remain reservations for future technical design. Both exterior entrance thresholds may remain visible without implying a completed right lobby. Keep unmodeled floors and service zones behind controlled thresholds; do not imply inaccessible doors lead to completed rooms.

Defer the right lobby interior and right core journey, office/residential typical floors, apartments, full tower corridors, intermediate lift stops, roof pavilion interiors, public bridge-roof garden, pools, restaurant/retail fit-outs, basements, parking and service-room fit-outs. No council, diplomacy or named story rooms are added. Functional diagram labels are placeholders, not issued room or level IDs.

## Image briefs and invariants

Every new image carries **CONCEPT / RECOMMENDED H1 / NOT TO SCALE** in its surrounding page or caption. Generated images may communicate intent; they do not become measured orthographic drawings or verified cross-view geometry.

1. **Full-building master:** one readable open-gap three-quarter view, complete tower tips and low base in frame. Use the catalog's asymmetry, left wrapping ribbon/stepped shoulder and right sharp crest/outer sweep. Show one compact high enclosed bridge with planted roof, large empty slot and an open ground passage. Use a neutral presentation background.
2. **Bridge/landing detail:** show both tower endpoints in one useful oblique, one level route inside glazing, recessed vestibules, amber interior and curved ivory underside. Planting sits on the roof. Do not introduce another walking deck, pool or disconnected threshold.
3. **Lobby route:** compact warm arrival under Split Complex's arcade, blue glazing, ivory arch pier, restrained warm metal and integrated lighting. Show a clear path from entrance to core approach; furniture stays outside the route. Benchmark Crown Landmark's finish without copying its crown portal or chandelier identity.
4. **Optional landing view:** a small bay within the same landing/gallery, restrained bench or pause area and uninterrupted through-route. Neutral sky beyond the glass until placement and saved cameras determine the real view.

Across the set, retain the same tower hierarchy, bridge count, base, landing story and finish family. The smaller left tower must remain visibly smaller in the declared comparison-front view. Keep the distinctive tower fins legible. Do not show a Crown Landmark crown, invented height metrics, scale bars, floor numbers, north arrows, surveyed site context or an asserted ocean/city view. The image operator records the actual references, tool/method, resulting files/hashes and qualitative deviations.

## Alternatives set aside

| Alternative | Reason to set aside now |
| --- | --- |
| Literal two-deck pool/garden bridge from the close render | Conflicts with the catalog's slimmer identity and adds an amenity route and level/egress obligations before fit is known |
| Near-equal or mirrored towers | Loses the named catalog asymmetry; perspective does not authorize a new massing hierarchy |
| Bare open bridge with no enclosed gallery | Simpler fallback if H1 cannot fit, but does not provide the recommended sheltered route or close-render interior character |
| Use generated Concept A as a geometry master | No authored measured model or saved cameras; generated choices cannot resolve original conflicts |
| Copy Crown Landmark's central entrance/crown | Transfers another asset's identity beyond its reference role |
| Expand directly to full office/residential kits | The starter proposes these; no program or scope is selected, and the bounded route needs review first |
| Develop both lobbies and a complete two-core through-route now | The first journey needs one arrival, crossing and receiving landing. Keep the far core/egress reservation without adding a second lobby interior |

## What the next measured pass must resolve

| Question | Evidence required | Owner |
| --- | --- | --- |
| Is H1 the chosen design and route scope? | Review the coherent images and record a named selection, edits and enterability | Legend |
| How large are the unequal towers and low base? | Authored envelope/level proposal with scale basis in the existing per-asset contract; no perspective pixel calibration | Asset author proposes; Legend selects scale |
| Can the two reserved cores meet one bridge datum? | Ground and bridge plans plus a section through both core reservations; develop the left journey and far landing to this scope, with floor schedule, future lift/stair continuity and clear landing openings | Layout/model author with Quik |
| Can the bridge remain compact and traversable? | One shared connection record for both ends; span/support/movement, headroom, level floor, roof build-up and fin/structure intrusions | Layout/model author and technical reviewer |
| Does the base support usable entrances? | Podium plan/section, open passage, door and furniture clearances, core approaches | Asset author |
| Does the route work with the actual player/camera? | Furnished sample and measured import/collision/traversal evidence, including doors, lift/stair behavior and protected route review | Quik and layout author |
| Where is the asset and what is outside its windows? | Selected parcel, shared frame, front/north convention, ground/access interfaces and model/camera-derived views | Legend and district/layout author |

No new dimension contract is issued in this design pass. No measured layout, shared model, saved physical camera or metric overlay accompanies these recommendations. Keep the visual package at CONCEPT; advance it only with the evidence and scoped approvals required by the adopted workflow. Pilot feedback, foundation readiness and actual engine verification remain separate work.
