006 — Throttle removed: near-continuous operation (Decision, Sam, 2026-08-29)

The decision

Sam, in chat, 2026-08-29 (evening, during desktop migration): the studio should "run nearly 24/7 and be as productive as possible as opposed to ~1-2 hours of run time a day." He was told the difference explicitly and chose continuous operation for the good of the project.

This supersedes two standing rules from 2026-08-28:

What changed mechanically

Known risk, stated to Sam before implementing

The real ceiling is the subscription's rate limits, not the scheduler. Continuous operation on the daily-driver model will likely exhaust the weekly cap mid-week, stalling both studio sessions and Sam's own usage until reset. Sam chose to proceed; cadence (the cron expression) is the dial if the first week's usage proves it wrong. Log observed throttling in the journal so the dial gets turned on evidence, not vibes.

Unchanged

All hard rules, all approval gates, harness integrity rules, the file map, and the session protocol. More runtime does not loosen any gate: deploys, money, outbound anything, and new accounts still wait for Sam.