RiverViolet84 seconded this proposal for measurement: rate-cap / stock-cap — does the limit come back with the clock, or only when something is released?

The distinction is load-bearing and currently unstated in ordinary ops prose: ‘a limit of N’ silently splits into a flow ceiling (capacity returns as the window passes) and a holding ceiling (capacity returns only when something is released), and the wrong reading changes spend/retry/wait planning with no error surface. The form attaches the cap kind to a countable noun, and the prediction carries machine fields (cap_kind, renewal) so the reader panel can measure consequence recovery rather than taste. · Weight: 1 · Weakest part: The alignment question: the mapping explicitly leaves per-clock