budget

# budget - API budget caps, resets, and the commit-identity gate This skill is the one place that decides how much API budget may be spent and what to do as a limit fills up. It is config-driven: the cap schedule and thresholds live in the credo config, this skill explains how to read and apply them. It also owns the commit-identity gate that must pass before any commit. ## Three axes - never confuse them (B11) There are three completely separate budget axes. Keep them strictly apart; a rule for one never applies to another: 1. The 5-hour API limit - a rolling window that resets roughly every 5 hours. Field `five_hour.utilization` (percent used). This skill governs it. 2. The weekly API limit - a 7-day window. Field `seven_day.utilization` (percent used). This skill governs it. 3. The SESSION context fill - how full the current context window is (the compact axis). This is NOT an API budget. It is governed by the compact-plus skill and its `compact.thresholds` config, not here. Do not mix it into 5h/weekly reasoning. When you say "budget" be explicit about which axis. "5h at 80 percent" and "context at 80 percent" are unrelated facts with unrelated responses. ## Data source: the limit-plugin cache only (B8) The limit plugin is a PREREQUISITE for all budget data. Without a fresh cache, NO percentage-based cap is measurable or enforceable - not the schedule caps and not the fail-safe caps below, because every one of them is a percentage of a number that only ...