A cheap architecture checker can keep coding agents honest
A can use an diagram as a real checking tool, not just a pretty document. The useful setup is , where the system is laid out as a timeline of cause and effect. An event leads to a reaction, the reaction creates a command, and the command creates another event.
This gives every part a rule: it should have a clear cause or result. A simple graph check can then inspect the cause-to-effect links without asking the model to make a vague judgment. It can return clear gaps, such as an event with no cause, a command with no resulting event, a policy that connects nothing, or a card that sits alone.
That gives the agent a based on fixed rules instead of tired or overconfident guessing.
Key points
- The diagram becomes something the agent can check, not just read.
- turns system behavior into linked causes and effects.
- The checker finds missing causes, missing results, empty connections, and isolated cards.
- A gives cheaper and more consistent feedback than model judgment alone.
- This can reduce false “done” claims from .