← Back to Token Trust
Working Documentation

Token Trust · Project Detail

The full framework, the market positioning, and the Canadian regulatory blueprint, kept out of the case study so the case study stays readable.

What this is
Every detailed block written for the project, held here in full
Team
Five, across industrial design and graphic design, led by Michael Joongmin Park
Phases
Phase I closed Mar 23, 2026 · Phase II closed Apr 5, 2026
A
Validation
How I tested the idea before committing to it

Six weeks is short enough that a wrong direction in week two is fatal, so I scored the concept before we built anything on top of it.

B
Research
What the team found, and what I did with it

I put the regulatory side with one researcher and market and cost with another. What came back is below, along with what I decided each part meant for the service.

The four numbers I pulled out for the pitch

A synthesis board this dense does not survive a presentation, so I reduced it to four figures a room could hold.

The full audit boundary

Boundary definition turned out to be the core finding of the audit, not a preliminary to it.

Starting from GDPR rather than from scratch

I did not want to invent governance principles. GDPR already defines them and companies already have to follow them, so I used its three pillars as the frame and asked what each would look like if it paid the user back.

Reading them this way changed my mind about the project. Consent and control are already legally guaranteed, but nothing in the law says the value has to come back. That gap is where I decided TokenTrust would sit.

The market numbers that made this a business case

The cost research I assigned is what moved the argument from ethics to economics, and it is the section I leaned on hardest when presenting.

Four signals I used to time the opportunity

I sorted what we found into signals and marked how strong each one was, because a weak signal you can see early is worth more to a service proposal than a strong one everyone is already acting on.

C
Strategy
The framework I built, and why it is shaped this way

The obstacle to paying people for data was never really technical. It was that nobody agreed on how to measure the thing being paid for. Once I saw that, the design problem became a measurement problem, and DQI became the exchange rate the rest of the system runs on.

What changes on each side

I argued the case twice, once for the person handing over data and once for the company collecting it, because a proposal that only helps one side does not get adopted.

This is the slide I used to open every review. When data is given willingly, liability turns into protection and collection grows on trust instead of resistance, and that reframing is what made the enterprise side of the argument work.

Component I: DQI, the Data Quality Index

Four dimensions decide what a contribution is worth, with privacy sitting outside them as a gate rather than a score.

Component II: Reward Token

The part that closes the loop between giving something and getting something back.

Component III: Data Credit

A trust rating for companies. I added this last, after realising the system had no way to hold the enterprise side accountable for keeping its end.

Who sits where

I mapped participants into three rings so the team could argue about influence without arguing about org charts. Governing bodies at the core, regulated companies in the middle, affected parties on the outside.

Partnerships follow the same three layers. Safe Superintelligence Inc. as technical advisor, Okta for identity and access, and GPAI to support entry into other markets. Government bodies stay informed and consulted while keeping regulatory authority. AI companies gain unified token management and access to consent-sourced data.

Four markets where nobody was standing

Competitors run on use then deplete. I positioned TokenTrust on use, refund, recirculate, which is what put us in open space on both value return and portability.

Three horizons to market

I sequenced it so trust gets built before tokens circulate, because launching an open token economy without an audit trail would have been the fastest way to fail.

"Beyond simple redemption or transactional utility, TokenTrust carries an inter-platform character that guarantees user autonomy and expands service accessibility for AI enterprises." This is how I closed Phase I, presented March 23, 2026 as Group 14 of the AI Data Governance Society.

D
Blueprint
Phase II, where I made it operable in one country

Phase I left us with a framework that worked in the abstract. For Phase II I narrowed it to Canada on purpose, because a governance proposal that names no jurisdiction cannot be checked, and I wanted the team's second submission to be checkable.

Services like OpenRouter, Perplexity, Cursor, and Copilot already let you reach several AI providers from one place. What none of them give you is any say over your data once it moves. That distinction, access versus value, is what Phase II is organised around.

What changed between the two phases
Four axes, and the order they switch on

I structured Phase II around four value axes and, more importantly, around their sequence. Getting the order wrong is how projects like this stall.

Traceability comes first because everything else is calculated from it. Regulation runs underneath all of them from day one. Refund starts at pilot. Interplatform only opens once cross-border governance is settled, which is why it is a year three item and not a launch feature.

Axis I, before and after
Axis II, before and after
Axis III, before and after
Axis IV, before and after
What has to be in place before any of it runs

The team pulled the regulatory instruments and I mapped each one to the horizon where it becomes binding. This is the section that took the longest and the one I am most confident in.

Three horizons, one question each

I gave every horizon a single compliance question, because a milestone list nobody can remember is a milestone list nobody follows.

Who is accountable for what

As lead I wanted names against responsibilities, not a diagram of boxes. We used RACI and let the matrix grow with each horizon.

R is responsible and does the work, A is accountable and owns the result, C is consulted for input, and I is kept informed.

Four questions the interface has to answer

I translated the governance model into wayfinding, since none of it matters if a person cannot find their own position in it.

"This positions AI token commerce not merely as an exchange mechanism, but as infrastructure that requires compliance as its base layer before value can flow." Phase II closed on April 5, 2026, with pilot operations and market validation as the next step.

E
Interactive Boards
Standalone artefacts built during the project

These were built as separate pages during the project and are kept here so they stay reachable. Each one opens on its own.