Field guide · read at your own pace
Promise-to-Process Test
Put the stated purpose beside the process that delivered it. You do not need to fill anything out. Use the lines below as a way to notice what the first description left behind.
Boundary: Keep the later record in the main case. A repair can narrow the finding, and complexity alone does not prove drift.
What to notice
Follow the lines without forcing them into one score.
Some lines will matter immediately. Others may stay unknown. That is useful: an honest blank is better than a confident guess.
- Stated promise
- First delivery
- Burden moved
- Repair
- Later record
- Persistence, mismatch, or unknown
Worked example
Hypothetical one-form service
- Promise: one form and one clear decision path
- First delivery: separate owners, notices, and correction channels
- Repair: one handoff was consolidated after the first release
- Later record: improved, unchanged, newly broken, or not yet measured
Where this method stops
Do not make the guide claim more than the record
- A mismatch does not establish motive, deception, or permanent failure.
- The later record must be comparable enough to show whether the original burden changed.
Transfer: Use the test on a public program, customer-service promise, school process, workplace system, or regulated service.