MIO° Conduct Record™
A sealed record of what your AI agents are allowed to do.
MIO° Conduct Record is a sealed register of what an organisation's AI agents are authorised to do, and which agents exist. When something goes wrong, or an auditor asks, you can show what each agent was authorised to do at the time. It records authority. It does not block, enforce or prevent anything.
What it does
- A change to a mandate is a new dated record that supersedes the old one, and the old record is kept.
- A lookup of the mandate in force at any given time is available through the API on both production servers, in New Zealand and Europe.
- An auditor can check a Conduct Record offline, without an MDSL account.
- In our own testing, out-of-mandate acts were recognised at a rate of 100% for blatant acts, 92% for moderate acts and 58% for subtle acts, with no false positives across 36 clean cases. The 58% means occasional sampling would miss most isolated subtle acts, so it limits what can be promised.
What it is, and what it is not
The lookup shows what was recorded, as recorded. The key that signs a record is held on a separate signing host, outside the process that writes records, and MDSL operates that host. Checking an agent's action against its mandate before it runs is not built, and continuous monitoring of agents is not offered.
Daily anchoring on the Midnight ledger
Status: Built. The Conduct Record records we have sealed can be gathered into a daily value, and the hash of our signed daily root, which covers that value, can be recorded on Midnight's Preview test network, a shared ledger. Only hashes go on the ledger. No record, name or agent detail does.
An anchor shows that a value was recorded under a date key. It does not answer whether the records are true or complete. It is an attestation by our service key. Midnight is a federated network, not a decentralised one.
How a record reads never depends on Midnight. The signature and the outside time-stamp token decide that, and the offline checker, governance-receipt-verifier.js, gives the same result with or without an anchor. When an anchor proof and the ledger reading are supplied through the options --anchor-proof and --anchor-check, the checker reports anchored or anchor_not_checked on a separate line.
Coverage: records held on our OVH servers only. A record that is signed and sealed after a day's range has closed joins the next day's range. The date an anchor carries is therefore the date of the daily root that first took the record in. It can differ from the day the record was created.
Price
| Sealed Statement | — per statement |
|---|---|
| Standing Record pilot, per agent | — /month per agent |
A Standing Record pilot covers up to five agents with a 90-day term. Prices exclude tax.
How to get it
Conduct Record is available on request. There is no self-service signup, no trial and no free tier. Tell us a little about your agents and what you need to be able to show; this creates no account, and every request is reviewed before anything is issued.
Related
- Governance API: the interface your software calls before an AI agent acts (sandbox by invitation).
- AI Visibility Auditor: measure what AI assistants say about you, and keep the measurement as a sealed record.
- Attested Accounts: finance records that show whether they were changed.
- The Village catalogue and price list · Pricing
Status as at 27 October 2026.