Read Today

GET /api/autopilot/today — the whole signed-in home screen, in order.

items arrives sorted and the client renders it as given: ordering is a judgement about what matters most today, it is made once here, and a client that re-sorted would be a second such judgement that the other two locales' clients would not share.

clear_until is the load-bearing half of an empty list. A screen that says only "nothing to do" sends the user hunting through the other screens to check, and then we have built two products; a screen that says "nothing else is waiting until <date>" and names what falls then is a claim the user can act on. It is therefore the day the next item appears — not the day that obligation falls due, which next_after_clear.due_date carries — so the sentence stays true right up to the morning it changes.

Both are None whenever items is non-empty: "nothing else is waiting" is not a thing to say next to a list of things that are. In the opening phase they are None for a second reason as well — the obligations they name are dated ones (an instalment, a payment term), and someone who has not opened a partita IVA has none. A date invented to fill the gap would be the product inventing a deadline.

phase is carried rather than inferred from the kinds present: the client changes the whole frame of the screen on it (what the empty state says, which nav is shown), and deriving that from "do any of the item kinds start with plan_" would be a second, weaker copy of a decision made once here. It has no default — every construction site states which half of the product it is describing, because the wrong answer is not a missing field, it is a screen telling someone with no partita IVA to go and reconcile their bank.