Corrections log

Rogata reproduces official records. When we get something wrong ourselves, the fix is recorded here — publicly, with the date and what changed.

Our corrections policy

Official changes are not corrections. If the official record changes — a new status, an amended text — our record follows it, and the change is listed under Recent changes, not here.

Our own errors are corrections. If Rogata publishes something wrong — a mis-transcribed word, a wrong date, a broken source link, a fingerprint that does not match its record — we fix the record and add an entry here saying what was wrong, what it says now, and when it was fixed.

Translation errors follow the same policy. A corrected translation is listed here like any other correction, naming the record and the text involved.

Corrections

• October 28, 2026 — SB22-029: the official summary in our dataset was scrambled — it began mid-sentence and carried fragments out of order (a defect disclosed here as a known issue when the Verified Record layer launched). The cause was in our own parser, which misread summary paragraphs that mix text with inline markup. The parser is fixed, the record was re-parsed from the official page, and the summary now reads exactly as published. The same parser defect had also displaced one line of HB18-1073’s summary; that record is corrected too.
• October 28, 2026 — SB24-197 and SB23-177: the official pages print each act’s approval and effective-date lines inside the summary block, and our parser had folded them into the summary text (“…by Governor May 29, 2024 APPROVED August 7, 2024 EFFECTIVE…”). Those lines are status information, not summary text, so the summaries now carry only the summary itself; the dates remain in each record’s status and action history.
• October 28, 2026 — Listing fields: the summary-level records drawn from the legislature’s search listing disagreed with each measure’s own record — 16 bills from earlier sessions were labeled with the current session, 6 joint resolutions were typed as “Bill”, and 3 long titles were cut short by the listing. All now match the measure’s own official record (SB22-029’s session is the 2022 Regular Session), and the data pipeline now takes these fields from the detail record on every refresh, so the listing is corrected from the measure’s own page each time.
• October 28, 2026 — Source links: on 50 state records, the official-source link carried the bill slug in uppercase (…/bills/SB22-029) while the record itself uses the lowercase form. The links now match each record’s own official page address exactly.
• October 28, 2026 — Spanish summaries: the labeled Spanish translations for SB22-029, SB24-197, SB23-177, and HB18-1073 were made from the defective texts above and carried the same defects. They have been corrected to match the corrected official summaries, and their translation dates updated to the correction date.

Report an error

Every bill page names its official source, links to it, and shows the record’s SHA-256 fingerprint under “Verify this record” — checking a record takes a minute. If something here does not match the official source, contact Progress 4 All through progress4all.com and tell us the bill number and what differs. We will check it against the official source; if we are wrong, the correction appears in this log.

Known issues — not yet corrected

Defects we already know about are listed here as known issues, not corrections. When one is fixed, the fix moves to the corrections log above.

No known issues are outstanding. The two issues previously listed here — SB22-029’s damaged summary and the search listing’s session labels — were corrected on October 28, 2026, and are recorded in the corrections log above.