Interop & AuthoringNo active project contextProject context required

CAD Studio

Use the CAD wrapper to normalize legacy drawing packets, but keep the project command center in the loop so intake, compliance, and capital handoff reflect the same working context.

Next action

Confirm the project command center before codes or permit handoff

Legacy CAD ingress is valuable early, but jurisdiction and downstream packet decisions should stay attached to the active project chain before operators rely on them.

Downstream packet impact

CAD ingress affects the project intake packet, jurisdiction evidence, and architecture handoff into later permit and finance surfaces. No project context keeps those packets provisional.

Active Project

Open next action Open project command center Open portfolio command center

Rapid AI Architect CAD

The next-generation CAD automation workspace is preparing for controlled rollout.

Jurisdiction Compliance Spine

Jurisdiction pending

Directives 0 · Permit docs 0 · Inspections 0

Spine Status

Spine pending

Select a project or jurisdiction.

Site Geometry

Boundary pending

Rows pending · Lots pending · Blocks pending

Verification Status

Pending

Awaiting compliance spine.

Live non-ICC sources: 0

Construction Ready

Pending

Construction-ready gate waits on compliance spine.

Trojan horse ingressODA canonical contract

Legacy CAD ingress

Upload DWG, DXF, PDF, and IFC artifacts here, normalize them into the ODA app-layer contract, and route them into live runtime import paths without bespoke per-page logic.

Runtime-ready

Need translation

Document packets

Select an active project first. This ingress layer persists artifact lineage and runtime candidates into project assets.

DWG / DXF

Bring in legacy CAD. DXF promotes directly, and DWG now attempts ODA-backed translation so it can land in the live runtime too.

PDF Packet

Capture flattened permit packets, spec books, and plan sets, then promote them directly into live evidence ingestion for the OS.

IFC Model

Preserve BIM lineage and promote the model directly into the current live BIM runtime for CAD operators.

Structured runtime candidates

Uploaded artifact lineage, normalization status, and promotion routes now all flow through one app-layer contract.

No legacy candidates yet. Upload a DWG, PDF, or IFC artifact and the shell will turn it into a structured runtime candidate.

Construction-ready gating is enforced by the compliance spine and non-ICC verification. When CAD launches, plans can generate in preview mode, but issue/submit remains locked until the jurisdiction is verified.

Need to verify a jurisdiction?Open Codes Verification

COMING SOON: Rapid AI Architect CAD

The next generation of procedural plan generation (Labs4 Engine) is currently in closed alpha testing.