A clause becomes a clock. The clock asks a person. The register keeps the proof.
Demiton fills your registers from the systems you already run, in a published format. Each duty in your contract becomes a protection that guards it, and each protection runs on its own clock.
- ContractTMR TIC cl 35.5(a)
The clause sets a duty.
- ObligationNotify a possible delay in 10 business days
One duty, one window.
- ProtectionA watch, guarding Missed claims
It tracks the window from the day it opens.
- Registercontract_notice
The record the notice is kept in.
- SystemThe system a customer already runs
Systems fill the register.
Read left to right for what Demiton does. The last step points back, because systems fill the registers.
Contracts come in.
Your contract and the law behind it are read into obligations: each one a duty with a window, a consequence and a clause to point at.
Obligations meet protections.
A protection is one of four kinds, and each guards one obligation against one disease. Three clauses from three sources, each landing somewhere different:
- TMR TIC cl 35.5(a)
Notify a possible delay within 10 business days
A watch guards Missed claims.
Miss it and the entitlement is barred.
Evidence register:
contract_notice - TMR MRTS50 cl 10.2
Notify a nonconformance within 1 working day of detecting it
A watch guards Rework.
Miss it and the contract is breached.
Evidence register:
safety_ncrApplies only where one of the clause’s listed triggers holds. Demiton does not collect this register yet.
- TfNSW TS 00088 cl 6.9
Record an inspection of each vehicle and plant item before it starts a shift
A check guards Lapsed compliance.
Miss it and the contract is breached.
Evidence register:
plant_prestart
Four kinds of protection
- Watch
A window opens when something happens, and the deadline is tracked.
- Check
Evidence that must exist is looked for.
- Countdown
A fixed date approaches, flagged at 90, 30 and 7 days with the renewal attached.
- Threshold
A measure is tracked against the line it must not cross.
Five diseases, caught where they start
- ReworkInspection and test results, NCRs, site inspectionsThe failed result reaches the person who can stop the next stage the day it lands.
- Missed claimsVariations, change events, progress claims, contract terms, site diaries alongside weather observationsThe notice is drafted, and the rain day claimed, before the window shuts while the ground is still wet.
- DisputesSite diaries, day works dockets, RFIs, contract termsA missing day's record is flagged while people still remember the day.
- Cost driftBudget against actual, by cost code, against the price you quotedDrift is flagged at AU$50K, not AU$5M.
- Lapsed complianceCertificates, insurances, prequalificationEvery expiry counts down at 90, 30 and 7 days, with the renewal attached.
Each protection runs on its own clock.
When a clock needs a person, it asks a named person for one of three things:
Read this
A protection sends a person a message: here is the notice, read it.
Decide this
A protection asks a named person for a decision, and records who made it.
Send proof
A protection asks a worker for evidence, and a photo counts only once a second person approves it.
Registers hold the facts.
A register is one kind of record kept in one agreed format. Every register format is published as JSON Schema.
Every register format, publishedSystems fill the registers.
Demiton reads the systems you already run. These are the connectors that are released today.
Field and workforce
Assignar
Hilti ON!Track
Finance and payroll
Xero
Employment Hero Payroll
Dynamics 365 Business Central
Documents and identity
SharePoint
Dropbox
Microsoft Entra ID
ExcelUploaded as a file
A kept dollar lands on the ledger.
When a protection saves money, the cash recovered is written to the catch ledger and signed off by the person who acted. Only cash recovered counts.
Start with the jobs you are running now.
Or tell us what you run and we will walk you through it.
Every fact keeps its source.
Each fact carries the date it landed, the system it came from and who or what produced it. When a fact changes, the old version keeps its history, and an answer in Claude or ChatGPT points back at the record.
Every job teaches the next. What the last job actually cost, which rates held, which site conditions drove a variation: the next estimate starts from what happened, not a blank sheet.
Every job leaves a trail. Civil Memory remembers it. Margins improve.
Ask Demiton over MCP