AICAD Studio

1. 01

   Fully localised interface

   ▣BUILT

   Ships in English and Vietnamese. The Vietnamese edition carries 2,030 AICAD-authored strings across 9 UI contexts with none left untranslated — a complete localisation rather than a partial one, and the same depth every additional language is held to.

   Evidence src/Gui/Language/AICAD_vi.ts — 20,543 lines; 2,030 messages across 9 AICAD contexts, 0 marked unfinished

   Detail · Chapter 06 →
2. 02

   Building-code advisory screening

   ▣BUILT

   Egress, accessibility and noise are screened against the loaded regulation pack, with clause-level citations shown in the application. The Vietnamese packs — QCVN 06 egress, QCVN 10 accessibility, QCVN 26 noise — are the most complete today; US IBC 2021 and UK ADB 2019 packs ship alongside them.

   Published limit

   Advisory screening only. Not a certified fire-safety or accessibility assessment, and not a substitute for statutory review.

   Evidence src/Mod/AIArch/aiarch_core/lifesafety_compute/ — 3,152 lines; native panel wired at src/Gui/AICADPanels.cpp:30570-30700

   Detail · Chapter 02 →
3. 03

   8 versioned regulation packs

   ▣BUILT

   QCVN 01:2021, TCVN 4470:2012 (hospitals) and TCVN 8793/8794:2011 (schools) verified, alongside IBC 2021 and ADB 2019 packs.

   Published limit

   The QCVN 06:2021 pack is still marked draft and awaiting review.

   Evidence src/Mod/AIArch/Resources/config/regulation_packs/ — 8 packs, validated by regulation_pack_validator.py

   Detail · Chapter 02 →
4. 04

   AI cannot change your model without approval

   ▣BUILT

   25 AI tools across 6 safety levels, with exactly one permitted to mutate the model — a constraint the build enforces automatically rather than by convention.

   Evidence aiarch_core/llm_backend/ai_agent_tool_registry.py — 25 tools, levels L0-L5, single mutating tool engine.approve.apply; aiarch_core/interop/formats.py validate_interop_advisory_plan() fails any plan whose approval flags drift

   Detail · Chapter 03 →
5. 05

   AI is optional — the CAD runs offline

   ▣BUILT

   With no model installed the CAD/BIM core still runs in full. No network connection is required, and no drawing has to leave the machine.

   Evidence model profile catalog install_default = 'disabled'; interop runtime declares model_required=false, offline_safe=true, network_access_required=false

   Detail · Chapter 03 →
6. 06

   AutoCAD-style command line

   ▩BOUNDED

   461 commands and 16 system variables, typed the way AutoCAD users already type.

   Published limit

   Of the 461: 105 native, 134 bridged, 44 emulated, and 153 catalogued but not yet independently verified.

   Evidence packaging/aicad/aicad_command_reference.json — command_count=461, system_variable_count=16, SHA-pinned from 10 sources

   Detail · Chapter 04 →
7. 07

   Drawing, modelling and documentation in one application

   ▩BOUNDED

   An 18-tab ribbon across 60+ command groups, around 20 always-available panels and 26 that appear in context — so moving from a drawing to a model to an issued set never means opening a second program.

   Published limit

   The most recent interface review found content clipped in all 19 panels it checked. Remediation is in progress.

   Evidence DESIGN_SPEC.md; src/Gui/AICADShellRibbon.cpp — 85 tracked files, ~138,000 lines

   Detail · Chapter 01 →
8. 08

   Reads DWG across 8 AutoCAD generations

   ▩BOUNDED

   Detects and reads AC1015 through AC1032, cross-checked against the independent LibreDWG decoder.

   Published limit

   A clean-room reader, not built on an Autodesk or ODA SDK. DWG writing is currently R2000 only, with a bounded entity set. No guarantee of exact round-trip fidelity.

   Evidence aiarch_core.interop.dwg_reader; validated against the GNU LibreDWG oracle (formats.py:711,836)

   Detail · Chapter 05 →

This table records evidence level, not commercial readiness. No row here is a promise about a release date, and no row is a usage metric.

This is a filtered view. The claim record also holds capabilities that exist in the source but do not yet carry enough evidence to publish; they are excluded from this table and are not described as features anywhere on this page. The filtering is enforced by an automated check, not remembered by an author.

Shell anatomy, top to bottom

The names set in mono are the real object names in the interface source, not labels invented by this page.

1. QMenuBar

   The persistent menu bar, ending in the AICAD Mode entry.

2. AICAD_ModeSwitcher3 làn · 19 module

   Three working lanes — CAD Familiar, AI Design Studio, BIM Review — plus an Environment pill and 19 module launcher buttons. Switching module changes mode in place: no window closes and the window size is preserved.

