What a row already gives you
Your agent listed five things a token would buy a loyalty program. Four are real. One is something a Postgres row already gives you. Tap it.
Tap the part that will not survive contact with reality — or press 1…5.
Keep the mint authority, or revoke it?
Hadra Records mints a token representing shares of one release’s revenue. Your agent asks: revoke the mint authority at launch, or keep it? Choose.
SPL Token, or Token-2022?
A festival membership that must not be resold. Two ways to build the token. Choose.
VoiceKit credits
VoiceKit will bill ChefCheffe €100 a month plus €0.30 per order handled. Your agent proposes the billing design. Judge it.
A credits token makes billing transparent: ChefCheffe holds credits, each processed order burns one, they can top up from any wallet, and other clients could trade unused credits between themselves.
A token for my-eye
my-eye: voice-first phone control for blind elderly users, grant-eligible, with a real first user. Your agent proposes funding and rewards. Judge it.
A community token could fund development and reward contributors: early users and testers earn it, it trades publicly, and it creates a community around the project before launch.
Two cases where it is defensible
Two of your projects where a token or program passes at least one of the four tests. Neither needs it today. Pick the stronger case and say why.
What survives this level
| Mint authority and freeze authority | Mint authority kept = supply stays programmable; revoked = a promise nobody can undo. Decide which the token is for. |
| SPL Token vs Token-2022 | SPL Token for maximum compatibility; Token-2022 only for a named extension, chosen at mint creation. |
| Decimals and supply as permanent decisions | Decimals are permanent and supply policy is public; both go in the brief as decisions, not defaults. |
| The four things a token buys, each tested against a database row | Name the party who must transfer or compose without asking you; if there is none, it is a Postgres table. |