# PI-STR-0003-V01 · Seawall and Promenade · preparation R01

**DRAFT_PRODUCTION_PREP** · 2026-10-16

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.

Prepare an unplaced shoreline section library distinguishing promenade wall from rocky/boulder options; hold datum and segment selection.

## Scope basis

Notes conflict between recessed wall, plain promenade edge/bollards and rocky shoreline. Foundation reset replaces freestyled coast; no one section is approved for every segment.

## Components

| Component | Role | Evidence | Open questions |
|---|---|---|---|
| Promenade surface | Pale tiled walk with curved cut-outs/edge variations. | source_notes | What clear width, level and accessible transition apply? |
| Recessed wall | Weathered base, waterline band and shallow lit arches. | source_notes | Is recessed wall standard or segment-specific? |
| Rock/boulder edge | Aerials show boulders west/northwest unlike quay-like render. | source_notes | Which segments use boulders and are rocks separate assets? |
| Bollard/rail edge | Render has gold-banded bollards; card has glass/metal rail/lamp. | source_notes | Which safety/boat interface applies by shore segment? |
| Datum/joints | Water/tide datum and dock/landing joins are open. | source_record | What datum governs wall/dock and relevant boat-clearance route? |

## Modeling sequence

1. **Separate typologies** — Compare recessed wall, plain promenade, rocky edge; do not make one standard. Gate: Legend assigns types after master review.
2. **Set datum fields** — Keep water/tide and wall-top null until resolved. Gate: Datum named before dimensioned section.
3. **Block edge parts** — Keep walk, wall, rocks, rails, bollards and planters separate. Gate: No detail baked into every shore segment.
4. **Check neighbor joints** — Diagram access, dock and landing ties. Gate: R04 connection review resolves interfaces.
5. **Package sections** — Return typology sections with no transform. Gate: Respect foundation reset and construction hold.

## Required review views

- **Shore typology strip plan** — Show wall/quay/boulder cases separately.
- **Promenade section** — Show walking surface and edge with datum null.
- **Rocky-edge section** — Keep boulders separate from promenade.
- **Dock/landing interface** — Show optional joins and datum questions.

## Candidate kits

- CK-KIT-SHORELINE
- CK-KIT-DOCK
- CK-KIT-BRIDGE
- CK-KIT-PROPS

## Proposed dependencies

- PI-STR-0002-V01: Candidate landing interface after wall type/datum selected. (proposed)
- PI-STR-0004-V01: Candidate dock frontage; count/spacing not assigned. (proposed)
- PI-STR-0005-V01: Candidate dock joint; attachment/tide unresolved. (proposed)

## Decision queue

- Which segments use recessed wall, plain promenade or rocky edge? Owner: Legend. Resolution evidence: Accepted shore typology map on current master..
- What datum governs tide, wall and boat clearance? Owner: Legend + Quik. Resolution evidence: Approved datum and measured section..
- Which rail/bollard and clear route treatment is selected? Owner: Quik. Resolution evidence: Dimensioned section and access/interface review..
- Where do docks/landings meet shoreline? Owner: Legend + Quik. Resolution evidence: Endpoint records and neighbor review..

## Friday: can prepare

- Prepare separate wall/promenade/boulder sections with datum unset.
- Create typology comparison and connection-question sheet.

## Friday: requires decision

- Accepted type per segment, water datum, route width and adjacent connections.
- Foundation reset/hold release before district assembly.

## Friday: return evidence

- Reusable components with no placement transform.
- Typology plan/sections with datum blank or decided.
- Proposed-only connection matrix.

## Controlling records and source inventory

- Dimension contract: [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json).
- Building R05 / District R05 / Spatial Imagery R01; dimensions and approval remain governed by their own records.
- [current-decisions.md](../../../../../../docs/current-decisions.md) · SHA-256 `8001f9a1c613b326b030da3ace10947a3021dc12f9273b7c7fa46d0ade10d382`
- [ASSET_BRIEF.json](../../ASSET_BRIEF.json) · SHA-256 `4e756a0f0da55452be9d9556a08ee74e5079589e53547533f365f6f6199c0005`
- [BUILDING_DIMENSIONS.json](../../BUILDING_DIMENSIONS.json) · SHA-256 `80ac70eca019dde1cdd2a8d91a9bc9bb67ec1d7917f9d4ff8ad5989538909f71`
- [REFERENCE_INDEX.csv](../../REFERENCE_INDEX.csv) · SHA-256 `d42ad5c467c3c0015b176801d5688621d345a944fc935bea80039c732c321f0d`
- [VISUAL_NOTES.md](../../VISUAL_NOTES.md) · SHA-256 `5dbd2950dba0f3214dfb1ea0d22b3514e328ca90e86f0993331bf742e0c7d855`
- [BUILD_REGISTER.csv](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.csv) · SHA-256 `45be2626767273dce204c95a1233c943cdcdc119fce7a17eda4810c3606a0d52`
- [BUILD_REGISTER.json](../../../../../districts/D02-CrownKey/planning/BUILD_REGISTER.json) · SHA-256 `bb0a893c54a83f490e9ff59197e593ea1093a393209c7714d57997cd3c06df3e`
- [ASSET_INPUTS_B.json](../../../../../districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_B.json) · SHA-256 `13b830ec89a557291c006de40e75574fa3be9cb844bb5c021f978e1a021d2698`
- [KIT_CATALOG.json](../../../../../districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json) · SHA-256 `52525e0754aee464c84793b3b3cfe2b6ae4c95981fd2bf3e67c2d91c02ada0b9`
- [Building_R05_GUIDE.md](../../../../../handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md) · SHA-256 `006818490740b4bd9e3994a428da95390f9f4dd987c6fd6f67a8dd1dbbc24509`
- [README.md](../../../../../protocols/building/R05/README.md) · SHA-256 `ecb4c6b0bf144a5da037ba8817528c40cb59ce272bc9ca63b3d187e704dc2715`
- [current.json](../../../../../protocols/current.json) · SHA-256 `c7be63113d117523e6b2e608149e6b31620f2f50436f4fbbeebdd1ffb005881a`
- [CONNECTIONS.json](../../../../../protocols/district/R04/templates/CONNECTIONS.json) · SHA-256 `a8b0be74020bc7b67bdf47eb2bacaa52515f301a02423bbc3bd676b4994387ab`
- [README.md](../../../../../protocols/district/R05/README.md) · SHA-256 `f95ad3a6c25f181898fd3be47eac800b39b5f1790387f8e93d5450e75ace5a7d`
- [GUIDE.md](../../../../../workflows/spatial-imagery/R01/GUIDE.md) · SHA-256 `288df4dc11896d4e606f8dc49f8b1a6969679d1fad50fad7595f3e2c8b9ad173`
