Nine apps, one record substrate

Village Gateway is built and deployed on both production hosts 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.

MDSL intends to release Village Gateway as open source. This is an intention only: nothing has been released, no licence has been fixed, no date is set and no stage has been named.

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

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.

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.

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 paying customer's run has been sealed.

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

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.

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.

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.

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.

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 (Catalyst, Wellington) or the EU (OVH, Strasbourg), and each Village is separate from every other.

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