# PI-STR-0001-V01 · Bridge Span

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

## Reference identity

- Catalog shows a vehicle bridge with two pedestrian edges, pale masonry piers and arched spandrels.
- Metal guardrails and repeated amber lights define the edge.

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

- end_A: [-12, 0, 0.035]; road top datum; pedestrian shoulders +0.14m
- end_B: [12, 0, 0.035]; road top datum; pedestrian shoulders +0.14m

## Route

{
  "vehicle_clear_width_m": 8,
  "pedestrian_clear_width_m_each_side": 2.875,
  "pedestrian_surface_z_m": 0.14,
  "road_polyline_m": [
    [
      -12,
      0,
      0.035
    ],
    [
      12,
      0,
      0.035
    ]
  ],
  "pier_underside_z_m": -7,
  "water_clearance_m": null
}

## Source gaps / next decisions

- No surveyed span length, pier spacing, water clearance or district abutment transform.
- District 20m boat air-clearance requirement remains an unresolved placement constraint: this isolated local span does not establish water datum or satisfy that requirement.
- Load path, foundation, road crash containment and pedestrian segregation need engineering.
- No count or arrangement of actual island bridges is established.

## Scope boundary

One isolated reusable span candidate, not a replacement district bridge layout. Road and pedestrian surfaces are authored separately; piers and arches are real geometry.

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.
