Offline site records that survive no signal
What offline site records looks like on a governed record, and the checks a reader can run for themselves.
Offline site records is the kind of thing a construction project usually argues about after the fact, from memory, with the evidence spread across inboxes and spreadsheets. CONSTRUX treats it as a record: every change to it is an append-only, hash-chained event on the golden thread, written before it is acknowledged, so the question "what did we know, and when" has an answer rather than an opinion.
Where it goes wrong
The failure is rarely a missing number. It is a number that exists in three places and agrees in none of them — the site diary, the commercial report and the board paper each telling a slightly different story about offline site records, with nobody able to say which was true on the day it mattered. By the time the disagreement surfaces it is a dispute rather than a decision, and a dispute is priced by whoever kept the better record.
How CONSTRUX handles it
Site records that survive no signal. Daily records, weather, labour, plant and progress captured offline and reconciled on reconnection — device timestamps preserved, duplicates refused by operation id, conflicts resolved the same way every time. A register of plant on hire, with utilisation and standing cost derived from the diary rather than entered twice.
A Golden Thread that detects its own tampering. Every state change is an append-only hash-chained event, journalled before it is acknowledged and shipped to Postgres behind that, where a standby can follow it live. Replay reconstructs the project from its own history and reports a root hash — so "has this record been altered" has an answer, not an opinion.
Ask the project a question in plain English. The copilot routes your question to the engine that can answer it and shows the records behind the answer. Where it cannot answer, it says so rather than inventing a number.
A record you can replay is a record you can rely on.
What you can check for yourself
None of this asks for trust. Replay reconstructs a project from its own history and reports a root hash; a document issued from the platform carries a content hash that lets anybody verify a document against what was issued; and every AI-assisted step names the engine that produced it and the records it read. If offline site records matters on your projects, the demo environment runs the whole cycle on a seeded programme — open it, run it, and read the record it leaves behind.
See the record being made rather than described.
Launch the demo environment