Journey 3: the 72-hour CTO (UC-15, UC-16, UC-12)

1. On Day 0, voting closes; the orchestrator creates the operation and opens the token dossier.
2. T+0: Scanner reruns checks; if the contract is no longer safe, the CTO is canceled.
3. T+2 h: Designer proposes 3 identities; a Telegram or X poll chooses before T+6 h.
4. T+6 h to T+9 h: Webdev publishes the website.
5. T+12 h: CM publishes the comeback thread on the new X account in this source journey.
6. T+24 h: TG Bot opens Telegram; the team submits the Pons CTO application.
7. T+48 h: Builder publishes the utility.
8. T+72 h: takeover ends; status becomes Sending or stays CTO live until the verdict.

Edge cases:

• A step fails 3 times: the orchestrator pauses it and alerts the team; independent steps continue.
• An agent reaches its budget: it stops; the team decides whether to increase the budget or skip the step.
• Nobody votes in the identity poll: this original journey proposes the Designer's top-ranked direction. The implemented orchestrator's calendar and approval rules should be checked before treating this as automatic behavior.
• An output waits for approval too long (over 2 h): send the team a Telegram reminder.
• Two CTOs overlap: each operation has its own schedule and budget.

See The takeover cycle for the schedule read from the current code, including the T+14 h comeback thread.