# Journey 4: a buyback slice (UC-17, UC-18, UC-08)

1. At buyback start, the Buyback Bot draws about 23 random times over 7 days and stores them encrypted.
2. At each scheduled time, it calculates the size: at most 1% of pool liquidity, within the remaining cap.
3. It calls `buyAndBurn` on BuybackBurner: purchase and burn in the same transaction.
4. Tracking reads the event; the war room and ledger update; the X bot posts the slice.
5. On Day 3, if average volume has not doubled, remaining slices are canceled and unspent funds move to the next cycle.

Edge cases in the specification:

- Slippage above 2%: postpone the slice by 1–3 h, with no larger purchase afterward.
- Empty hot wallet or balance below minimum: suspend the slice and alert.
- A token graduates from the curve during buyback: stop at graduation.
- Emergency stop: no further slices for that CTO token.

For differences between these source rules and implemented slice rejection and window behavior, see [Implementation status](etat-implementation.md).