Village Gateway
An AI agent asks, your policy decides, and a one-use permit carries the action.
Village Gateway puts an AI agent’s actions under your policy. Its functions share one record substrate, built to be checked offline. Village™ is part of it.
Receipts are signed under keys MDSL holds, and Village Gateway is switched on separately for each organisation.
An AI agent asks, your policy decides, and a one-use permit carries the action.
Your software sends a proposed action; a verdict and a signed receipt come back.
A dated, signed register of what each AI agent may do, and which agents exist.
Puts your buyers’ questions to AI assistants and records each answer word for word.
Each proposed email meets your policy first; a person releases or refuses a held one.
Every change to an invoice, quote or expense is signed as it happens.
Send sealed records a reader checks in their own browser, offline, with no account.
One file holding a lot’s signed records and the decision to send them.
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.
Records are hash-linked, so a removed or reordered entry shows.
Sealed records written from 24 September 2026, 11:30 NZST are hash-linked, so a deleted or reordered entry in the middle of a history can be detected.
Limits and dates for each: EST-12.
Time stamps come from European authorities; the daily estate root carries two.
Time stamps from outside time-stamping authorities under RFC 3161 are in use: Certum (Poland) stamps records, and the Portuguese state's Cartão de Cidadão authority stamps the estate root. The published estate-root index shows both stamps on every root from 4 October to 8 November 2026 (36 of 36).
Per-record time stamps come from Certum (Poland), a non-qualified service; the daily estate root also carries a stamp from the Portuguese state's Cartão de Cidadão authority (EST-10).
The Gateway checker holds five authorities’ keys, Portugal’s and the qualified ArubaPEC’s among them.
The offline checking program verifies a stamp from any of five European time-stamping authorities: Certum (Poland), BOSA (Belgium), CESNET (Czechia), the Portuguese state's Cartão de Cidadão authority and the qualified ArubaPEC (Italy). It needs no account and no network.
Limits and dates for each: GTW-08.
Each checking program is published with its SHA-256.
Each offline checking program is published at mysovereignty.digital/downloads/ with its SHA-256, so a reader can confirm that the file they run is the file MDSL published.
A decision record can be exported with its approvals, receipt and events, and an offline checker (Node 20, no network, no product installed) verifies the export against a bundle of public keys.
A second signature, ML-DSA-65, on four kinds of record, switched on per account.
A second signature using ML-DSA-65 (NIST FIPS 204) is added to Provenance seals, Governance API receipts, Email Decision Record receipts and proof-chain compaction summaries after the classical signature, so a record carries both; the downloadable verifier checks it.
Limits and dates for each: EST-37.
Signing keys sit on a separate host; a 2-of-3 split-key scheme is built and available on request.
A separate signing host, operated by MDSL, holds the signing key for each Village moved onto it. A 2-of-3 split-key scheme (FROST: the key is generated in shares and no whole key ever exists) is built, tested, deployed to both servers and available on request: a Village is moved onto it by a key ceremony among its three key holders.
Limits and dates for each: EST-16.
One hash a day, the hash of the estate root, is anchored on Midnight mainnet.
One value a day, the hash of the signed daily estate root, is anchored to an insert-once contract on Midnight mainnet (contract 517a75cf…5de7, deployed 12 Nov 2026); the ledger holds a date key and a hash, and no personal or tenant data.
A daily hash of the estate root is anchored on the Midnight main network (EST-29); business records stay on MDSL infrastructure in New Zealand and the EU. Village Gateway is built so that, where Gateway anchoring is switched on for a Village, each of its Gateway receipts is a leaf in that Village's sealed day root, and a proof file links each receipt to the anchored hash; that path is built and tested and has not yet been run on the main network (GW-57).
Records stay in New Zealand and France; no US-owned provider holds them.
Where Villages run and members sign in, and where Village Gateway is priced, set up and supported.
mysovereignty.digital →The Tractatus framework, the papers, and MIO-STD-01, MDSL’s draft standard for sealed records.
agenticgovernance.digital →MIO is a proposed service company for this product. Read about it for participants or for distributors.