Judge record freshness against review cadence; record Utah review dispositions - #13
Merged
Merged
Conversation
Record pages aged the verified badge with fixed 90/180-day bands, so active Utah records past their 90-day cadence showed "aging" instead of overdue, and 365-day historical remaps showed "aging" while current. Home countdowns were frozen at the build-clock date. - Move the cadence policy into scripts/lib/verify-policy.js so verify.js and build.js share one source. - Emit data-review-days on each record badge; tables.js labels records past cadence "review overdue". - Emit data-date on upcoming countdowns; tables.js recomputes days against the reader's date. Generated HTML stays deterministic; only the browser view ages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent source-consistency review for issue #3 (PUB-1). Each of the five statutes, the JIA and the three RMAs is source-consistent with open editorial findings (42 open discrepancies in total). No record edits and no last_verified renewal; human review decides renewal, and corrections go through prepare:admission receipts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
data-review-daysfrom the sameproject.ymlpolicyverify.jsenforces, andtables.jslabels records past cadence "review overdue".data-dateand is recomputed in the browser.scripts/lib/verify-policy.jsso the gate and the site share one source.ops/evidence/utah-overdue-dispositions-2026-09-23.json: agent source-consistency dispositions for the nine Utah records overdue in Knowledge drift detected #3 (five statutes, the JIA, three RMAs). All nine are source-consistent with open editorial findings (42 open discrepancies). No record edits and nolast_verifiedrenewal in this PR; corrections follow separately through admission receipts.Generated HTML stays deterministic; only the browser view ages. Merging deploys Pages.
Test plan
OBLIGATION_FIRST_DIR=../obligation-first npm run verify:cipassesnode --test tests/*.test.js(59 pass) andnpm run evalspassnpm run verifystays nonzero: the nine records remain truthfully overdueRefs #3
🤖 Generated with Claude Code