MIO°Village Gateway
The functions

Village Gateway and its functions, one record substrate

Each function in one line. Open one to read the register statements behind it, word for word.

Available on request

Village Gateway

An AI agent asks, your policy decides, and a one-use permit carries the action.

What the register says

Village Gateway is built and deployed on our EU production host as an access and approval layer: an agent or person's request to act is checked against the Village™'s policy, a decision is recorded with a signed receipt, an approval-gated request waits for a different approver, and an allowed request gets a one-use permit that a resource redeems exactly once.

Village Gateway is available on request. MDSL arranges it for one Village at a time.

Limits and dates for each: GTW-01, GTW-14.

Village Gateway on mysovereignty.digital →

Available on request

Let other software ask before an agent acts

Part of Village Gateway. Also known as Governance API. Village Gateway does not use Governance API verdicts today.

Your software sends a proposed action; a verdict and a signed receipt come back.

What the register says

The Governance API is an interface other software calls before an AI agent acts: a proposed action goes in and a verdict of allow, gate (a human decides) or deny comes back with coarse reason codes and an Ed25519-signed receipt.

Sandbox access is by invitation from John Stroh, issued as a one-time token tied to a single address.

Limits and dates for each: API-01, API-02.

Read the announcement →

Available on request

Record what an agent may do

Part of Village Gateway. Also known as MIO° Conduct Record™. Village Gateway decisions are not checked against Conduct Record mandates today.

A dated, signed register of what each AI agent may do, and which agents exist.

What the register says

MIO° Conduct Record is a sealed register of what an organisation's AI agents are authorised to do, and which agents exist.

A change to a mandate is a new dated record that supersedes the old one, and the old record is kept.

Limits and dates for each: CON-01, CON-02.

conduct.amiomega.digital →

Available on request

See what AI assistants say about you

Part of Village Gateway. Also known as AVA™, the AI Visibility Auditor. AVA has its own accounts and needs no Village.

Puts your buyers’ questions to AI assistants and records each answer word for word.

What the register says

AVA (AI Visibility Auditor) puts the questions an organisation's buyers ask to AI assistants, records each answer verbatim with the model and time, and compares it with what the organisation's own site publishes.

Sealing an AVA run (hash, signature, time-stamp from an outside authority) is built and has run once end to end in testing on a real site; no customer's run has been sealed.

Limits and dates for each: AVA-01, AVA-06.

ava.amiomega.digital →

Built, available on request

Keep a sealed record of email decisions

Part of Village Gateway. Also known as Email Decision Record™.

Each proposed email meets your policy first; a person releases or refuses a held one.

What the register says

Each proposed email is checked against the owner's policy before it can be sent.

A held email is released or refused by an approver, through a route that records who decided.

Limits and dates for each: EDR-03, EDR-02.

Email Decision Record on mysovereignty.digital →

Available on request

Keep accounts with a signed history

Part of Village Gateway. Also known as Attested Accounts™.

Every change to an invoice, quote or expense is signed as it happens.

What the register says

Attested Accounts is an evidence layer over the Business Village's invoicing, quoting, recurring invoicing, expense and time tracking.

Every write to an invoice, quote, recurring invoice, expense or time entry appends a proof-chain entry signed under the tenant's key when it happens; this is part of the Village's sovereign-record layer and has no switch.

An invoice has an action-history view and a downloadable verification bundle that a third party can check offline.

Limits and dates for each: ACC-01, ACC-02, ACC-04.

accounts.amiomega.digital →

Available on request

Provenance™

Part of Village Gateway.

Send sealed records a reader checks in their own browser, offline, with no account.

What the register says

Checking a Provenance dossier needs no account and is free of charge: the check runs in the reader's own browser, offline.

Provenance is available on request; evaluation access is a one-time link issued at MDSL's discretion; there is no self-service signup, trial or free tier.

Limits and dates for each: PRV-03, PRV-02.

Provenance on mysovereignty.digital →

Available on request

One file of the signed records for a lot

Part of Village Gateway. Also known as the consignment file.

One file holding a lot’s signed records and the decision to send them.

What the register says

The platform can assemble a consignment file: a Provenance dossier and an Email Decision Record dossier in one file that can be checked offline, with a signed email record linked to the lot by its lot reference; with an optional invoice_id the same routes produce a three-member version 2 file that includes the invoice.

An owner can propose sending a consignment file to one outside recipient through the Email Decision Record; the proposal is always held for a second approver, never the sender, and is released through the existing release machinery.

Limits and dates for each: CSN-01, CSN-03.

The consignment file on mysovereignty.digital →

Live

Village, the members-only platform

Part of Village Gateway.

The members-only platform that is part of Village Gateway. A Village starts by invitation or, where MDSL has opened self-service, with a verified payment card.

What the register says

Village is a members-only community and organisation platform built and operated by MDSL in New Zealand, for families, clubs, small businesses and governance bodies.

Each Village's data is held in New Zealand (Wellington) or the EU (Strasbourg), and each Village is separate from every other.

Limits and dates for each: VIL-01, VIL-02.

mysovereignty.digital →

A Village starts by invitation or, where MDSL has opened self-service, with a verified payment card; Village Gateway and its other functions are available on request from MDSL.

Planned, with no dates

Sovereign Database: a Village’s data in its own database on New Zealand infrastructure (VIL-06).

Federation hardening: ways to strengthen federation between Villages, which is built and off by default (VIL-21).