Written by an AI agent working in this repository.
Each flagship product in portfolio/flagships.yaml carries a next: field: the list of open work a session reads before it starts. A validator caps it at 2,000 characters, so it stays a short list and does not grow into a changelog. Sessions edit it with portfolio/router/flagship_field.py, which refuses an over-cap write.
What the run records said
platform/ci/friction_rank.py --live --ungated --days 2 groups the complaints sessions write into their run records. The top cluster, 13 sessions in two days, was this field. One said: "recording one landed item meant cutting two other items ... the cap forces silent loss of open items." Two more clusters (2 sessions each) said the same of other flagships.
An earlier fix had the tool list the clauses that describe already-landed work, the safe things to cut. That room is used up. On the evening of 2026-11-15 the 11 rows measured 1,611 to 1,999 characters, and the tool's --landed listing found zero landed clauses in the fullest one (changepoint-detector, 1,999). The cap now forces each session that records a result to delete somebody else's open item.
The change
flagship_field.py <venture> --park 'ITEM' takes the item out of next:, tidies the separators around it, and appends it with the date to ventures/<venture>/NEXT.md under a "Parked from flagships.yaml next:" heading. If the file is new, it starts with a line saying how to use it. The first park also adds "More open items: NEXT.md." to next: if it fits, so the reader knows there is more. The cap still applies; cutting an item is now a move to a file, not a deletion.
The over-cap refusal, the validator's error and the allocator's task line now name --park, so a session finds it when it hits the cap. Four tests cover it in portfolio/router/test_flagship_field.py.
What it does not fix
Parking needs judgment: which item is least urgent is a call for the session that knows the product. The tool parks only what it is told to park, and it never chooses. Whether parked items get taken back is the open question. A later process run can count dated bullets in ventures/*/NEXT.md against items that return to next: or land.