Registers
Every one of the five diseases starts as a fact on a register: the failed test result, the variation notice, the missing diary day, the budget line drifting from the tender, the certificate expiry. Demiton catches a disease where that fact lands, so the register is where prevention happens. All registers groups them by the disease they feed.
A register is what you’re actually asking for. Every kind of record in Civil Memory - a site diary entry, a safety incident, a budget line, a supplier rating - is kept on a register. It is the same idea as the plant register, drawing register or NCR register a contractor already keeps: one kind of record, in one agreed format.
A register holds what happened; an obligation is what a job owes. The deadline a protection watches comes from an obligation, and the fact that shows it was met lands on a register. The obligations themselves are public, one file per Act, contract form or specification, in the obligation library on GitHub.
When you ask a question through Studio or Ask Demiton, you’re naming a register: “safety incidents,” “budget vs actual,” “site diaries.” You don’t need to know, or care, which system produced the underlying record. Every register has a published contract that says what one record on it holds.
Why the register, not the system
Section titled “Why the register, not the system”Before this model existed, a request named the pipe that wrote the data, not the record it produced. That worked as long as one register had one writer. It broke as the platform grew for reasons that show up as real product limits if left unfixed:
- More than one system can feed the same register. If your organisation runs Business Central for one contract type and Xero for another, “job cost elements” should mean the same thing regardless of which ERP produced it. A request that names the writer instead of the record can’t express that.
- Delivery is a server decision, not a caller decision. Whether a fact is served from a cache, computed live, or read straight off a table shouldn’t change what you ask for.
- The name should describe the record, not the plumbing. “Safety incidents” is what you mean. The mechanism that got the incident into memory is an implementation detail.
A register is deliberately not the same thing as an ingest group - the pipe that writes to it. Keeping the two separate is what makes both problems solvable independently.
Next steps
Section titled “Next steps”- Register catalog - every register, grouped by domain
- Register contracts - the fields, requiredness and an example record for each register
- Ingest groups - the pipe that fills a register
- Obligations - the duties a protection holds a job to, and the public library they come from
- Agents - agents read registers the same way Studio and Ask Demiton do
- How your registers become one record - the record registers are drawn from
Frequently asked questions
- What is a register in Demiton?
- A register is one kind of record Demiton keeps in Civil Memory, such as site diaries, safety incidents, or budget lines. It is the same idea as the plant register or drawing register a contractor already keeps: one kind of record, in one published format. When you ask Demiton a question through Studio or Claude, you are naming a register. The server decides which connectors and computations feed it.
- Why do some older integrations say shelf?
- Shelf is the earlier name for a register. The API and the MCP tools are moving to register, including the register parameter on Ask Demiton, and the older shelf parameter still works and returns the same answer. A register ID and a shelf ID are the same value.
- What happened to the term Capability in Demiton?
- Capability has been retired as public-facing terminology. What used to be described as a single capability is now two separate things: a register (the record you ask for) and an ingest group (the pipe that fills it, previously called a conduit). Old capability names still work as an alias - nothing that used to work has stopped working.
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.