It will not certify the same payment twice
Over-certification, double certification and overpayment are refused by the payment cycle itself, not caught by a report afterwards. A refusal arrives as a refusal, never as a zero.
Construction AI Operating System
You find out in month nine.
It started in month five.
A missed pay less notice makes the application payable in full. An extension of time you cannot substantiate is an extension you do not get. Margin erodes in the four weeks between the thing happening and the review that finds it. This platform computes all three on the day they happen — not at the month end.
One governed record from concept to the thirtieth year of operation, and every figure on it computed from that record rather than typed into it.
Real programme, real notices, real money, no signup. Or start free and book twenty minutes when you want somebody on the call.
- Concept
- Design
- Tender
- Construction
- Commissioning
- Handover
- Operation
One system across all seven, and the last of them runs for thirty years. There is no migration at handover because there is nothing to migrate to.
The console's shape, drawn rather than screenshotted, on the demonstration project's real name and value. The commercial and programme figures in it are an illustration — the seeded programme itself is one click away and every figure on it is computed from its own event chain.
Event catalogue805closed, versioned
API surface1219documented endpoints
Runtime dependencies0nothing to patch at 3am
HGCRA 1996 · s.111
The notice nobody was counting
On the demonstration project, application 3 goes in at £2,248,650. The valuation withholds £119,650 — handrail terminations not to detail, dewatering rates not agreed — and the pay less notice is served inside the window. The notified sum is £2,129,000, and the reason is on the record.
Serve that same notice two days late and the whole £2,248,650 becomes the notified sum, payable in full, whatever the valuation said. The QS finds out at the month-end review, three weeks later. The platform computes it the day the window closes, names the notice that established the sum, and states what has to be served next.
Those are the seeded demonstration project's own figures, not a customer's job, and you can open the cycle and read them. Put your own turnover into the arithmetic and it will tell you what one window is worth on your books — with no industry average anywhere in it, because we have not got one and would not print one if we had.
One person · one seat · any number of projects
Invite the whole job. Pay for the 10 roles that decide.
Of the 20 roles this platform grants, 10 hold authority — they approve money, baselines and contracts, administer people, or run the business. Those are what a package's seats are. The other 10 are participants, and a participant takes no seat at all.
- A project invitation never adds anybody to your paid seats. Site, quality, design, supply and supervision come on for nothing, whether they work for you or for one of your subcontractors.
- A Controller from another organisation arrives on their own licence. If their firm — or any company in their group — already pays for their seat, that seat travels with them onto your project. You are not charged a second time for a person somebody else is already paying for.
- Where they hold no licence anywhere, you decide. A Project Controller Pass opens Controller authority for that person on that one project, for as long as you set, at £40.00 a month. It is a purchase you make deliberately; nothing buys it for you.
- A regulator costs nothing, ever. Building Safety Regulator access is an obligation the asset owner carries, not a licence we sell — so it and the platform operator are the 2 roles that consume no seat on any package.
And the AI a guest runs is charged to whoever agreed to pay for it — their own organisation under a consented monthly limit, or you, once, on an authorisation you gave. Never both, and never silently.
It refuses
Every other platform in this market generates. The useful moments here are the ones where this one declines — because a document the system was willing to invent is a document you cannot stand behind.
It will not approve a plan with gaps in it
A Construction Phase Plan missing its judgement sections cannot be approved, and while it is unapproved the platform refuses to record an induction against it. The paperwork order is the safety order.
It will not sign in a name that is not competent
Six of the sixteen CDM documents need a principal contractor's appointed approver. Where nobody holds that duty, those documents sit complete and unsigned rather than carrying a signature the platform had to invent.
It will not spend on AI it cannot account for
No provider is called on an empty wallet, and no charge is taken without a ledger entry. Where a model is unavailable it falls back and says which one answered.
No agent decides anything
Of 81 agents, 2 may ever act without being asked — and only inside an envelope a person granted, with an end date, revocable, naming the exact commands. One files a tender return register; the other says the platform is unwell. Both carry a value ceiling of zero. Every other agent can only propose.
A decision is a state a model cannot reach
Governance events are marked closed to AI in the event catalogue itself, and an envelope naming one is refused when somebody tries to grant it. So a decision taken by a model is not a permission that was withheld — there is no path to it, whatever an agent or a future envelope attempts.
Every AI-written line says so
Narrative sections carry their author and whether a model or the local stand-in produced them. An assurance team asking who wrote the safety case gets a name, not a shrug.
It will not call prose a table
A bill's rows come off the PDF as rows, blanks kept blank and a wrapped description joined. Two columns of prose that happen to line up, or a heading beside a date, are refused as tables rather than read into a schedule as quantities nobody measured.
A standby will not extend the record
A second process following the record from Postgres answers every read and refuses every write by name — sign-in included — so two processes can never each hold a different truth. Promotion is a restart, and the database refuses a second writer rather than forking.
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
805 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.
Eight 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.
Executive
What across the portfolio needs a decision this week, ranked with the reason and the exposure behind it.
Stage 0 to year thirty, on one record
RIBA Plan of Work 2020 across seven gated phases, CDM 2015 duty documents that stop the job when they are unapproved, the payment statute, ISO 19650 suitability and the golden thread the Building Safety Act expects. Not a compliance checklist bolted on — the gates are what the platform refuses on.
- RIBA 0 · RIBA 1 Concept Establish the asset, its sector, its funding envelope and its governance. At least one scope package defines what is being built
- RIBA 2 · RIBA 3 · RIBA 4 Design Mature the design to the point where quantities can be measured and risk priced. Design maturity has been formally assessed for the package being priced
-
Procurement task bar
Tender
Price the work, test the market, adjudicate and award on evidence.
A tender estimate has been frozen before bid submission
An executed contract exists before construction begins -
RIBA 5
Construction
Build against a frozen baseline, with progress, cost and risk measured continuously.
An approved programme baseline governs the works
An approved cost baseline governs the works - RIBA 6 Commissioning Prove the asset performs as designed before anyone takes responsibility for it. Commissioning tests recorded and accepted
-
RIBA 6
Handover
Transfer a complete, evidenced asset — not a box of PDFs — to the operator.
Handover pack compiled and accepted by the receiving party
Asset register populated for operations - RIBA 7 Operations Operate at minimum lifecycle cost for 30+ years, on the same data spine. Runs for the life of the asset.
RIBA Plan of Work 2020, stages 0–7
Every stage maps onto one of seven gated phases, and a project cannot leave a phase until the gate is met. Design maturity is assessed per discipline at its RIBA stage, and the DESIGN gate refuses to open without one.
lifecycle/phases.ts — PHASE_GATES, evaluated on every advance; DesignMaturityAssessment carries a 0–7 stage per discipline
Not claimed — This platform is not a RIBA-certified tool and does not issue RIBA deliverables. Procurement is a gated phase here and a task bar there; the mapping says so.
Construction (Design and Management) Regulations 2015
16 duty document types, each with the sections the regulations require, drafted against the project's own record. Construction Phase Plan gates the construction phase: unapproved, the work cannot start.
domain/cdm.ts — CDM_DOCUMENTS with required sections and the approver role; the gate refuses an unapproved plan
Not claimed — Drafting a duty document is not discharging the duty. The dutyholder approves it, and the platform records who did and when.
Housing Grants, Construction and Regeneration Act 1996 (as amended 2009)
Due dates, payment notices, pay less notices and the notified sum, counted in days as the Act counts them. A missing payment notice makes the applied sum payable in full, and the platform says so before the date rather than after.
engines/maths/constructionAct.ts — statutory periods, with s.116(3) handled separately from service dates
Not claimed — It is not legal advice, and an adjudicator decides what a notice meant.
ISO 19650-2 information management
Every container in the common data environment carries a suitability code, and a code the standard does not define is refused. A drawing issued for comment is not a drawing to build from, and the record knows the difference.
domain/cde.ts — suitability refused with SUITABILITY_UNKNOWN
Not claimed — The platform does not certify a BIM execution plan or audit an organisation against the standard.
Building Safety Act 2022 — the golden thread
Every governance act is an append-only, hash-chained event with its author, its evidence and its correlation. The chain is verifiable by anybody holding the export, including after this platform is gone.
goldenthread/ — the chain; export/exporter.ts — a verifiable export; erasure keeps the safety record the Act requires
Not claimed — The Act places duties on dutyholders, not on software. This keeps the record they are required to keep; it does not make anybody a dutyholder or discharge one.
JCT 2016, NEC4, FIDIC 2017 Red Book, IChemE and MF/1
Obligations resolve to the clause that imposes them under the form the parties actually signed — notice periods, retention release, defects, extension of time, variations. Where a form has no equivalent clause the entry is absent rather than approximated.
engines/maths/contractClauses.ts — clause references per suite; an absent obligation is left absent
Not claimed — An amended standard form is the amendment, not the standard. A wrong clause reference is worse than none, because it gets quoted in a letter.
Enforced means the platform refuses the work without it — an unapproved Construction Phase Plan stops the construction phase, a design with no maturity assessment cannot leave design, a suitability code the standard does not define is rejected. Carried means the record is structured to the standard and a person still decides. Every line above is read from the module that implements it, so this page cannot claim a gate the platform has stopped enforcing.
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.
Why it exists
Built by someone who spent years working without it
CONSTRUX comes out of Justin Nseya's years as an MCIOB construction professional and senior project-management leader — and out of the same failure, met on project after project.
Design, programme, cost, procurement, contracts, delivery, commissioning and handover were each managed competently, and each in a different system. Every one of them was fine on its own. What did not exist anywhere was the join — so information arrived late rather than missing, risks were found after they had already become variations, and the most expensive people on the project spent their time chasing updates instead of controlling delivery.
That is not a people problem and no better version of any one of those systems fixes it. It is structural: there was nowhere that recorded what happened once, at the moment it happened, in a form every discipline could read.
If we disappeared tomorrow, you would keep the evidence
That is not a reassurance. It is three properties of the record, and you can test all three before you pay us anything.
- Every export leaves whole. Branded, hashed and recorded, in PDF, Word, JSON or CSV. Nothing about a document depends on this platform being reachable to read it.
- Every document proves itself without us — to a stranger. A content hash proves nothing on its own: whoever alters a document recomputes it. So each one carries a verification code only this platform can produce, and anyone holding the document can check it with no account and no relationship to you. A client's solicitor. An adjudicator. An insurer.
- The log verifies on its own terms. Replay every event, recompute the chain, and a single root hash falls out that any party holding the same log can reproduce. That check does not run here — it runs wherever the log is.
Which is also the answer to the question behind it: an evidence trail whose truth depends on the supplier still trading is not an evidence trail. It is a subscription.
Start with a record you can defend
A trial governs, records and computes. No card, no call, no sales qualification step.