Parks CV needs a weekend festival quota bump without permanent entitlement creep. What should Run:ai admins do?
Select an answer to reveal the explanation.
Short Explanation
You can give Parks a temporary quota increase for the festival, then revert it so the extra capacity does not become permanent. Permanently doubling Parks quotas, disabling quotas citywide, or taking emergency-management GPUs without a ticket would create entitlement or operational risk.
Full Explanation
Parks computer vision may need a weekend festival quota bump without turning a temporary event into permanent entitlement. Grant a time-bounded Run:ai quota increase for the municipal event, then revert it so baseline fairness returns for other departments. A ticketed, temporary change helps prevent entitlement creep. Permanently doubling Parks quotas with no end date locks in capacity that other teams may need after the festival. Disabling quotas citywide for the weekend removes guardrails for everyone and can invite uncontrolled resource use. Taking GPUs from emergency management without a ticket creates operational and safety risk and bypasses change control. Exam caveat: a temporary boost needs a clear reversion mechanism; relying on someone to remember Monday can leave the increase in place. Practical check: ticket the change with its start and end times, approving manager, and affected projects; confirm the festival jobs run successfully, verify the quota reverts on schedule, and check that emergency-management quotas were not reduced. A calendar reminder or automated Run:ai API call can support the reversion. Without that follow-through, a temporary municipal quota change can become permanent entitlement and erode trust among Parks, emergency management, and platform admins.