CONSTRUX
Construction AI Operating System

The record of how your asset
came to exist
.

One governed spine from concept to the thirtieth year of operation. Every state change is an append-only, hash-chained event. Every figure is computed from the record rather than typed into it. Every claim on this page is checkable by replaying the log.

Concept
Design
Tender
Construction
Commissioning
Handover
30-yr O&M

One system across all seven. No migration at handover, because there is nothing to migrate to.

191event types, closed catalogue
285API endpoints
177communication events
0runtime dependencies

Not a document store with a search box

Three things separate a record that survives a dispute from a folder that does not.

01

Nothing is edited in place

A correction is a new event and the original stays visible. Each event carries the hash before, the hash after, and a chain hash over its predecessor — so an insertion, deletion or alteration anywhere changes every hash after it and the state root along with them.

02

The catalogue is closed

191 event types and no others. An event nothing can emit is a capability that does not exist, and a test fails if one appears. That invariant exists because a control standard once reported a missing site diary on every project — with no command able to write one.

03

Replay is the proof

Rebuild every entity from the log alone, verify each event independently, emit one root hash any party holding the same log can recompute. Where your policy withholds a record, the redaction is reported and the root still covers the complete record.

Seven engines, real arithmetic

Not summarisation over your documents. Forward and backward pass, expected value, statutory date reckoning — computed, deterministic, and the same answer twice.

Programme

Critical path, float and PERT probability. Monte Carlo completion, corrected for merge bias.

Commercial

Earned value with three EAC scenarios, CVR with margin erosion, S-curve cashflow.

Contracts

The Construction Act position — which notice established the notified sum and what a missed one cost.

Risk

Expected value, P80 contingency, and thresholds proportionate to the contract rather than fixed.

Quality

Inspection and test plans with acceptance criteria, hold points witnessed rather than asserted.

Design

Revisions, clash closeout with evidence, and clause extraction from the specification as supplied.

Operations

Reliability-adjusted maintenance forecasting against the asset the record actually describes.

HGCRA 1996 · s.108 · s.111 · s.116

The statute that decides who gets paid

If the payer gives no payment notice and no pay less notice, the sum applied for becomes the notified sum and is payable in full, however optimistic the application was. The platform computes that position rather than describing it: which notice established the notified sum, what a missed or invalid one has already cost in money, whether the right to suspend is open, and what has to be served next.

A term the Act makes void is replaced by the Scheme whether anybody noticed or not — so a contractor who priced for a payment period the Act strikes out has priced for a cost he does not carry. A term that is merely onerous is lawful, and stays his problem. The platform tells the two apart.

And it invents nothing. Statutory interest runs at base rate plus 8%; the base rate is a fact about the outside world this platform is not connected to, so the entitlement is stated and the amount is not.

Start with a record you can defend

A trial governs, records and computes. No card, no call, no sales qualification step.