Agents - scoped reasoning loops
Agents are scoped, budgeted tool loops that reason over Civil Memory and deliver a result on their run - either a citation-rich artifact or a proposed change to your organisation’s configuration. They sit alongside Workflows (deterministic verb graphs you configure once and run repeatedly) and Studio (ad-hoc chat): an agent is a bounded, purpose-built reasoning loop with its own budget and its own audit trail.
Find it at /agents in the app.
Two kinds of agent
Section titled “Two kinds of agent”Every registered agent declares which of two categories it belongs to. The split exists so that agents touching organisation-wide configuration are never trusted with a direct write - a human always reviews the change before it takes effect.
- Probe agents own one axis of your organisation’s configuration and propose it - they never write it directly. Every side effect lands as a pending approval in your approvals queue, and a probe can re-run itself when it detects drift. Example: a probe that infers which of your systems’ identities map to the same worker.
- Producer agents consume configuration you have already approved and write reviewable output - never silently finalised, always visible for review before it’s treated as fact. Examples: a measurement agent that verifies drawing quantities against a schedule of rates, or an agent that synthesises a cited tender launch brief.
For the underlying taxonomy - why the split exists and how it prevents unreviewed drift - see Agents under Concepts.
What will you find on the Agents surface?
Section titled “What will you find on the Agents surface?”/agents- the index. Every agent definition available to your organisation, grouped by probe or producer, with a strip of recent run activity./agents/:slug- an agent’s detail page. Overview (what it does, its budget, what it produces), Runs (its history), and - for probes - Proposals (its pending approvals)./agents/runs/:runId- a single run. Budget burned against budget allowed, a step-by-step timeline that surfaces failures first, and - for measurement agents - the source evidence behind the result.
How do Agents connect to the other surfaces?
Section titled “How do Agents connect to the other surfaces?”Agents read Civil Memory the same way Studio and Ask Demiton do, and measurement agents source the underlying documents the same way the platform’s own harvesters do. A probe’s proposals resolve through the same approvals queue as every other proposed change in the system - there is no separate approval mechanism just for agents.
Which tier includes Agents?
Section titled “Which tier includes Agents?”Baseline - the same gate as Memory. Agents require organisation configuration that only exists once your organisation is connected, so there is no Public-tier Agents surface.
Next steps
Section titled “Next steps”- Agents (Concepts) - the probe/producer taxonomy in depth
- Memory - what agents read from
- Studio - the ad-hoc alternative for a one-off question
Frequently asked questions
- What is the Agents surface in Demiton?
- Agents are scoped, budgeted tool loops that reason over Civil Memory and deliver either a citation-rich artifact or a proposed change to your organisation's configuration. They are distinct from Workflows, which are deterministic verb graphs, and from Studio, which is ad-hoc chat. Find them at /agents in the app.
- What is the difference between a probe agent and a producer agent?
- Probe agents own an axis of organisation configuration and only propose it - every side effect is a pending approval a human reviews, never a direct write. Producer agents consume approved configuration and write reviewable output, such as a drawing-quantity measurement or a cited tender brief.
- What tier is required for Agents?
- Agents requires Baseline. There is no Agents surface on Free, because agents require organisation configuration - bindings, workspace profile - that only exists once an organisation is connected.
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.