Evidence before conclusion
If the system cannot cite the record behind a claim, it does not make the claim. This is an architectural constraint, not a prompt instruction.
OneAI Construction is a OneAI Labs product focused entirely on construction and infrastructure — the sector where coordination failure is most expensive and least visible until it is too late to absorb.
The industry has spent two decades digitising documents and is still surprised by delays that were visible in its own records weeks earlier. The problem was never a shortage of data. It was that no system held the project as a single coherent object — geometry, time, evidence and decisions in one place, connected well enough to reason over.
Every project already contains the signal. A delivery record moves, an inspection is deferred, a crane is reallocated. Those facts exist, in systems that have never been introduced to one another, and by the time they converge into a monthly report the decision window that could have absorbed them has closed.
We think the right response is an intelligence layer: something that understands project context, preserves evidence, reasons about risk with its sources attached, and coordinates action under explicit human control. Not a chatbot over a document store, and not another silo asking teams to enter the same data a fourth time.
That is the whole company. Two products — Construction OS and Construction Twin — built on one Project World Model, deployed one project at a time against a success test we agree before we start.
These constrain the roadmap. When a feature request conflicts with one of them, the principle wins.
If the system cannot cite the record behind a claim, it does not make the claim. This is an architectural constraint, not a prompt instruction.
AI recommends. A named person approves anything consequential, and the approval is recorded with the evidence that was visible at the time.
Foundation models will keep changing. The semantic representation of your project is the durable asset, so we keep the model layer replaceable.
Capital projects run on systems that work. We are the layer between them, not a proposal to rip them out.
Pilots have success tests agreed in writing before work starts. When a test fails, we say so.
On projects where decisions get examined years later, the audit trail is not compliance overhead around the product. It is the thing being bought.
The most useful first conversation is about a decision you are struggling to make on a live project — not a feature list.