Production Incident Agent
See how an AI request can move through application access, credential evidence, tools, policy, and consequential actions. This synthetic example demonstrates the relationships HAIEC can represent when the relevant evidence is available.
Interactive React Flow diagram with lens/zoom controls and node inspector. If the diagram does not load, switch to the Text / HTML version.
Action to Consequence
Trace what AI can do, how authority and controls narrow it, what was actually evaluated, and exactly where the evidence ends.
System Constellation
Limitations
- Illustrative sample data: not evidence
- No runtime observation connected
- Delegation not established
- Credential evidence: limited
- Synthetic high-action scenario: demonstration values only
- …and 2 more
How to read this view
CTO questions this view should answer
- What untrusted data can influence the agent before a consequential action?
- What identity does the action execute under, and what is effectively granted versus policy authorized?
- Which consequence-resolving choices are still model-selected or unknown?
- Do synchronous, async, MCP, webhook and fallback paths cross equivalent controls?
- What can the system mutate, send, delete, authorize, schedule or execute?
- Which parts are source-proven, runtime-observed, policy-declared, partial, or unknown?
Truth semantics
Production edges need source Evidence, time basis, confidence and stable identity. A missing route-local guard is not automatically an unsecured endpoint.
High-value derived CTO insights
Residual discretion · policy-vs-code capability excess · effective overgrant · weakest-path control parity · late/audit-only controls · unbounded consequence dimensions · retry/idempotency multiplier · context trust gaps · topology change since evaluation · evidence blind spots · containment/witness limits.
Framework crosswalk (mapping only – not certification)
Accessible topology details
Limitations
- Illustrative sample data: not evidence
- No runtime observation connected
- Delegation not established
- Credential evidence: limited
- Synthetic high-action scenario: demonstration values only
- 3 review paths / 9 CODE_CAPABLE / 2 OBSERVED / 5 evidence gaps are demonstration values only
- REQUESTED means an explicit customer/operator declaration, not prompt or user input