3. AICAD_CommandCortexBar

   An intent field alongside a strip of context chips: route preview for the command, its source, its state, the lane, the layer, the bias, the DWG fidelity, AI and hatch. Chips that overflow fold into a chevron.

4. AICAD_DynamicCommands18 tab · 60+ nhóm

   The multi-tab command surface, filtering over 60+ command sections. Related commands collapse into split-button dropdowns. Picking a lane in the row above switches to the matching tab.

5. Dockstrái 210–300 px · phải 310–430 px · dòng lệnh 68–126 px

   Left: the Tool Palette at roughly 54% height, with Layers/BIM below it at a 220px minimum. Right: Smart Properties, a scrolling inspector. Bottom: the AICAD command line.

6. MDI

   The central document area: a Command Center tab as the starting surface, alongside AICAD model viewports.

7. AICAD_CADStatusBar

   Prompt feedback, plus Grid, Snap, Ortho, Osnap, the current layer, the scale, viewport badges and the two Zen / Max switches.

DESIGN CONCEPT

Enlarge

The layout studied for the shell: command band on top, layer tree to the left, viewport in the centre, property inspector to the right, command line along the bottom. That structure is what has been built; the presentation in the drawing has not.

Every number, file name and percentage inside the image is placeholder content built for the design study. None of it is a measurement of the product, and none of it should be read as data.

The ribbon: 18 tabs, and one fail-closed replacement set

In the CAD Familiar lane the ribbon carries 17 fixed tabs plus a contextual tab named modules — it appears only while a module is open and holds that module’s tools. Eighteen in total. The section-to-tab map lives in the source, not in a configuration file editable at runtime.

This is the shell’s navigation, not a list of published capabilities. The capability register at the top of this page is the only authority on that: a discipline layer without enough evidence is absent from the register whether or not the shell has a tab leading to it.

DESIGN CONCEPT

Enlarge

A multi-tab ribbon and a command line inside one frame — the arrangement the tab list above describes. The tab count and tab names in the picture are the study’s, not the current set; the current set is the list immediately above.

Every number, file name and percentage inside the image is placeholder content built for the design study. None of it is a measurement of the product, and none of it should be read as data.

Panels and docks

Around 20 always-available panels are registered, four of which are visible the moment the CAD Familiar lane opens. Beyond them are 26 panels summoned by context — the design contract names 22 of the 26, and these are those 22 names.

Three viewport focus modes

Pressing the active mode again returns to Normal. Switching working lane also resets to Normal. On exit each dock’s visibility is restored exactly as it was, rather than rebuilt from defaults.

Three checks, with the citations taken from the source

• QCVN 06▤Advisory screening

  Egress

  Occupant load by use, required exit count and egress width, travel distance measured by grid geodesic rather than straight line, and vertical egress for multi-storey buildings.

  Source: aiarch_core/lifesafety_compute/egress.py

• QCVN 10:2014▤Advisory screening

  Accessibility

  Barrier-free dimensions: ramp slope and run, landings, clear widths, doors. Every finding carries its clause reference, written in Vietnamese.

  Citation as the product emits itQCVN 10:2014 §2.2 đường dốc

  Source: aiarch_core/lifesafety_compute/accessibility.py

• QCVN 26▤Advisory screening

  Facade noise

  Facade noise mapping built on the multi-octave ISO 9613-2 propagation model, checked against the QCVN 26:2010/BTNMT limit at the receiving facade, floor by floor.

  Source: aiarch_core/environmental_compute/acoustics.py

Eight versioned regulation packs

Each pack is a versioned data file, and each file carries its own verification-status field. The table reads that field directly — nothing rounded, nothing merged.

The four packs still marked draft are published as draft, the fire-safety pack included. An unreviewed dataset presented as reviewed is the most dangerous thing code-checking software can do.

Evidenceaiarch_core/lifesafety_compute/ occupancy · egress · egress_code_checks · vertical_egress · accessibility5 modules · 3,152 lines

Four flags a machine checks, not four flags engineers remember

Every emitted plan carries the four flags below. validate_interop_advisory_plan() fails the plan if any value drifts from the preview-before-apply contract — along with the nested contracts for the approval boundary, the rollback plan and the runtime.

aiarch_core/interop/formats.py — validate_interop_advisory_plan()

AI is optional. The CAD does not depend on it.

No model is installed by default

The AI engine ships with install_default = disabled, and declares required = false.

No network required

The runtime contract declares model_required = false, offline_safe = true, network_access_required = false. Your drawing never has to leave the machine.

