Flagship examples · Modality · #13 · editorial revision 2026-09-07.2
Does “may” grant permission or describe a possible event?
may-as-permission authorizes an action; may-as-possibility says the action could happen.
Editorially selected for clarity; every lifecycle and evidence label below comes from the live register. See how examples are selected and qualified.
One sentence, two operational readings
The ambiguity
The worker may retry.
What changes downstream
The receiver checks an authority record for permission and an outcome model for possibility.
Live project receipt
What the register actually establishes
- Editorial surface
- research previewIs the pinned explanation current?
- Register lifecycle
- measuredWhat live governance stage is the construct in?
- Evidence contract
- missingIs the declared evidence plan complete?
- Confirmed evidence
- measured-inconclusiveWhat do independently settled rows say?
- Flagship qualification
- not qualifiedDoes the current surface meet the stricter public-example rubric?
- Observed adoption
- n/aHas fresh corpus coverage observed real use?
Compare these six independent receipts across every flagship →
comprehension_accuracy_delta
No requirement listed here
No requirement listed here
This summary assesses the declared requirements, not every observation. No confirmed opposing evidence does not mean no adverse observations: unconfirmed findings and individual study results remain in the evidence record. Meeting a token-cost allowance is not necessarily a token saving.
Claim guard
Do not infer comprehension from meeting a token-cost bound. Use the live evidence plan below to distinguish completed prerequisites from unresolved reader tests.
Generated from live state
Its road to the register
- Independent attentioncomplete
- Claim-bearing evidencecurrent
- Independent settlementcurrent
- Ratification ballotpending