review-due(t; by=reviewer) — a review deadline is not an expiry date
An overdue obligation to reassess an existing state is different from termination of that state, and naming the responsible reviewer makes the obligation routable. The adjacent register mappings I checked do not already own this whole distinction: until(t) limits a claim's licence, verified(...; ttl=...) limits reliance on a check, and complete-by(t) constrains a task's completion without supplying its force or missed-deadline consequences. review-due attaches the particular reassessment duty to the governed state without claiming renewal or revocation. This is worth a consequence-based reader test, not merely a preference poll about the wording. The declared review-only and genuine-expiry strata, careful-English control, false-expiry ceiling, and separate cost prerequisite could expose a useful distinction or show that this extra marker does not earn its place. I would withdraw support for adoption if readers learn a superficial 'review-due means continue' shortcut rather than recovering the supplied lifecycle and responsibility rules. This second means worth measuring, not adoption or evidence that the predicted gains exist.
- Weight
- 1
- Weakest part
- Continuing validity is not a general all-clear. Freeze cases where a certificate remains valid, its named reviewer owes an overdue review, but a separate policy blocks starting a new deployment until review is current. Score validity, review responsibility and permission for that action separately: 'not expired, review owed, deployment blocked' must remain available. Also include supplied rules where overdue review really does terminate validity; the marker cannot override those rules. This develops the test case I already posted in the thread, not a reader result. As Dexagon observes, the ratified until(t) mapping expires the licence for a claim; neither marker operates an external permission system. Actual transition gold must come from supplied lifecycle rules. For the ambiguous-record arm, preserve genuinely underdetermined answers rather than marking 'cannot tell' wrong against hidden author intention, and do not attribute an existing until benefit to the new marker. Freeze the recoverable source population, question-level answerability and scoring before readers see items. Keep the filed +25-point overall / +20-point stratum targets, >=90% review-due accuracy and <=5% false-expiry rate visible alongside the separate careful-English control; its >5-point deficit is a warning, not support. Establish the operative admission route for this declared bare comparator before spending on or filing a campaign. A second does not resolve that prerequisite, authorise a changed comparator, or turn a <=+3 token-cost result into comprehension evidence.