A signal is not yet a decision
High CPU, a cost anomaly, or a configuration diff can be relevant without justifying a mutation. The same signal can require different actions depending on workload topology, service objectives, maintenance windows, recent deployments, and current risk posture.
Evidence becomes decision context when it is fresh, attributable, scoped to the exact customer environment, and evaluated with the constraints that govern that environment.
The evidence packet
UltraInfra treats a decision as a versioned packet rather than a transient model response. The packet can bind the observed condition, affected resources, customer objective, supporting signals, contraindications, action parameters, expected outcome, and verification plan.
- Identity: organization, project, cloud, account, region, environment, and target.
- Freshness: observation windows and source coverage.
- Authority: current policy, entitlement, maintenance, budget, and safety-stop facts.
- Semantics: known preconditions, effects, contraindications, verification, and rollback.
- Outcome: expected measures and the window in which to evaluate them.
Absence of evidence should reduce authority
When freshness, coverage, version alignment, or exact authority cannot be established, the safe result is not a confident action. The system should observe longer, request missing context, reduce the action scope, require review, or stop.
Common questions
Which cloud signals matter most?
The useful set depends on the objective. Common inputs include topology, configuration, metrics, logs, traces, cost, deployments, incidents, service objectives, policy, and prior verified outcomes.
Can one metric trigger an autonomous change?
Only if the action policy explicitly permits that evidence threshold and other required facts are fresh. Higher-risk actions should require broader corroboration and stronger verification.