# PI-STR-0002-V01 · Bridge Landing

EXTERIOR CANDIDATE R01. Editable reusable local geometry, derived views and a proposed dimension/interface contract. All acceptance gates remain false.

## Reference identity

- Masonry capped abutments and broad stair transition occur in the source crop.
- Bronze/amber rail and light details continue from the span.

The exact original catalog crop is `catalog-reference.webp`; its immutable source is in `SOURCE_REFERENCE.json`. The catalog is visual evidence, not a survey. Read `CANDIDATE.json` for every editable component and `INTERFACES.json` for route and endpoint datums. Do not infer Crown Key shoreline, bridge count, tide or placement from this candidate.

## Build order for Quik

1. Keep the original source and candidate in separate Blender collections. Use metres, Z up, front −Y, unit object scale.
2. Run the shared `../../../../../../tools/crown_exterior_batch.py` on `CANDIDATE.json`; or import the delivered OBJ/MTL as the exact generated candidate.
3. Review hero/rear/front/plan views and dimensions from this same model before altering the silhouette.
4. Resolve the interface and source gaps below, then attach this local candidate to the reviewed district frame. Endpoint datums are local authoring interfaces, not claimed world coordinates.
5. Check actual structural/support behavior, drainage, collision, route transitions, camera/capsule fit and engine materials. Record real engine tests separately.

## Proposed local interfaces

- district_side: [0, -6, -0.45]; lower landing datum; actual site grade unknown
- span_side: [0, 6, 0]; upper pedestrian landing; span adapter must reconcile +0.14m shoulder

## Route

{
  "ramp_polyline_m": [
    [
      -4.9,
      -6,
      -0.45
    ],
    [
      -4.9,
      -5,
      -0.45
    ],
    [
      -4.9,
      5,
      0
    ],
    [
      -4.9,
      6,
      0
    ]
  ],
  "ramp_clear_width_m": 1.975,
  "ramp_slope": 0.045,
  "steps": 4,
  "riser_m": 0.1125,
  "tread_m": 2.5
}

## Source gaps / next decisions

- Grade change 0.45m and side ramp are new proposed coordination, not measured catalog facts.
- Join to actual span and road/footpath grades remains unresolved; landing top0 versus span pedestrian+0.14m needs a reviewed adapter.
- Ramp landing/handrail/access requirements need project-specific review.

## Scope boundary

A local pedestrian landing study with both broad steps and a clear side ramp. Does not claim completion of a district vehicular abutment.

No dimension, engineering, access-code or engine compliance is claimed. Local geometry and arithmetic checks only. All cited widths and slopes are proposed and require project-specific review.
