The agent records the specification, the material data, and the approval basis behind a design or substitution decision.
Verifiable AI for construction.
Every compliance decision attached to the building’s digital twin.
Building records are still largely paper-based and scattered across contractors, owners, and regulators. nOS attaches every compliance decision, material origin, and emissions record to the building digital twin, so context persists across the full lifecycle. Trace Labs contributes to initiatives such as the EU Digital Building Logbook to make construction compliance verifiable end to end.
What gets captured
Shared & Verifiable
Working memory captures private agent reasoning. Shared memory is where multi-party context coordinates. Verifiable memory is where decisions are enshrined.
EU Digital Building LogBook
Real enterprise data, processed in production, with decision traces enshrined as Knowledge Assets in the OriginTrail DKG.
The case for verifiable decisions in construction.
A building outlives every contract that produced it. Design decisions, material substitutions, and compliance sign offs are made by contractors and consultants who disperse at handover, leaving an owner with drawings that do not explain why the built asset differs from the design.
Reporting has caught up with that gap. CSRD disclosure and the EU Digital Building LogBook expect evidence about materials and performance across the asset lifecycle, which is difficult when the reasoning behind each substitution was never recorded in a form anyone else can check.
How a decision becomes verifiable.
Context the owner, contractor, and certifier are entitled to see moves into shared memory, so the as built record is assembled continuously rather than at handover.
Substitution and sign off decisions record their reasoning, including the standard applied and the party who accepted the deviation.
The trace is enshrined in the DKG and attaches to the building’s digital twin, so the reasoning survives the contract that produced it.
What this changes in practice.
The change is that the as-built record assembles itself. Rather than a handover package compiled at the end by whoever remains, each substitution and sign-off is recorded with its justification as it happens, so the owner receives reasoning rather than only drawings.
For the asset owner this compounds across the lifecycle. Refurbishment, resale, and disclosure all depend on knowing what was actually built and why, and that knowledge currently degrades every time a contract ends.
Questions about construction.
What problem does this solve at handover?
How does this support CSRD reporting?
What is the EU Digital Building LogBook connection?
Does every subcontractor need to participate?
Who benefits most, the contractor or the owner?
Does this require BIM?
Power up your business with the OriginTrail DKG.
Create Knowledge Assets, build shared context graphs, enshrine decision traces. Open-source infrastructure. Community support. Zero cost.
The full Network Operating System.
Custom agent frameworks (Hermes, OpenClaw, LangChain, Claude). Custom data pipelines. Custom integrations with your enterprise systems. Dedicated infrastructure and support.