Evidence & updates

Evidence and source status

Inspect the dated source record behind each encoded rule, replay the structured cases, and see which records would need review after a source changes.

Source status is not approval. A date on file means source evidence was recorded. It does not mean a jurisdiction, counsel, or named human reviewer accepted the encoded interpretation.

Current prototype state

Rule-source status

The browser recomputes these figures from the same generated data bundle used by the project guide and applies the reviewed source-watch snapshot committed with that bundle.

Within review window

of rule records have dated source evidence inside the 180-day review window.

Structured replay

Loading structured scenarios…

Registry reach

Loading jurisdiction registry…

Committed source-state receipt

Snapshot used by this build

Loading the committed source-state receipt…

Receipt status “reviewed” means a repository maintainer deliberately adopted this completed-run receipt for publication. It does not mean that a named human, counsel, or a jurisdiction approved the legal interpretation or product guidance.

Open the exact workflow receipt · Inspect the machine-readable snapshot

Dependency rehearsal

What happens when § 66321 changes?

Temporarily layer a change to one source ID over the committed snapshot. Every linked rule turns stale; unrelated records remain unchanged. The rehearsal itself is not written back to the committed receipt or review queue.

Rule	Scope	Status

Flagship evidence gate

Prepared, not run

The review and research package is versioned so future evidence can be tied to one journey, source snapshot, and commit. Preparing the package is not evidence that any external work occurred.

No external outcome is claimed. No qualified content review, participant session, manual accessibility signoff, Spanish semantic review, complete maintenance rehearsal, or qualifying partner commitment is recorded.

25-item content review

Not run

Two independent reviewer slots are prepared. Every row-level mapping and action disposition remains pending.

Same-version sessions

Not run

No applicant or practitioner session, score, task time, quotation, or usability outcome is recorded.

Partner gate

Pending

No written next step with an owner and date is on file. Interest or praise would not satisfy this gate.

Manual access and language: Not run. Keyboard, screen-reader, zoom, mobile, print/PDF accessibility, forced-colors, and Spanish semantic checks still require signed, version-bound evidence.
Maintenance rehearsal: Not run. The browser simulation above is not the timed detection-to-republication rehearsal and does not establish an acceptable maintenance burden.

Inspect the machine-readable gate ledger, 25-row review matrix, and manual evidence matrix. Inspect the six-session scorecard ledger and source-change rehearsal ledger. Read the execution and claim protocol.

Recorded source evidence

Source monitoring

Selected official state and local sources have a recorded content hash and are re-fetched by the repository workflow. A reviewed snapshot of the last run is bundled above and overlays its exact changed-source dependencies on applicant outputs. Unwatchable sources remain visible as reference-only records. Automatic adoption, review assignment, and new-law discovery remain planned.

Source	Monitoring	Recorded	SHA-256

How to read this page

Four boundaries stay visible.

Trust comes from showing what each artifact proves and what it does not prove.

Matching: Rules choose the records. Deterministic criteria use the applicant’s structured answers. Explanation copy cannot create or change a match.
Language: Readable copy stays separate. English and Spanish explanations are versioned AI-assisted prototype drafts. None is represented as human-reviewed or jurisdiction-approved.
Currency: A changed source affects its dependents. Stable source IDs connect rules to evidence. A reviewed watch snapshot is committed with the public bundle; the change rehearsal remains a separate temporary overlay.
Coverage: Statewide screening is not local encoding. The statewide candidate-rule set can run for the registry. That does not mean local codes, forms, parcel facts, or exceptions are comprehensively represented.