Journey 5: Pons CTO and fees (UC-14, UC-19)

1. At T+24 h, Scanner and CM prepare the CTO application; the team reviews and submits it through the Pons form.
2. CM publishes the verification tweet tagging @ponsdotfamily.
3. Pons accepts: tracking detects the new recipient (CTO Fees wallet) after the 3-day wait.
4. Daily, the treasury job claims fees; the Buyback Bot uses 100% to buy back and burn $VIVRA.

Edge cases:

• Pons rejects: the dossier shows rejected; CTO and buyback continue without the flywheel.
• No Pons response after 7 days: the team follows up manually.
• Original developer returns during the 3-day wait: Pons can cancel; the team is alerted.