Journey 2: publishing a cycle (UC-11)

1. The team creates the cycle in the back-office and sets its schedule.
2. It opens the list of submitted, approved projects and selects 5.
3. Scanner produces a pre-report per candidate; the team reviews it.
4. The team writes each dossier's thesis, 3 reasons, plan, and risks.
5. It publishes all 5 dossiers together; the X bot posts a dossier drop for each candidate.
6. Voting opens automatically at the scheduled time.

Edge cases:

• A candidate becomes ineligible before voting (the developer returns and sells): the back-office flags it; the team removes or replaces it before opening.
• Fewer than 5 eligible tokens: this source journey allows a cycle with 3–5 candidates.
• A candidate not elected in the previous cycle can be reused with one click and an updated dossier.