# Recover after two weeks away, however full the inbox got

**Come back from a gap and find what is on fire, and the one step that gets you back in control, without wading through everything that piled up while you were gone.**

`control/assurance.md` sets a measurable bar for this: fourteen days without a review and a hundred captures, and the risks have to be locatable in ten minutes. Recovery has no view of its own: it is `get-next` asked five ways, in a fixed order — risks, deadlines, waiting, blocked, and then the one next action — and none of them requires the inbox to be empty first: a hundred untriaged captures sitting alongside the real risk changes nothing about finding it.

Driven by a person and an agent. Every step below is a step in
`packages/server/tests/e2e`, run against a listening server on every pull
request; the calls under each one are what that run executed.

The same flow is playable at https://flow.ttoss.dev/docs/examples/recover-after-an-absence.

## 1. Ana starts a project

- `POST /api/v1/projects` → `201`

## 2. A hundred untriaged captures pile up — the noise a real absence leaves

- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`
- `POST /api/v1/captures` → `201`

## 3. Four real things are also true: a high-consequence task, a near deadline, something waiting, something blocked

- `POST /api/v1/tasks/batch` → `200`
- `POST /api/v1/tasks/batch` → `200`
- `POST /api/v1/tasks/batch` → `200`
- `POST /api/v1/tasks/batch` → `200`

## 4. Fourteen days pass with nobody reviewing anything


## 5. Ana asks for the risks first: prioritised work nobody confirmed in time

- `GET /api/v1/next?slice=risks` → `200`

## 6. Then the deadlines, soonest date first

- `GET /api/v1/next?slice=deadlines` → `200`

## 7. Then what is waiting on somebody, and what is blocked

- `GET /api/v1/next?slice=waiting` → `200`
- `GET /api/v1/next?slice=blocked` → `200`

## 8. And last the one next action — the hundred captures notwithstanding

- `GET /api/v1/next` → `200`