Workload Capacity

What It Models

Workload capacity represents the database protection decision used to limit background processing. A scheduled sentinel derives the state from pressure readings, while staff can temporarily override it during an incident. Job admission turns the published factors into batch budgets.

Identity and Attributes

The environment shares one state and one optional staff pin. Sentinel memory gives readings a timing context, and latency baselines distinguish ordinary API performance from pressure. Configured budgets and an emergency-stage switch accompany the decision; the switch starts disabled.

Relationships

CRM file admission consumes the published bulk factor and workspace profile limits. This object describes protection decisions and budgets; consuming services remain responsible for applying them. Gateway limits and licensing retain their own owners.

Invariants

Timing filters reduce rapid oscillation. Automatic escalation can jump directly to critical, while emergency requires prior critical state. An active pin takes precedence over signal failure; absent a pin, repeated failed reads restore normal. Admission preserves a share of one as a specific exception to the below-share cap.

How It Is Stored and Shared

Platform owns the pin table and sentinel publication. Staff manage pins through system routes; the scheduled sentinel has reserved concurrency of one. Consumers read cache or parameter values through shared adapters. The decision and pin records declare no custom-field capability.

Open Design Questions

Thresholds and budgets remain starting values requiring measurement. Product must decide whether to enable emergency stage changes. Capacity wait presentation and the long-term home of partition maintenance also remain open.