Typed scope, tool allowlist, spend ceiling, and approval requirement are checked before execution.
The goal and safety boundary stay human-controlled; autonomy starts only inside that approved boundary.
Investigate the live GitHub platform status, reconcile component health and active incidents, then produce an evidence-grounded operational brief.
GitHub Status API + NIST policy corpusTyped scope, tool allowlist, spend ceiling, and approval requirement are checked before execution.
The goal and safety boundary stay human-controlled; autonomy starts only inside that approved boundary.
The input schema, source allowlist, rule version, and approved outcomes are validated before any source is called.
This is a production strength: every permitted input and outcome is explicit, testable, and reproducible. Its boundary is the model encoded here.
Run both lanes to stream the agent’s cited conclusion here while its trace is still visible above.
Run both lanes to evaluate the versioned rules against the same live facts.
Use rules for the known, repeatable boundary. Use the agent only where evidence can be ambiguous, the next useful action depends on what was just observed, or multiple findings must be reconciled.