`verification/daily-catchup-decision.txt`

12 lines

task_id: TK-11326; owner/finalizer: root Codex; delegation_chain: root -> DTD reviewers; depth1; no redelegation.
Read-only design review only; no edits, external writes, publishing, billing or credentials. Parent records evidence on canonical ticket. Zero-cost model mode mandatory.

Steve told the assistant 'start loading for the day now' after 37 DW vendor products had activated today and the21/hour slot was full. He previously explicitly authorized skipping Gemini for the fixed504 provider-outage-held vendor cohort;21 known BLOCKs remain excluded and21 of483 candidate records were already activated, leaving at most462 authorized candidates before fresh checks. Daily cap500 leaves463 available slots. The requested operational result is loading today's remaining eligible products now.

Choose implementation:
A: Explicit date-bound one-time catch-up authorization for2026-09-09/TK-11326, activated only by a dedicated CLI flag. Skip hourly pacing for this invocation only, never increase the500/day cap or owner cohort. Invalid/stale dates and midnight crossing stop. Fresh data/vendor/price/sample/known-BLOCK guards and zeroGemini policy remain. Default scheduled path stays21/hour. Hold the existing singleton lock; live read-only plan + independent before-state + one-product canary and full batch verification.
B: Permanently remove the hourly pacing for every scheduled run and raise the daily cap if candidate supply exceeds500.
C: Leave the user's day-loading request waiting until the next hourly slot without implementing a catch-up path.

Pick exactly one option. Begin your answer with VERDICT: <option> on its own line, then one paragraph with main risk and one concrete regression test. Implementation advice only, not legal advice.