Rule agents check one thing each. The service agents do the jobs that span a source or a domain: profiling what the data looks like, finding duplicates, verifying values against the world, proposing and applying corrections, watching the sources for anomalies, and explaining a finding to whoever asks.
The level shown is the usual starting point; every level is per action type and is earned upward.
| Service | What it does | What it produces | Usual level |
|---|---|---|---|
| Profiler | Reads a source and learns its shape: fill rates, formats, distributions, value lists, key candidates, drift over time | Column scores per dimension, cross-source comparison, suggested rules for the weakest fields | L1: proposes rules; writes nothing |
| Duplicate finder | Runs the domain's match rules on new and changed records, and periodically over the whole domain | Pairs and clusters with a confidence band and the evidence that joined them, queued for the steward | L1 to L3: merges alone only above a band the owner sets |
| Verifier | Checks tax ids, registrations, addresses, bank details and sanctions lists against outside services | A verification result with its reference, date and evidence, and a correction proposal where the service returns a better value | L2: applies confirmed corrections after approval; two-person rule on bank details |
| Corrector | Turns findings into proposals: standardisations, list mappings, derived values, values taken from the winning source | Tickets with the before, the after, the basis and a confidence; bulk proposals for identical fixes | L1 to L3 per action type: standardisations climb fastest |
| Monitor | Watches volume, freshness, structure and value distributions on every source, with learned patterns | Anomaly tickets with the root cause traced through lineage; pauses on a feed; notices to consumers | L3 for pausing a feed; L1 for everything that changes data |
| Explainer | Answers 'why is this record quarantined' and 'what changed here' in plain words for the grid, the API and the assistant | An explanation with the rule, the evidence and the ledger entries behind it | L0: reads and reports |
A rule agent has one directive and a narrow scope. A service agent has several directives, a scope that may span a source, and tool grants that let it call the match engine, a verification service or a write interface. Both are described by the same eight blocks, live in the same register and climb the same ladder, which is why a steward who has managed rules can manage services.
Services are also where the models live. The corrector's confidence comes from a model trained on the estate's own accepted and rejected fixes; the monitor's expected ranges come from a model of the source's own rhythm; the duplicate finder's bands come from the match engine's scoring. Each model is an implementation detail behind a directive, and each is evaluated on golden cases like any rule.
Services are shipped with the platform and configured per domain; they are the reason a first week on a new domain is a week. The profiler runs on Monday with no rules written, and by Monday evening the owner can see which fields cost the most.
Where a programme needs an agent beyond the shipped six, the same eight blocks describe it: a mission, a scope, directives in sentences, tool grants, a trigger, guards, an escalation route and an eval. Definitions can be co-drafted with an outside model, with metadata crossing the boundary and row data staying inside.
Illustrative, from the showcase supplier and material domains; figures labelled showcase.
Yes, through the same read-in-place connectors the rest of the platform uses, with each source's own permissions applied. Writes go through the released interfaces and are acknowledged.
The profiler, the monitor's observation and the explainer run from the first day at L0 or L1. Anything that changes data starts at L1 and climbs through the gate described on the autonomy page.
Configured as tools with a mode, per agent: tax authorities, company registries, postal services, bank verification and sanctions lists. The verification page lists them.
Bring one domain and two systems. In a week the sources are profiled, the ten costliest fields are under rules, the first corrections are written back with their acknowledgements and the publish gate is on.
