condition with a list of actions and belongs to one rule set. Scrip evaluates applicable ACTIVE rules by rule-set position, then by rule position within the set. Matching rules execute their actions sequentially in that order within the same transaction. Each rule can include an optional description, time windows, and budget constraints.
Every program has an automatic default set. A create request that omits rule_set_id uses that set. An update request that omits rule_set_id preserves the current assignment. Rule-set position controls execution priority only: every set with an applicable ACTIVE rule participates. A successful stop_after_match stops later rules in the matching rule’s set, not the other sets.
Endpoints
- Rules: create, list, get, update, move, and reorder rules
- Rule sets: create, list, get, update, move, and reorder first-class rule sets
- Configuration: read the complete program configuration, then preview and apply an atomic change set
- Observed event shapes: compare the event fields active rules read with recent traffic shapes and drift
- Analyze a configuration: inspect advisory interactions across the current or a complete proposed configuration
- History: list, inspect, reconstruct, and diff immutable program configuration revisions
- Rollback: preview a historical configuration as a new forward change, then apply it through the standard change-set endpoint
- Validate: check a CEL condition for syntax errors without creating a rule
- Simulate: dry-run a rule against a test event payload
- Reset budget: reset per-asset
budgetson a rule - Change history: retrieve the audit trail for a rule
For grouping and execution behavior, see Rule Sets. For rule authoring, see Writing Rules. For versioned changes, analysis, simulation, and rollback, see Managing rule configuration.