dApp GuideThree Judgments
How It WorksD4

MPC dApp Guide (D4): Three Judgments Kept Apart | Data Readiness, Onboarding and Issuance

Does ready data approve an issuance? No. The Three Judgments chapter of the Mineral Project Coin (MPC) dApp Guide keeps three owners apart: data readiness (a versioned rule set), protocol onboarding (MPC Protocol Governance) and legal issuance (the issuer and its counsel). A recorded go creates no transferable right.

Status
Design & build stage
Whitepaper basis
§6.2 From Onboarding to Issuance · §5.5 Asset Issuance Structure · §9.3 Platform vs. Asset-Level Compliance
Verified on-chain today
None. Nothing here is deployed yet
Still at design stage
Gate decision records · Protocol onboarding vote
  • Judgment
    Data readiness
    The question it answers
    Is the required material and review in place?
    Who is accountable
    A rule-based system, on a versioned rule set
  • Judgment
    Protocol onboarding
    The question it answers
    Will MPC support this project technically?
    Who is accountable
    MPC Protocol Governance
  • Judgment
    Legal issuance
    The question it answers
    Can issuance or an offering actually happen in this structure and jurisdiction?
    Who is accountable
    The project-specific issuer, its legal counsel and the required external bodies

Ready data does not approve an issuance. A decision by MPC to support a project is not an investment recommendation and is not a legal issuance approval.

Mockup · 1440px capture
Mockup decision step showing a HOLD notice and a disabled 'Go is blocked' button next to an enabled 'Simulate replacement evidence' button.
The decision. While a blocking readiness result stands, go is not an available action; the only route forward is better evidence.Full size ↗

The decision record keeps the decision authority, the input snapshot hash, the rationale, and any monitoring condition attached to a watch result. That is what makes the decision auditable later, including by the person who made it.

What this does not do

  • Readiness does not auto-promote a project to the next registry.
  • Protocol governance cannot override a readiness result or approve a legal issuance.
  • A recorded `go` does not create any transferable right.

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