Tsagaan Tolgoi and the Mongolia profile
The official reference project, and the first jurisdiction profile — used to prove the workflow against real conditions, not to imply that the project is ready to issue.
- Status
- Reference workflow
- Whitepaper basis
- §14.1.3 Deploy — Reference Deployment · §15.6 Forward-Looking Statements
- Verified on-chain today
- None — nothing here is deployed yet
- Still at design stage
- Source inventory · Adapter states · Manual fallback procedure
Tsagaan Tolgoi is the official reference project. That fact alone presumes nothing about project rights, government consent, an issuer, an SPV, the legal structure or issuance readiness — and the product is built so that it cannot quietly imply otherwise.
Mongolia is the first jurisdiction profile to be supported in depth. This does not make the system Mongolia-only: the core Registry, adapter interface and policy engine stay country-neutral, and only Mongolia's institutions, legal meanings, source access, freshness, disclosure, language and unit rules live in the profile.
Every source carries its own state
| Source state | What it means |
|---|---|
planned | Identified, not yet assessed |
feasibility confirmed | The route exists; access is not yet established |
access confirmed | Access rights and licence terms are confirmed |
in test | Connected, under verification |
in use | Producing receipts in the live workflow |
unavailable | Currently failing — recorded as a failure, never as an empty result |
manual | Confirmed by official extract or registry check instead of an interface |
- Source state
planned- What it means
- Identified, not yet assessed
- Source state
feasibility confirmed- What it means
- The route exists; access is not yet established
- Source state
access confirmed- What it means
- Access rights and licence terms are confirmed
- Source state
in test- What it means
- Connected, under verification
- Source state
in use- What it means
- Producing receipts in the live workflow
- Source state
unavailable- What it means
- Currently failing — recorded as a failure, never as an empty result
- Source state
manual- What it means
- Confirmed by official extract or registry check instead of an interface
An API, an institutional agreement or a republication right that has not been confirmed is never described as implemented.
Every item carries its own state too
| Item state | What it means |
|---|---|
confirmed | Evidence and rights are confirmed |
pending | Evidence or confirmation is still missing |
rejected | The submitted basis cannot be used |
not_applicable | Does not apply to this project |
- Item state
confirmed- What it means
- Evidence and rights are confirmed
- Item state
pending- What it means
- Evidence or confirmation is still missing
- Item state
rejected- What it means
- The submitted basis cannot be used
- Item state
not_applicable- What it means
- Does not apply to this project
If material turns out to be insufficient, the project runs the Project and Verification Registry workflow and finishes there without an offering. If the real disclosure scope cannot be confirmed, the functionality is exercised on synthetic data only and the reference publication stops.
What this does not do
- Reference status is not a claim about project rights or government consent.
- No resource or grade number is published ahead of a competent-person report.
- A single confirmed source is not generalised into confirmation of the project.
This chapter is a public adaptation of the internal product specification. Where the two differ, the specification and the whitepaper govern.
MPC dApp Guide · design & build stage · synthetic demo data