Packet completeness
100%
Required context present
HAAM Agent OperationsControl loop prototype 01
Checkpoints, handoffs, audits, responsibility
Every action leavesa path another agent can follow.
A visible operating system for agent work.
Each run carries its goal, evidence, permissions, decisions, unresolved questions, artifacts, current owner, accountable human, and precise resume instructions. Work can move between agents without losing context, while independent gates prevent one agent from quietly approving its own output.
Run HAL-2026-071in progressHigh risk
Current operational run
Checkout accessibility remediation
Remove the keyboard trap and missing error association from the checkout address step without changing payment behavior.
- Updated
- 07 Jul 2026, 13:42 EEST
- Lease
- Active for 18 minutes
Evidence
2/3
Checkpoint records attached
Questions
0/1
Resolved before progression
Confidence
78%
Visible estimate, not a claim
Resumable state
The handoff packet
- In scope
- Checkout address form, validation messages, focus order, and regression tests.
- Outside scope
- Payment provider, pricing logic, visual redesign, and production deployment.
- Exact resume instruction
- Run the manual Safari and VoiceOver case, attach the result, resolve the open question, then request human approval.
Evidence required to pass
Keyboard path recording
Before and after focus sequence captured for the address form.
artifact/focus-path.json
Automated accessibility check
Targeted axe run has no critical or serious violations in the changed step.
artifact/axe-checkout-address.json
Screen reader error announcement
Manual result still needs confirmation in the second browser and screen reader pair.
artifact/manual-test.md
Open checkpoint questions
Does the error announcement remain understandable in Safari with VoiceOver?
Owner: Verification agent
Artifacts
- v3
checkout-address.patch
Code diff
- v2
focus-path.json
Interaction trace
- v1
axe-checkout-address.json
Test result
- draft
manual-test.md
Review notes
Recorded decisions
- 01Keep the existing visual treatment and change semantics only.
- 02Move focus to the first invalid field after submission.
- 03Associate each error through aria-describedby instead of a global live region alone.
Visible assumptions
- ?The payment provider iframe is unchanged by this patch.
- ?The existing browser support matrix remains current.
Checks and balances
Control policies attached to every run
MC-01
Maker-checker separation
The agent that creates an artifact cannot independently verify the same checkpoint.
HO-02
Complete handoff packet
A transfer requires goal, current state, artifacts, evidence, decisions, unknowns, and the exact next action.
IR-03
Irreversible action fence
Publishing, payment, deletion, outreach, permission changes, and production merges require a named human approval.
EV-04
Evidence before progression
A checkpoint stays blocked when required evidence is missing or acceptance criteria are not testable.
OS-05
Ownership stays singular
One active responsible owner and one accountable human remain visible at every point in the run.
ST-06
Stale work escalation
A run without a heartbeat, valid lease, or reachable owner is returned to the orchestrator for reassignment.
The operating contract
Continuity is designed into the work packet.
01
State before personality
The run belongs to the system, not to one agent session. Goal, scope, permissions, evidence, and status persist independently of whoever is working.
02
Typed handoffs
Every transfer includes completed work, artifacts, assumptions, unresolved questions, blocked decisions, and the exact next action.
03
Maker-checker separation
Execution and verification are assigned to different roles. High-impact actions cannot pass through self-approval.
04
Human accountability
One named person remains accountable for consequences, exceptions, publication, and irreversible actions.
05
Blockable checkpoints
A checkpoint can stop progression when evidence is missing, scope changed, confidence is too low, or required review has not happened.
06
Complete visibility
The audit trail records who acted, what changed, why it changed, which evidence supported it, and who accepted the result.
Build the real workflow
Turn a recurring process into an accountable agent system.
HAAM can map the work, define permissions, design the handoff contract, connect tools, add review gates, and build the operational interface around the agents.