MIO° Conduct Record™
24 September 2026 · John Stroh, Director, My Digital Sovereignty Ltd
What it is
MIO° Conduct Record is available on request at conduct.amiomega.digital: a sealed register of what an organisation's AI agents are authorised to do, and which agents exist. A customer seals a mandate (the actions an agent is permitted), seals an inventory entry binding each agent to an identity reference, and can ask which mandate was on record at any past moment.
It is built on SSST, the same sealed, signed and time-stamped design AVA™ applies, implemented per product. A change is a new record that explicitly supersedes the old one, and the old one is kept. A third party verifies a record offline against published keys.
Published pricing: a Sealed Statement at NZ$526, and a Standing Record pilot at NZ$263 per agent per month (up to 5 agents, 90-day term). Available on request.
The buyer is any organisation that must later show a board, auditor or regulator what its agents were permitted to do.
Built vs roadmap
The product is available on request and sellable. Status as of 24 September 2026, established by AI agents from the code and plans; no person has checked every line (see the status page):
| Capability | Status | What it means for a customer |
|---|---|---|
| Sealing substrate (SSST: hash, signature, an RFC 3161 timestamp from an outside authority) | Available on request for Conduct Record (AVA uses the same design) | Each record is submitted for a time-stamp from an outside authority; if the authority does not answer, the record says so and the request is retried. A third party can check a record offline |
| Mandate and agent-inventory records, with supersession | Available on request; deployed on both production servers (NZ and OVH) | Sealed history of what each agent was authorised to do. Hash-linking is live for records written from 24 September 2026; removal of the newest entries is not yet detectable |
| API: seal mandates and inventory entries; "mandate in force at time T" lookup | Available on request; deployed on both production servers | Programmatic use from the customer's own systems |
| Offline verification by a third party | Available on request | A third party checks a record on their own machine, with no account and no call to MDSL. Until the signing key is separated, the check still relies on MDSL not having rewritten and re-signed the record. |
| Guard against personal names or emails in agent records | Available on request | The guard rejects personal names and email addresses in agent records |
| Site, pricing, how it works, FAQ | Available on request at conduct.amiomega.digital | Buyers can read the offer and ask for access |
| 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) | Built and tested in development; not in production | Not available to customers |
| Enforcement: agent action checked against its mandate before it runs | Not part of Conduct Record; a pre-action verdict is what the Governance API returns (sandbox today) | Conduct Record evidences authority; acting on a verdict is the caller's system |
The full participant one-pager, with the competitive landscape and the risks and open decisions, is shared in the private room, to named people, with a record of who opened it. Write to john.stroh@mysovereignty.digital to be invited.