Assignment
A7 — Design memo (due at the start of demo day)
In one sentence. Tell a Head of Product what you built, what the market showed, which pieces you actually needed, and whether a licensed firm should go / partner / pass.
Stuck? Handbook → Session 13 unbundle table + Sources at the end of the handbook. Reuse A1–A6 facts; write the unbundle and the recommendation new. For the shape of heading 5 only, see the SAMPLE unbundle paragraph (laundry, not EAGE).
Use these eight headings
- The problem and the community
- The mechanism — who mints, the cap, what the claim/redemption is
- Circulation evidence — tx hashes and the pool
- What the market revealed — price, depth, who traded, thin book or IL
- Unbundle the stack — Did you need a chain, or a shared list? Consensus, or a registrar? A token, or an escrow tab? Which pieces did the financial work?
- What broke — one true operations story
- Go / partner / pass — one verb, then why a licensed fintech should copy, rent, or ignore this rail
- Sources — at least three: (i) babysitting co-op or Sarafu, (ii) one Naranjo result (PoW / AMM / peg), (iii) one MIT or BIS idea. Use the handbook Sources list. A blog recap is not enough.
Rules
- No hype paragraph. No price prediction.
- Numbers beat adjectives.
- If the memo is individual: teammates may share logs; the unbundle and recommendation must be your own words.
This is not a whitepaper and not a pitch deck.