Written by an AI agent working in this repository.
Each flagship product in portfolio/flagships.yaml can carry a buildable: field: the work a cloud session can do with no outside input. The router, portfolio/router/allocate.py, prints it as "BUILDABLE HERE" and picks a "Start here" row for each session from the first six free Deepen rows.
On 2026-11-18 the e-invoice validator's buildable: read, in part: "After 2026-11-23: rebuild peppol-next-* from the 3.1.0 tag on master and diff". The rest of the field described work that had already landed. So the one open item could not be done for five more days, but the router still treated the row as buildable. Run records from the last two days show the cost: four sessions were sent there and left (friction_rank.py --live --ungated --days 2, cluster 4), and one on 2026-11-18 at 06:12 said so in its doc_friction about allocate.py.
What changed
allocate.py now reads dates that gate an item ("after", "from", "once", "not before", "no earlier than", followed by YYYY-MM-DD) in a row's buildable:. When one is later than today (UTC) it does two things:
- the task line adds "(NOT YET: an item here is dated after 2026-11-23, so it is not buildable today; take another item, or another row if none is left)";
- "Start here" ranks the row after every free row without such a date. If nothing else is free, it still names the row.
A date in the past gates nothing, so the row comes back by itself on 2026-11-23. Marking it inputs_only: would have kept it out until someone remembered to take the mark off. The pattern ignores dates such as "in force 2027-02-24", which describe a fact rather than a wait.
Checked
- Two new tests in
portfolio/router/test_allocate.py(126 pass): only future dates count, and dated rows come after undated ones, including within a session's spread. - On today's queue the e-invoice row carries the NOT YET note. Today's pick for this session (row 6) did not change.
platform/ci/main_health.py: 270 of 270 checks pass on main.
The note is only as good as the prose. A gate written as "next week" or "once the tag ships" is not read. Those are rare: today the date pattern matches one phrase across all twelve rows' buildable: and next: fields.