MIO° Conduct Record™
20 October 2026 · John Stroh, Director, My Digital Sovereignty Ltd
What it is
MIO° Conduct Record is a sealed register of what an organisation's AI agents are allowed to do, and which agents exist. ("Sealed" means locked with a digital signature and a time-stamp from an outside authority, so a later change shows up.) The organisation records each agent's permitted actions. A change is a new dated record and the earlier one is kept. Someone can ask "what was this agent permitted to do on that date?" and check the answer independently.
Who it is for
- Organisations that use AI agents and must later answer to a board, auditor or regulator: finance, health, public sector, and community data holders.
- Their leaders say things like: "Who authorised that agent?" and "Can we show what it was allowed to do at the time?"
- It does not stop an agent doing something. It is the evidence of what was authorised.
- Iwi, hapū, marae, rūnanga and other Māori organisations are approached by MDSL directly, not through distributors.
What a customer gets today
| Item | Status | In plain words |
|---|---|---|
| Recording an agent's permitted actions; each change is a new dated record and the old one is kept | Available on request | Available now |
| Register of which agents exist, by a reference code instead of a name | Available on request | No names or email addresses are recorded, only roles and references |
| "What was in force at this time" lookup, from the customer's own systems | Available on request | Available through the API |
| Time-stamp from an outside authority, and offline check by an outsider | Available on request | An auditor can check a record without an account |
| Signing key held on a separate host, outside the process that writes records | Built; not yet in use for Conduct Record | A separate signing host is in use for every active Village™. It is not yet in use for Conduct Record; until it is, MDSL holds the key and a verified run shows what was recorded. The host is operated by MDSL: the key is in a different place, but still in MDSL's hands. Split-key signing is built and not yet in use |
| Spot-checks seeded from public randomness (drand) | Prototype; built and tested in development; not in production | Not audited. Not available to customers |
| Checking an agent's action against its permissions before it runs | Not built | Conduct Record evidences authority; a pre-action verdict is what the Governance API returns (sandbox today) |
Published pricing
From the Conduct Record pricing page:
- Sealed Statement: NZ$526, one point-in-time evidence bundle
- Standing Record pilot: NZ$263 per agent per month, up to five agents, 90-day term
- Continuous monitoring is not built and has no published price
Available on request, and MDSL quotes no price beyond these figures.
How to introduce it
Risk, audit or compliance lead
- "If an auditor asked what your AI agents were permitted to do last March, what would you show them?"
- "Who signs off an agent's permissions, and how is that recorded?"
- "Could you show what each agent was permitted to do at the time of an incident?"
Technology or operations lead
- "How many AI agents are running in your organisation, and is there one list of them?"
- "When an agent's permissions change, is the old version kept and dated?"
- "Would a record that an outside party can verify save you an argument later?"
What to say and what never to say
A distributor works to the same wording. MDSL describes Conduct Record as evidence: it records authority, it does not enforce it, and it does not prevent anything. Status is described from the table: available on request, built, planned or not built; "live" is used only for what a customer uses in production.
MDSL does not use these words about any product: tamper-proof, court-defensible, legally admissible, compliant, certified, immutable, safe. MDSL does not say Conduct Record stops an agent acting, and does not promise that audits will catch everything. A price other than those above is not quoted, available on request only, and any absolute term needs approved wording from MDSL first.
What we provide you
- The published pricing and how-it-works pages to hand to a customer
- Direct contact with John Stroh for any question you cannot answer
- Customer access, when we agree it, arranged directly by John Stroh
Next step
The next step is for the distributor to name the customers they have in mind and which of the two customer types they are; John Stroh then confirms what can be shown to them and arranges any access himself. The subscription itself is between the customer and MDSL.
Nothing in this note is an offer, and no exclusivity, territory or margin is agreed or implied by it. Any arrangement today is with MDSL. If MIO is formed, it may later be assigned to MIO, and the terms would say so. Prices are those on the published pricing page; quote no other.