21 engines registered in the core

AICAD computes in these engines, not inside a language model.

Three command surfaces, not one

• The command line

  A fixed bottom dock, 68–126px tall. Type a command name or an alias, read the prompt, and see the command history in place.

• Command Cortex

  An intent field at the top of the shell with route-preview and source chips — you see which command is about to run before it runs, and where it came from.

• The AIArch Python surface

  184 invocable names resolving to 121 canonical commands across 6 groups. This name set does not intersect the command catalogue (0 shared names), so the two are separate surfaces rather than one total added up to look larger.

DESIGN CONCEPT

Enlarge

The study for the intent field: command proposals carrying their own shortcuts, and a synonym list so someone who knows the old command name still finds the new one. The proposal mechanism is what is being built; the numbers and labels in the picture are not.

Every number, file name and percentage inside the image is placeholder content built for the design study. None of it is a measurement of the product, and none of it should be read as data.

The command catalogue, including the unverified part

The reference lists 461 commands: 106 built natively in AICAD, 185 reaching their behaviour through the inherited runtime (bridged, routed or emulated), 153 catalogued only, and 17 published boundaries — retired commands, commands needing a licensed adapter, commands out of scope.

106

native

185

through the inherited runtime

153

catalogued only

17

published boundaries

16 tracked system variables, each carrying its own status.

The full table is directly below: searchable, filterable by status, and every row records what the product’s registry records. This is where you look up the commands you type every day.

DWG — said carefully, because it is the easiest place to overpromise

AICAD reads DWG through a clean-room decoder AICAD wrote, independently cross-checked against the GNU LibreDWG oracle. No Autodesk SDK, no ODA SDK — so no SDK fee is passed on to you, and there is no native parity to promise either.

DESIGN CONCEPT

Enlarge

The study for the importer: seven steps from file scan to commit, a split view comparing source against converted result, and a fidelity report broken out by item — including the line stating that native DWG support is off.

Every number, file name and percentage inside the image is placeholder content built for the design study. None of it is a measurement of the product, and none of it should be read as data.

The import fidelity report

The importer scores fidelity item by item rather than emitting one number, and it keeps the layer, block, xref and font/style mapping so the next import can reuse it. The items scored:

• geometry
• layers
• blocks
• xrefs
• AEC objects
• dimensions
• materials
• properties
• round-trip status

Counted

2.030

interface strings authored by AICADsrc/Gui/Language/AICAD_vi.ts

9

interface contexts coveredAICAD_vi.ts — contexts

0

strings still marked unfinishedAICAD_vi.ts — 0 unfinished

20.543

lines in the translation fileAICAD_vi.ts

Interface languages: VI · EN

The translation boundary, deliberate and reasoned

Visible captions are localised at render time. The routing keys underneath are not: object names of the form AICAD_RibbonSection_<key> stay English in every interface language. The practical consequence is that the command contract does not shift with the language — a macro, a script or a written procedure produced on a Vietnamese-configured machine runs unchanged on an English-configured one, and the reverse. For a bilingual practice that is the difference between usable and not.

Citations written in Vietnamese, where the work happens

The code-checking layer does not return an error code and leave you to look it up. It emits its citation in Vietnamese inside the application, in the shape below — which means the person reading the result and the person reading the regulation are the same person, reading the same language.

Stacked diacritics

Written Vietnamese stacks a tone mark above a vowel mark. At interface sizes this is where a typeface not drawn for Vietnamese breaks first — marks clipped, marks colliding with the line above, or marks crushed together. This is what the Vietnamese surface has to carry:

ế ữ ằ ẵ ộ ỹ

This specimen is set in the website’s typeface, not the desktop application’s. We do not publish the build’s typeface because there is no verification evidence for it.

Platform facts

Platform

Windows x64. No other platform build is published.

Licence

Closed-source commercial software, built on an inherited open-source CAD runtime. Full attribution and terms ship with the installer.

Project format

.aicad

Network requirement

The CAD/BIM core needs no network. Activation needs one sign-in.

AI

Optional. No model is installed by default; it runs in full with no model at all.

Price

Denominated in AICoin, the same wallet as the web applications. Detailed pricing is published when the beta opens.

Not published, and why

Nothing below has a measured receipt at HEAD. We leave it blank rather than fill in a plausible number, because a plausible wrong number is still a wrong number — and you would find out exactly when it costs you money.

• —Minimum CPU
• —Minimum RAM
• —GPU requirement
• —Install size
• —File size limit
• —Maximum model count
• —Release date
• —User, download or rating figures

When the evidence exists we publish the evidence first and the feature second. Never the other way round.