Decision turns Signals into run, wait, or stop states so the right human, agent, or policy path can act with context.
- Run
- Wait
- Stop
- Escalate
Decision
The queue where humans, agents, and policy decide what happens next.
Decision gives operators one surface to review Signals, approve bounded action, ask for more context, or stop work before risk moves downstream.
Map shows where the Decision sits, which systems are affected, and what Proof must be recorded after the action.
- Composition: signal-decision-proof
- Hub: Map
Decision operating boundary
One surface. Three questions.
See what the surface owns, inspect its production contract, then continue through the connected governance loop.
01 / 03 See the boundary
Decision owns the queue.
Decision routes whether the next step can run, must wait, or should stop with a named owner.
RUN WAIT STOP
Signal
A watched source says something changed or needs attention.
Decision
The queue routes the update to a human, agent, policy rule, or stop point.
Map
The map keeps the owner, system boundary, and downstream impact visible.
Proof
The decision produces evidence, outcome, receipt, audit trail, and rollback note.
Evidence
- Signal: A watched source says something changed or needs attention.
- Decision: The queue routes the update to a human, agent, policy rule, or stop point.
- Map: The map keeps the owner, system boundary, and downstream impact visible.
- Proof: The decision produces evidence, outcome, receipt, audit trail, and rollback note.
Receipts
Surface: queue4 connected states
02 / 03 Inspect ownership
The boundary stays small enough for operators to inspect.
In production, Decision is required because it owns review owner, run-wait-stop state, allowed action, escalation and policy reason.
Decision owns the named review owner, allowed action, escalation reason, policy reason, and current run-wait-stop state.
Decision should not start from a vague task. It consumes a Signal with source context, affected system, and reason to review.
Decision produces the minimum proof needed for the next operator to understand what happened and why.
Evidence
- The review owner
- The incoming Signal
- A proof requirement
Receipts
review ownerrun-wait-stop stateallowed actionescalation and policy reason
03 / 03 Continue with context
Atlas connects this surface to the rest of the governance loop.
Production workflows need Map, Signal, Decision, and Proof attached to the same operating boundary.
Evidence
- Signal
- Map
- Proof
Receipts
Signal inboxMapProof graphProduct overview
Decision implementation
Attach this surface to a real workflow.
Start with one live workflow, connect the source signal, name the decision owner, and decide which proof record must survive the action.
- Owner
- Decision operator
- Authority
- Decision production contract
- Proof
- Connected workflow receipt
- State
- review
- 01 / Queue Define the operator action
Decide what a reviewer can approve, reject, route, request, or stop.
- 02 / Policy Name the decision rule
Turn hidden judgment into a policy rule or owner approval path.
- 03 / Proof Require the evidence
Make the queue ask for the proof record before the workflow moves on.