New exterior candidate · R01
Open the model and drawings.
Proposed isolated geometry, four views from the same model, elevations, section and editable sources. Dimensions, shell acceptance, interiors and engine verification remain separate.
Exterior package and downloads →Draft production prep · R01 · 16 October 2026
Bridge Landing
Prepare isolated landing/abutment interface study; do not set coordinates, transforms or routes while foundation inputs are unresolved.
Current R02 scope requires a complete usable asset package. Design and isolated authoring can proceed; proposed dimensions, shell selection, site placement and actual engine checks retain explicit evidence status.
Current production program · R02
Exterior, usable spaces and a complete handoff.
Complete Bridge Landing with usable access, materials, clearances and coordinated building / waterfront interfaces.
Required spaces
- Continuous public access through the authored structure
- Defined service / restricted boundary and adjoining asset connection
Required exterior coverage
- Overall usable route
- Interface close-up
- User-eye approach / exit
- Section or clearance review from authored model
Delivery state: Scoped — complete design: not yet evidenced; reviewed build packet: not yet evidenced; engine verification: not yet evidenced.
Audited source baseline: Catalog/source preparation and starter records; no dedicated asset design pack, drawings or model identified.
Owner: OA1 / assign after first packages · Independent reviewer: OA1-assigned independent read-only reviewer
Five-seat production plan and kickoff briefs → · Full current scope → · Download all31 programs
R02 supersedes conflicting shell-only or deferred-interior recommendations in the earlier preparation records below. Proposed room uses do not create new story canon; references do not establish completed geometry.
Prepare now
- Prepare detached abutment/apron/rail kit with grade and endpoint fields blank.
- Diagram road/steps/ramp alternatives without coordinates.

Preparation / not geometry
What Quik will build and review.
Component labels come from this asset’s prep record. This board is a task map, not a dimensional drawing.
- 01Curved abutmentsource notes
- 02Apron/grade transitionsource notes
- 03End post/rail jointsource notes
- 04Switchback interfacesource record
- 05Shore/water interfacesource record
Modeling sequence
- 01Register conflictsNo landing ID or position inferred.
- 02Block abutment partsVisual form review without fixed location.
- 03Diagram movementRoute/grade selected before layout.
- 04Test jointsEndpoint/datum agreed before assembly.
- 05Return evidenceNo placement/collision claim.
Planned review views
Components & scope evidence
Scope basis: Concept shows curved abutment, tiled apron/steps and rail continuity, but card vs aerials differ on road/step treatment and landing locations. Switchback attachment is open.
| Component | Role and evidence | Open questions |
|---|---|---|
| Curved abutment | Pale sweeping face and stepped plinth. source_notes |
|
| Apron/grade transition | Tiled apron and steps in card; aerials read road-level. source_notes |
|
| End post/rail joint | Lit end post and bridge rail continuity. source_notes |
|
| Switchback interface | Required creator route is not drawn on landing card. source_record |
|
| Shore/water interface | Must meet a selected shore type and datum. source_record |
|
Modeling sequence & review views
Register conflicts
Record landing discrepancies and card/aerial step ambiguity.
Gate: No landing ID or position inferred.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Block abutment parts
Separate face, apron, steps, rail/post and road edge.
Gate: Visual form review without fixed location.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Diagram movement
Separate road, pedestrian and switchback alternatives.
Gate: Route/grade selected before layout.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Test joints
Show span and shore as detached components.
Gate: Endpoint/datum agreed before assembly.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Return evidence
Plan/elevation/section/joint views; dimensions null.
Gate: No placement/collision claim.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Required review views
Landing plan
Show apron and vehicle/pedestrian/ramp options.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Water-facing elevation
Show curved face, plinth and rail.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Landing section
Show deck/water datum and transition unknowns.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Span/shore joint axon
Show detached interfaces, no coordinates.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Shared kits & asset dependencies
Candidate kits
Proposed dependencies
- PI-STR-0001-V01: Proposed span deck/rail joint; endpoints unresolved. (proposed)
- PI-STR-0003-V01: Candidate shore joint; typology/water datum unresolved. (proposed)
Decision queue & Friday return
Which landing endpoints are canonical?
Owner: Legend. Resolution evidence: Accepted map-aligned endpoint list.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/ASSET_BRIEF.json
- production/assets/structures/PI-STR-0002-V01/BUILDING_DIMENSIONS.json
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Do steps/apron remain or does vehicle road continue?
Owner: Legend + Quik. Resolution evidence: Selected circulation plan and separation review.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/ASSET_BRIEF.json
- production/assets/structures/PI-STR-0002-V01/BUILDING_DIMENSIONS.json
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Where do ramps attach and what grade/accessibility applies?
Owner: Legend + Quik. Resolution evidence: Approved connection section and measured path.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/ASSET_BRIEF.json
- production/assets/structures/PI-STR-0002-V01/BUILDING_DIMENSIONS.json
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Which shoreline/datum meets landing?
Owner: Legend + Quik. Resolution evidence: Accepted shore detail and datum.
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/ASSET_BRIEF.json
- production/assets/structures/PI-STR-0002-V01/BUILDING_DIMENSIONS.json
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
Friday: requires decision
- Landing endpoints, step/road choice, ramp path, shoreline type/datum.
- Foundation hold release before geography connection.
Friday: return evidence
- Editable interface blockout and route alternatives.
- Plan/elevation/section/joint views.
- Endpoint/transform register with unknowns.
Downloads & source inventory
README and JSON retain repository-relative source paths. Use the linked inventory here when reviewing downloaded copies.
Source inventory
- docs/current-decisions.md
- production/assets/structures/PI-STR-0002-V01/ASSET_BRIEF.json
- production/assets/structures/PI-STR-0002-V01/BUILDING_DIMENSIONS.json
- production/assets/structures/PI-STR-0002-V01/REFERENCE_INDEX.csv
- production/assets/structures/PI-STR-0002-V01/VISUAL_NOTES.md
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.csv
- production/districts/D02-CrownKey/planning/BUILD_REGISTER.json
- production/districts/D02-CrownKey/planning/prep/R01/ASSET_INPUTS_B.json
- production/districts/D02-CrownKey/planning/prep/R01/KIT_CATALOG.json
- production/handoffs/quik/2026-10-16/crown-landmark/R01/COORDINATION/PROTOCOL_SOURCES/Building_R05_GUIDE.md
- production/protocols/building/R05/README.md
- production/protocols/current.json
- production/protocols/district/R04/templates/CONNECTIONS.json
- production/protocols/district/R05/README.md
- production/workflows/spatial-imagery/R01/GUIDE.md
