Lost SoulsCrown Key / preparation

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

Required exterior coverage

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.

PI-STR-0002-V01P1structureunset

Prepare now

Open source concept image ↗Bridge Landing concept reference
Existing concept reference; appearance evidence, not a measured layout or accepted build reference.

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.

Modeling sequence

  1. 01Register conflictsNo landing ID or position inferred.
  2. 02Block abutment partsVisual form review without fixed location.
  3. 03Diagram movementRoute/grade selected before layout.
  4. 04Test jointsEndpoint/datum agreed before assembly.
  5. 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.

ComponentRole and evidenceOpen questions
Curved abutmentPale sweeping face and stepped plinth.
source_notes
  • How does abutment align to accepted shore endpoint?
Apron/grade transitionTiled apron and steps in card; aerials read road-level.
source_notes
  • Are steps retained and how do pedestrian/vehicle paths divide?
End post/rail jointLit end post and bridge rail continuity.
source_notes
  • Which rail/lamp components continue and where terminate?
Switchback interfaceRequired creator route is not drawn on landing card.
source_record
  • Where does it attach and what grade/access envelope governs?
Shore/water interfaceMust meet a selected shore type and datum.
source_record
  • Which shoreline type and water datum are accepted?
Modeling sequence & review views
  1. Register conflicts

    Record landing discrepancies and card/aerial step ambiguity.

    Gate: No landing ID or position inferred.

  2. Block abutment parts

    Separate face, apron, steps, rail/post and road edge.

    Gate: Visual form review without fixed location.

  3. Diagram movement

    Separate road, pedestrian and switchback alternatives.

    Gate: Route/grade selected before layout.

  4. Test joints

    Show span and shore as detached components.

    Gate: Endpoint/datum agreed before assembly.

  5. Return evidence

    Plan/elevation/section/joint views; dimensions null.

    Gate: No placement/collision claim.

Required review views

Landing plan

Show apron and vehicle/pedestrian/ramp options.

Water-facing elevation

Show curved face, plinth and rail.

Landing section

Show deck/water datum and transition unknowns.

Span/shore joint axon

Show detached interfaces, no coordinates.

Shared kits & asset dependencies
Decision queue & Friday return

Which landing endpoints are canonical?

Owner: Legend. Resolution evidence: Accepted map-aligned endpoint list.

Do steps/apron remain or does vehicle road continue?

Owner: Legend + Quik. Resolution evidence: Selected circulation plan and separation review.

Where do ramps attach and what grade/accessibility applies?

Owner: Legend + Quik. Resolution evidence: Approved connection section and measured path.

Which shoreline/datum meets landing?

Owner: Legend + Quik. Resolution evidence: Accepted shore detail and datum.

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