Task health
Separate running, waiting, blocked, failed, and completed tasks. A task waiting on approval should not be reported as a technical failure.
OPERATE / OBSERVABILITY
Operational visibility should connect agent health, task outcomes, model usage, latency, costs, incidents, policy blocks, and human escalations. See where work is moving and where it needs attention.
02 / THE OPERATING CONTRACT
Separate running, waiting, blocked, failed, and completed tasks. A task waiting on approval should not be reported as a technical failure.
Inspect which capabilities and systems a workflow used. Capture latency and tool errors without hiding the business context.
Track compute, model, tool, and task costs with explicit attribution. Optimization suggestions need quality and privacy checks.
Connect a failure to its agent version, tool request, policy decision, and recovery step. Route unresolved events to a responsible owner.
03 / CONNECTED BY DESIGN
Inspect the sequence.
Each stage has a defined responsibility.
Select a node to inspect its role in the workflow.
Define the source of truth, permitted actions, accountable owner, and acceptance criteria. Scope matters more than an open-ended instruction.
Check the outcome, capture unresolved exceptions, and preserve the relevant policy and evidence. A task is complete only within its defined boundary.
04 / A CONCRETE EXAMPLE
Northstar’s illustrative dashboard separates policy blocks from tool failures and review queues. A prohibited request stopped by FIN-04 is a functioning boundary. A data source timeout is a reliability incident. Each has a different owner and next step.
Use verified business outcomes alongside latency and cost. A fast, cheap task that used the wrong data is not a successful task.
05 / QUESTIONS & BOUNDARIES
Architecture descriptions show intended system behavior. Validate implementation, integration, data handling, and operational controls before relying on a production workflow.
No. Any displayed agent counts, task totals, and percentages are fictional interface examples.
The affected task, relevant versions, timing, data and tool context, impact, owner, and the recorded recovery action.
Identity, context, policy, evaluation, verification, execution, and audit form one operating model. Explore the related components below to see their responsibilities.
06 / CONTINUE THE EXPLORATION