Who this is for
For implementation and pilot partners
Organisations that actually run pilots and implementations in a region.
What we actually do
We prepare the Pilot Proposal and the Implementation & Pilot Pack with evidence, constraints and stop conditions. Responsibilities and data boundaries are explicit in the document; a plan never implies an agreement exists.
- Proposals state their evidence and stop conditions
- A plan's existence never implies an agreement exists
What that rests on
Public-source evidence bound to the region's Case; partner-specific information only as you provide it.
What we do not claim
We claim no partner network, no running pilot and no closed engagement. None of those exist today.
What you actually receive
Implementation & Pilot Pack — the relevant Case, the local role that may exist, the responsibilities required, the operating constraints, the validation protocol needed, and the dependencies and risks
The decision it serves: in what scope and under what conditions a pilot can start
- Read online — read the current version in the Workspace and drill into the evidence
- Download the official report — the released version itself as one self-contained file with its identity block; print to PDF from your browser
- Structured data (JSON) — machine-readable data that keeps every statement's truth class, evidence and incompleteness
- Comment, revision, acceptance, outcome — respond to the deliverable in your own words and ask for the next decision
Beta: the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet · not yet delivered to any real organization.
What you can do next
Tell us the role you can take and the region. Synthetic samples are inspectable right now.
Tell us the role you can take
Send only what is needed. A personal name, telephone number and postal address are not required.
A person reads what you send. There is no automated reply and no automated sales follow-up. Sometimes there will be no reply at all.