Record Before Admission and Reserve With One Conditional Update

Context

Concurrent staff and jobs can request model work against the same organization’s capacity.

Decision

Create the request before reserving its estimate and running slot through the conditional monthly update; treat the current reservation sizing policy as proposed.

Alternatives Considered

Reserve only a typical conversation cost: It admits work before its full configured reservation is covered and can reveal overspend only after usage.

Check balance before a separate unconditional hold: Competing readers can each accept capacity that only one request can consume.

Create bookkeeping after holding credits: Interruption can leave a hold with no request record to inspect.

Add a daily spending budget: The existing throttling decision avoids another budget period and its effect on legitimate batch work.

Consequences

The hold predicate serializes competing admissions under current capacity. Reservation size can cause refusal before displayed usage is exhausted. Holding credits and recording their amount remain separate transactions. Allowance refusal takes precedence when both allowance and concurrency predicates fail.