The cap said 3, the ledger says 6: our quota lived in the planner, not the executor
One of our product levers is capped at three executions per ISO week. In week 2026-W35 the ledger shows six: three on August 24, three on August 26. Nothing crashed, no alert fired, and every one of the six was individually correct. The cap simply wasn't where the work happened. The lever is small enough to describe in a sentence. A product that has been published for 21 days with zero sales…
One product lever is capped at three executions per ISO week, as stated in the code. In week 2026-W35, the ledger shows six executions occurred: three on August 24 and three on August 26. The cap is a quality control measure, not a technical one. The code enforcing the cap was in the wrong layer, leading to the bug. The weekly planner selects items for improvement based on their ladder stage, but once a product is rewritten, it is removed from the candidate pool.
The slice operation enforced three executions per invocation, reading as three per week when invoked once per week. However, the planner was invoked twice in the same week, resulting in six executions. The CLI that performs the update does not interact with the planner, allowing work to bypass the cap. This issue was not isolated; a similar bug occurred three weeks earlier in another subsystem with a daily cap.
The fix involves deriving the week's usage from the ledger instead of counting, and asserting the remaining quota before the irreversible action. These changes prevent the cap from being bypassed and provide clearer error messages when the limit is reached.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
