AI Allowance
What It Is
The AI allowance is the organization’s shared account for model work during a month of its own calendar. Its base is either the configured allowance or the Platform default. The first relevant request creates the period when needed, so a new month does not require a scheduled reset of the previous account. Earlier periods remain available for review and correction.
The account separates charged credits from credits held for work still running. Before admitting a request, the ledger checks both amounts together with the new reservation and any temporary capacity active at that moment. This lets concurrent requests make one atomic affordability decision. Completing a request replaces its hold with the settled charge. The reservation is calculated from estimates and a declared ceiling; it is not an absolute promise about final measured spend.
What It Is Not
An allowance is not an application licence, a feature permission or Rhythm’s supplier credit balance. A person still needs the consuming feature’s authority. Exhausting the customer allowance differs from the supplier saying that Rhythm’s own account has no balance. A warned dashboard status also does not prove that a warning email has been delivered: status counts committed usage, while crossings count charged usage.
How It Is Used
Customer administrators need allowance figures to anticipate interruptions and understand renewal. Support staff inspect them when a request is refused. Authorized Rhythm managers can change recurring limits, grant temporary relief or correct charges, with reasons retained in the audit trail. Lowering a limit changes subsequent admission but preserves already running work. Good support compares the refused request’s estimate with remaining capacity rather than assuming that any positive balance admits another request.
Its Facets
Monthly period. The local month keeps base, charged and held amounts together while preserving prior months.
Credit. The customer sees a capacity unit rather than the internal dollar cost of model usage.
Hold. A reservation prevents another request from spending capacity already committed to running work.
Thresholds and notices. Crossings record charged usage once at each threshold and support tracked, bounded delivery attempts.
Limits. Recurring allowance, switches and concurrency settings control new work and distinguish defaults from explicit configuration.
Extra capacity. Grants have start and end instants and can be revoked. Operation exemptions and extra credits solve different admission restrictions.
Correction. Signed changes retain their own record rather than rewriting the original request charge.
Ceilings. Global bounds constrain effective capacity, individual grants and their windows even for authorized managers.
Status. Live balance and access state supply the displayed classification independently of past crossings.
How It Relates
AI operations determine reservations and operation identities. AI requests make the holds and settlements that move the account. AI usage reads its current position and historical periods, while the security audit store retains management attribution and reasons. The notification infrastructure delivers administrator emails; the allowance does not itself define every future notification responsibility.
What It Could Become
The product should choose one coherent meaning of allowance exhaustion across admission, dashboard status and pause notices. It should also confirm the interim Administrator-role recipient policy while responsibilities are being developed. Refunds to missing periods, interrupted settlement and replay of management writes need stronger handling before staff rely on the disabled console controls. These decisions should preserve separate records for limits, grants and corrections.