Most software changes when a vendor ships a release. AOS8 is built to improve continuously, from what it sees in your own work. That only makes sense if every improvement is controlled. The loop is that control.
The left side: agents propose
- Scout spots it. An agent that watches how work actually runs notices a pattern, such as a step that keeps waiting on a person. It reports what it saw, with the numbers.
- Drafter proposes a change, and previews it on your past work, so you can see what it would have done.
- Critic reviews it, and the way back is planned before anything moves.
Each of these is a different agent. The one that proposes a change is never the one that reviews it.
The diamond: you decide
Everything on the left is a proposal. The two halves never touch, so nothing reaches the right side without passing the diamond: a decision. A person approves it or rejects it, and a rejection goes back to the agents with the reason. For routine items inside limits you set, two agents that have each earned their vote may decide. An agent never approves its own work.
The right side: the change runs
- It rolls out a little at a time.
- It is watched against the target it promised.
- It is kept, or rolled back. If it misses its target, it goes back, and the agents learn from the result.
Then the agents look again. That is why the shape is a loop, and why it does not end.
What moves through the loop
- Your processes. A step that slows your team down gets a proposed fix.
- Your agents. An agent with a good record is proposed for more responsibility, and a person decides.
- AOS8 itself. The system is built by the same process it gives you, under the same approvals.
Why "under oath"
A witness under oath has to tell the truth, on the record, and answers for what they say. The loop holds every improvement to that standard. When an agent argues for a change, every figure it uses is checked against the record before it is shown as fact. Every proposal, decision and change is written to a record that is witnessed outside AOS8, so anyone can check it later.
In freight
In Flowwolf AOS, the freight back office built on AOS8, a pass of the loop might start when Scout sees that 14 of 40 carrier invoices waited more than two hours on a person. Drafter proposes letting the billing agent check routine matches under the limit. The controller previews it on last month's invoices, approves a two-week trial, and the result is measured. The figures are illustrative; the path is the same every time.
You can pause the loop with one click. Your processes keep running, and every way back stays open.