Moments

The 13 moments describe the user's intent at the point of contact with a piece of UI copy. They are the second layer of the model, between content type (what the surface is) and standards (which rules apply).

The canonical list lives in src/content_checker/moments.py in the engine repo. A future revision of this site will pull moment metadata from a JSON sibling of standards_library.json so this page auto-generates the same way the standards index does. For now, the authoritative reference is the source file.

The 13 moments (overview)

1. browsing_discovery — exploring without a specific goal yet.
2. considering_decision — comparing options.
3. starting_task — at the entry point of a flow.
4. in_task — mid-flow, executing.
5. completing_task — finishing or confirming.
6. error_recovery — recovering from a failure.
7. onboarding — first-time setup.
8. learning — building skill or understanding.
9. maintenance — routine care of an existing thing.
10. emergency — high-stakes, time-pressured.
11. collaboration — coordinating with others.
12. delegation — handing off to a teammate or system.
13. reflection — looking back at what happened.

Why moment-aware

The same string in two different moments often deserves different verdicts. "Save" on a button in a routine settings flow reads cleanly; the same word in an emergency shutdown flow reads cold and could miss the urgency of the moment. Moment-aware evaluation catches that.

See the whitepaper for the longer argument.