AI that fails offline is not construction software
Sites run on unstable connectivity and harsh conditions, so an AEC frontend must be a project control instrument for versions, approvals, sync and conflict — not just a screen. Offline data is a working copy, not official truth, and conflicts are handled by type and escalated, not merged.
This is the final piece in the three-part series 'AEC AI IS NOT A MODEL PROBLEM' by Youngtae Kim, CEO of doAZ. It defines the AEC frontend not as a mere screen but as a project control instrument that ties versions, approvals, synchronization and conflicts to action in the field. The discussion moves through site operating conditions, performance priorities, offline-first design, the handling of semantic and permission conflicts, the interface as governance, UX fitted to the human body, closed-loop data flow and field-centered testing, and arrives at the real stack of AEC AI — the Control, Context, Execution and Assurance Planes.
The full original article follows below.
전체 문서AI that fails offline is not construction softwareOpens the full article in a new window (Korean)열기 →We run a verification demo on one real set of your drawings.
Request a verification demo