How your registers become one record

Every job leaves a trail. Civil Memory remembers it. Margins improve.

Civil Memory is the heart of Demiton. It is one continuous, sourced record of a civil job across its whole life - from the moment it appears in a government forward programme, through the open tender, to the award, into delivery on site, and back out as structured reporting to the government client. Everything else in the platform is a way to feed that record or a lens onto it.

This is the mechanism behind the five diseases that erode margin: a fact caught late costs money, a fact in the record the moment it happens doesn’t.

---

One continuous story

Most construction software treats the public market and your own delivery as two different worlds. Demiton treats them as one life, joined at the award.

   PUBLIC MARKET                  THE SEAM                 YOUR DELIVERY
   planning -> tender -> award  ──►  you win  ──►  deliver -> close out

• Before the award you are watching and pursuing public work - planning notices, open tenders, who won what. This is the Market surface.
• The award is the seam. A public contracting process becomes your private delivery project. Linking the two runs through the project-contract-link API today; the in-app declare-win flow is still to come.
• After the award you deliver the job, reading from your own systems - ERP, field ops, payroll, documents.

Civil Memory is the only place that draws the whole line. It is where you see a pursuit go from “spotted in the pipeline” to “delivered and closed out,” with every fact attributed to where it came from.

Standards underneath

Under the hood, the public half is the open OCDS standard (contracting processes) and the delivery half is OC4IDS (infrastructure projects). You never have to read a standard - they run underneath as the credibility engine. “Civil Memory” is how the work is actually used. See Conformance for how the platform guarantees it.

The seam and OC4IDS today

The award is the seam: a public contracting process becomes your delivery project. Linking the two is implemented on the backend - the project-contract-link API moves a link from pursuing to won - but the in-app declare-win flow is still to come.

OC4IDS emission is in the same state. The platform stages an OC4IDS payload for review and stops there; nothing is published to a government client. The consent model exists, but the emission path that would call it does not, and it is not on the roadmap. The declare-win flow is still to come.

---

Why it compounds

Civil Memory is not a search index of documents. Each fact is a typed, time-valid record, attached to the canonical entity it is about - a worker, a project, an asset - and carrying a citation back to its source. Records accumulate and supersede rather than overwrite, so the history is never lost.

That is why memory compounds. Every reconciliation, allocation and form submission adds to the record, and because records supersede rather than overwrite, the history is never lost. What accumulates is specific to how your organisation runs work - your rates, your crews, your ground conditions, your subcontractors - so it is not something a competitor can copy from public data or a product demo.

See Memory for the full model - entity anchors, memory types, ACLs, entity briefs, and the knowledge graph.

---

You reach it chat-first

You do not learn a new dashboard to use Civil Memory. You ask for it, in the AI client you already use, through Ask Demiton. Open Claude or ChatGPT and ask “where did my labour rates hold last year?” or “who won the contract we lost on the Pacific Highway, and at what price?” - the answer comes back sourced, identity-filtered, and attributable.

The web app at app.demiton.io is where you configure systems, review the audit trail, and work the surfaces directly. The day-to-day questions happen in your AI client.

---

The surfaces are lenses on memory

Demiton is six surfaces. Five live in the app; one is the external door through your AI client. Each one either feeds Civil Memory or reads from it.

The surfaces are lenses on memory

Surface	What you do there	Relationship to memory
Studio	Ask, in the app, and get sourced answers and reports	Reads memory; runs reports over it
Market	Discover and pursue public work	Feeds the public half of the spine
Protection	See the five diseases that erode margin, and the project board under cover	Reads the registers the diseases fire on
Memory	See the whole sourced story - the seam where a public award becomes your delivery project	Civil Memory itself
Agents	Run scoped tool loops that propose config or produce artifacts	Reads memory; producer agents write reviewable output back
Ask Demiton	Use Demiton from Claude, ChatGPT, or your IDE	Reads memory over the open MCP standard

The former Prequalification and Projects surfaces were retired into Protection in September 2026.

---

Tiers are how far along the life you reach

Demiton’s tiers map to lifecycle reach, not company size. Memory deepens as you move along the spine.

Tiers are how far along the life you reach

Tier	Lifecycle reach	What lights up in memory
Public	Watch and pursue the market (free)	The public record: planning, tenders and awards
Baseline	Deliver won projects from live systems	The delivery half - your uploaded history and live operational memory
Enterprise	Portfolio	The full spine across every entity

---

Next steps

• What is Demiton - the platform in full, and how the tiers fit together
• Quickstart - sign up, ask your first question, connect a system
• Memory - the detailed memory model
• Ask Demiton - connect Claude or ChatGPT