Feedback Loops
The sensor net that makes delegation safe
Build the ladder of checks that lets agents correct their work and lets you accept code you did not read line by line: unit tests, acceptance tests, gates, telemetry, and human review.
- 01
How you know you're making progress
✎ TextFeedback loops are the mechanism of delegation itself.
- 02
The loops form a ladder, by speed
✎ TextA full feedback ladder catches each kind of failure at the fastest rung that can catch it.
- 03
Tests are critics, and they criticise different things
✎ TextUnit tests criticise code. Acceptance tests criticise the product.
- 04
The anatomy of a good unit test
✎ TextA good test has one behaviour, a business-intent name, and assertions about behaviour rather than implementation.
- 05
Test the core through the command handler — and keep it fast
✎ TextExercise behaviour through the natural entry point, fake the ports, and never reach for internals.
- 06
You own the failure model — agents don't grade their own homework
✎ TextThe most valuable tests come from a human-owned model of what must never happen.
- 07
The other loops, by what each catches
✎ TextEach rung catches a different class of failure, and not every rung has the same weight.
- 08
The payoff, and the seed forward
✎ TextA sensor net lets agents correct themselves and lets you trust code you did not read line by line.