How we verify what we publish

Statute text#

Statute text on this site is extracted by a repository script from the Revisor of Statutes website. Its configured targets are Chapters 308A, 308B and 308C and only section 80A.461 of Chapter 80A. The parser normalizes the extracted text and stores structured data with a SHA-256 hash ^P1. A hash identifies that captured text; it does not prove that extraction was complete, that a provision was correctly classified as operative or repealed, or that the capture is current.

The Revisor's published text is the authority. The stored copy is a convenience, and each statute page links to the Revisor's page for the section.

A successful fetch from a live citation URL establishes what that page displayed when accessed, not all law effective on that date. Check the displayed statutory edition, section history, intervening session laws and effective dates for the question at hand. The stored edition or capture date is not proof that no later enactment applies. Agency and federal sources likewise need source-date and applicability checks.

Commentary pinned to the text#

Each annotation records the first twelve characters of the captured section's hash in an anchor. A mismatch is a structural check failure when the checker runs, and the site flags affected commentary. A mismatch can result from a legislative amendment, a parser correction or changed source markup; it does not by itself prove that the law changed. Matching anchors likewise do not prove a correct legal interpretation, freshness or attorney review.

Annotation coverage uses the parser-derived corpus as its denominator. The restored corpus has 87 annotations for 87 sections classified as live in Chapter 308B. That is an internal coverage count, not independent proof that every operative provision was extracted or legally reviewed.

Automated checks#

The repository configures CI for pushes to main and pull requests. When run, the content checker checks structural conditions including:

• cited source identifiers and statute sections exist in the local registries;
• internal links and related-page references resolve;
• each captured 308B section classified as live has an annotation with a matching anchor;
• content dates are not in the future;
• pages outside the about and glossary sections cite a source or statute.

It also warns about pages not re-verified within 180 days, uncited sources and ambiguous titles or aliases. A passing result does not establish that the cited source supports the claim.

Configuration is not proof of execution. The latest inspected hosted run, 38984291424, ended in startup_failure before any jobs or check runs were recorded. Its logs were unavailable, so the cause is unknown. We cannot claim hosted checks operate on every change. The repository, Actions details and pull requests are private and require authorized collaborator access; local checks are separate evidence, not proof of hosted operation.

Monitoring for changes#

The watcher is configured for Mondays at 11:17 UTC and manual dispatch. If it executes successfully and captures differences, it is configured to propose a pull request with the data diff. Its scope is Chapters 308A, 308B and 308C plus § 80A.461 only. It does not monitor agency forms or fees, administrative rules, other state statutes, federal law or case law. No complete or timely legislative-monitoring service is promised.

The capture change log records differences detected by normal ingestion, not a verified list of legislative amendments or effective dates. Parser and source-markup changes can affect captures too. For a known extraction repair, npm run wiki:ingest -- --repair-extraction refetches and regenerates the configured targets without appending change-log entries; it preserves existing history. It does not re-review commentary or prove the regenerated extraction complete. Manual comparison with the official sources is still required.

What the checks do not do#

The checks catch structural errors. They cannot establish exhaustive extraction, correct operative/repealed classification, legal accuracy, current agency fees, source support for a sentence or attorney review. The official source and its effective-date information must be checked for the reader's actual question. Human review remains necessary; a named review record, if present, is separate from a matching hash. Content remains unreviewed unless that review is recorded. See Editorial policy.

Manual research findings#

Research findings and limits — October 2026 records the October 2026 legislative-history and case-law work, including the distinction between a cooperative investment-note decision, a fact-specific housing decision and an incidental Chapter 308B citation. It states the statutory-edition, search-access and later-treatment limits rather than claiming comprehensive legal coverage.

Found a mistake?#

Corrections lists completed corrections and explains the currently documented access limitations for reporting problems.