MPC dApp Guide (D9): Registry Interface Walkthrough (Synthetic Demonstration Data)
Is the MPC dApp walkthrough real project data? No. The Walk the Mockup chapter of the Mineral Project Coin (MPC) dApp Guide steps through one synthetic project, SYNTH-PROJECT-001, in eight steps, from Project Registry to publication, change impact and the Conditional Asset gate. Nothing is connected.
- Status
- Mockup · synthetic data
- Whitepaper basis
- §5.4.2 Application Layer · §13.4 Mining RWA and Verification Risk; status wording is inherited from here
- Verified on-chain today
- None. Nothing here is deployed yet
- Still at design stage
- Every screen shown below · All source connections · The chain anchor and its proof
The fixture project is SYNTH-PROJECT-001, labelled synthetic_test_project inside the product itself. It was built to demonstrate one thing: that the workflow holds together when the evidence is imperfect, which is the only condition it will ever run in.
What happens across the eight steps of the synthetic walkthrough?
- 01Project Registryregister
- 02Sources & receiptsconnect
- 03Professional verificationreview
- 04Readinessassess
- 05Human decisiondecide
- 06Publication & proofpublish
- 07Change impactmonitor
- 08Conditional Asset gatelocked
Steps 06 to 08 are locked until the authorised decision at step 05 is recorded. The lock is the point of the demo, not a loading state.
How does evidence come in with its limits attached?
How is readiness kept separate from the human decision?
go is not an available action; the only route forward is better evidence.Full size ↗Pressing Simulate replacement evidence resolves the blockers to watch. The go button still does not appear on its own; a demo approver has to record the decision, with a monitoring condition and the input snapshot reference. Only then do publication and proof unlock.
Why is stopping before Asset integration not a failure?
How does the mockup read on a phone?
The same screens at 390px: the step rail becomes a horizontal scroller, and every table row restacks into labelled fields rather than scrolling sideways. No value is dropped between breakpoints: a status that is visible on a desktop is visible on a phone.
What this does not do
- The mockup connects to nothing and broadcasts nothing.
- Its numbers, entity names and hashes are fixtures and must never be quoted as project facts.
- It does not demonstrate a purchase, subscription, transfer, custody or offering control, because none exists.
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







