Skip to content
Panasia plate: nested orbits at differing inclinations
01 / 09

INSTITUTIONAL ADOPTION / ADOPTION GUIDE

A practical path to institutional blockchain adoption.

Who has to sign, what evidence each signature needs, and which unresolved question should stop a program before it reaches production.

Part of Institutional Adoption.

Reviewers a program has to clear

02 / 09
  • Accountable business owner
  • Risk & compliance
  • Information security
  • Legal & regulatory
  • Procurement
  • Operations & production support

WHERE ADOPTION IS DECIDED

03 / 09

The review is the decision.

The program page describes what Panasia produces. This piece describes what the institution has to be able to answer in its own review, after the vendor has left the room — because that review, not the pilot, is where adoption is decided.

FOUR THINGS THE INSTITUTION OWNS

04 / 09

Four things you own.

A blockchain program is easier to evaluate when it is framed as an operating decision with an accountable owner rather than a technology announcement.

A delegation meeting across the table
Cabinet Secretariat · CC BY 4.0
Panasia plate: market conditions read as concentric bands
01 / 04

Name the accountable owner first

A program without a single accountable business owner produces a demo. The owner is the person who can stop it, not the person who sponsored it.

Panasia plate: a dense integration lattice seen head on
02 / 04

Evidence per reviewer, not per phase

Risk, security, legal, procurement, and operations each need a different artefact. Producing one deck for five reviewers is the most common reason a pilot stalls at month five.

Panasia plate: layered planes dispersing at the edge
03 / 04

Controls are the deliverable

MAS Notice PSN05 is the kind of standard a reviewer actually applies. Designing to a published control standard from the start is cheaper than retrofitting one after the pilot.

Panasia plate: separate approaches converging into one route
04 / 04

Production means recoverable

Adoption is provable when someone can operate, approve, stop, and recover the system — and has already done so in a test.

FOUR STEPS TO PRODUCTION

05 / 09

Owner, reviewers, recovery, transfer.

Each step produces an artefact a reviewer signs, which is what turns a pilot into an adoption record.

Panasia plate: layered institutional planes dispersing at the edge
  1. 01

    Owner

    Name the accountable business owner and the stop authority in writing.

  2. 02

    Reviewer map

    List every internal reviewer, the artefact each requires, and the date each is engaged.

  3. 03

    Recoverability test

    Demonstrate operate, approve, stop, and recover before the pilot is called a success.

  4. 04

    Obligation transfer

    Move monitoring, reporting, and incident duties to a named operating team with a scheduled review.

The standards these reviewers reach for.

06 / 09

CITED PUBLIC SOURCE

07 / 09

MAS — participants in the Project Guardian industry group

MAS publishes the institutions in the Project Guardian industry group, which is what a verifiable adoption claim looks like: a named institution and a named use case, not a named technology.

Evidence as of

Hong Kong — a member addresses the Legislative Council
inmediahk · CC BY-SA 2.0

RESOURCES

08 / 09

Continue into the program, or the markets where the controls are already published.

SCOPE THE ADOPTION CASE

09 / 09

Which reviewer is unsatisfied?