# The takeover cycle

A new cycle is planned every week. Cycles overlap: a new selection can begin while the previous project is still being followed.

**Day 0 is the close of voting.** T+ means hours after Day 0; Day + means days after Day 0. All times are UTC. The French source uses J0 and J+ for the same day markers.

## Before Day 0 · the community chooses

The team submits addresses for analysis, checks eligibility, and publishes five dossiers. Voting stays open for 48 hours. The score is frozen at publication; market data is tracked separately.

## The first 72 hours

| Time | Action | Responsible |
| --- | --- | --- |
| T+0 | Full report and team-approved go / no-go decision | Scanner |
| T+2 h | Three brand directions | Designer |
| T+2 h 30 | Community poll on the identity | Designer |
| T+5 h | Brand kit based on the selected direction | Designer |
| T+6 h | Website and mini-dapp built from templates | Webdev |
| T+12 h | X account setup and CTO verification tweet | CM |
| T+14 h | Project comeback thread | CM |
| T+24 h | Telegram, manual CTO application, and planned buyback start | TG Bot, team, Buyback Bot |
| T+48 h | Utility and website integration | Builder, Webdev |

These are orchestrator deadlines. A step also waits for its dependencies and, where required, human approval. The advertised timeframe does not bypass these checks.

## Day 3 · buyback review

The default configuration calls for an early stop if average volume has not at least doubled compared with the seven days before the vote. Unspent funds return to the reserve for a later cycle.

The buyback is split into about 23 slices, with liquidity and slippage limits. Current code ends its window on Day 8 with default settings, whereas the specification says “Day 1 to Day 7.” The verdict remains on Day 7. See [The Buyback Bot](buyback-bot.md) and [implementation notes](etat-implementation.md) for this distinction.

## Day 7 · the verdict

The verdict does not arrive at the end of the 72-hour takeover. The code schedules `scanner.verdict` at **168 hours**, or Day 7.

Default thresholds for `revived` are average daily volume at least five times higher **and** at least 10% more holders. For a token on the curve at voting time, graduation can also produce this status. Missing essential data must not lead to an invented verdict.

Both the verdict and its publication require human approval.

## Day 30 · the handover

The community receives the accounts under the handover procedure: Telegram, X, and a website export. The website may remain hosted on the Vivra subdomain. Redirected creator fees remain allocated to $VIVRA buyback & burn under the V1 rule.

Handover is a human action. Details are in [Pons CTO and fees](cto-pons-et-frais.md).