Measure
Satisfaction
You might say: behavioral pass rate, user-fit measure, trajectory score
The fraction of observed scenario trajectories that probably satisfy the user. It measures behavior across the whole run instead of counting only assertions.
- What it does
- Shows whether the factory's changes satisfy users, even when a scenario needs judgement rather than an exact value.
- Ask
- Of all observed scenario trajectories, what fraction likely satisfies the user?
What to look for
- A scenario score with the evidence that led to it
- A trend split by scenario and release
- A threshold that blocks or permits the next run
Sources
- Justin McCarthy (StrongDM), Software Factories And The Agentic Moment, Software Factories And The Agentic Moment
We use the term satisfaction to quantify this validation: of all the observed trajectories through all the scenarios, what fraction of them likely satisfy the user?
Use it on your project
teardown-apply: hold "Satisfaction" (satisfaction) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal