CONTROLLED EXECUTION
Where does human judgment sit in an agent workflow?
Follow one request through scoped context, approved tools, a human decision, and a retained trace.
Skip the guided view01Scope
Define the task and its stopping point.
The harness receives a request to reconcile one invoice. It knows the permitted sources, expected output, and action it cannot take alone.
- May
- Read invoice and contract
- May not
- Send or approve payment
ResultA bounded run with explicit permissions.
ILLUSTRATIVE CONTROL PATTERN
02Context
Load only the evidence needed for this run.
Current contract terms and invoice details enter the working context with source references. Irrelevant client files stay outside it.
- Current contract clause
- Invoice line items
ResultA task-specific briefing with visible provenance.
03Tools
Use narrow capabilities for specific work.
The agent can read approved records and draft a correction. A separate permission boundary blocks sending or changing the accounting record.
- Read
- Contract and invoice
- Draft
- Correction note
- Blocked
- Send and payment approval
ResultPrepared work without an unauthorized side effect.
04Decision
Pause where responsibility changes hands.
The operations lead sees the discrepancy, source clause, and drafted correction before choosing whether to proceed.
- Decision owner
- Operations lead
- Evidence
- Invoice, clause, proposed response
ResultA consequential action remains with its accountable person.
05Trace
Return a record of the run.
The trace records what was read, which skill version ran, what was proposed, who decided, and what happened next.
- Inputs
- Tool calls
- Decision and outcome
ResultA run that can be reviewed and improved.