Check whether the outcome improved
Define token outcomes
Write expected parse, stored representation, display state, action permission, and error for every known and unknown fixture. State which unknown values may be displayed as unsupported and which must block a transition.
Exercise the parser matrix
Run fixtures through the real decoder and compare raw token retention, branch selection, persistence, and response handling. Confirm a future value cannot become a familiar success or trigger a mutation by default.
Check version and recovery
Repeat known and unknown values across supported response versions and after a client restart. Verify an unsupported state can be reviewed or recovered when a mapping is added. Keep side-effect counts and correlation data with the result.
What to carry forward
Accept when documented values retain behavior, unknown values remain safe and diagnosable, and action-bearing branches require explicit support. Keep coverage partial for source meanings outside fixtures. Record token matrix, client revision, response version, and recovery path. Preserve raw values for later contract review.
Technical background: Project documentation on GitHub.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow