Architectural Set
The architectural set is the professional translation layer between the LDD bible and construction. It should make the design legible to architects, engineers, AHJ reviewers, GCs, and trades.
Target Sheet Index
| Sheet | Purpose | Primary LDD inputs | Status |
|---|---|---|---|
| A0.0 | Cover, project data, code basis, sheet index | Project Command, AHJ decisions | Red |
| A1.0 | Site plan and civil coordination references | Site + civil, structural | Yellow |
| A2.1 | Level 1 floor plan | LDD-01, 03, 10, 13, 14 | Yellow |
| A2.2 | Level 2 floor plan | Future Floor 2 LDD | Red |
| A3.0 | Elevations and exterior envelope | LDD-11, 16, 17 | Yellow |
| A4.0 | Sections: spine wall, gym, south bay, ceiling hierarchy | LDD-03, 04, 12, 13 | Yellow |
| A5.0 | Interior details: doors, stairs, social counter, finishes | LDD-18, 19, 20, 24 | Draft |
| MEP | Mechanical, electrical, plumbing, radiant, ERV/venting | LDD-02, 05, 06, 07, 08, 09, 10 | Red |
Package Logic
LDDs define intent
The LDDs should answer why a design choice exists and what cannot change without breaking the concept.
Drawings define geometry
Architectural sheets should turn intent into dimensions, details, assemblies, schedules, and permit-reviewable scope.
Engineers define performance
Structural, MEP, radiant, envelope, and civil drawings need stamps and calculations where the LDDs are only design intent.
Project Command defines priority
Open conflicts between LDDs and drawings should be routed through the command dashboard before changing the bible.
Next Upgrade
Create the first clean architectural index once AutoCAD or another CAD tool is connected. Each exported PDF/SVG sheet should get a stable link here and a matching source entry in CAD exports.