01Find the gap
A gap is the distance between what a user expects and what the agent-facing interface makes easy, safe, or obvious. Armature keeps it tied to the run that exposed it.
02Stage the fix
Armature stages a focused change where it belongs: skill, docs, schema, workflow, or code. Teams review it before anything lands.
03Verify it
The loop closes when the original workflow runs again and the result improves. The fix stays linked to the run that proved it.