Skip to content
How it works

Evidence

Mohave County · evidence records supporting the roll

Evidence exists, verifies, and is accepted

Every value the report relies on resolves to a dated artifact whose hash still matches and which the engineer has accepted.

Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.

Every judgment has an author and a reason

Engineer-owned changes and basis values are attributable, so a reviewer can ask a person why a number is what it is.

Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.

One condition earlier in the engagement is unmet, and this stage cannot finish until it is resolved. It is on Roll.

Captured96 of 96 parcels
Hash verified96 of 96 parcels
Accepted96 of 96 parcels

Where this stands

An artifact is captured from the same county navigation that reads the value, hashed on arrival, and verified against that hash on every later read. Acceptance is a separate, accountable act by the engineer. A captured document is not evidence until it verifies and is accepted.

One project file

prospector-point-edu-schedule.csv

Accepted
Basis import
Evidence type
Basis import
SHA-256
348d04a50ffeb2df65c58b79d80a21014bb5be0164a223fb541b46f0adaeb512
Captured by
Freeboard demonstration fixture
Source
evidence/artifacts/prospector-point-edu-schedule.csv
Review outcome
Accepted
Reviewed by
Freeboard demonstration fixture
Reviewed at
Aug 18, 2026, 5:00 PM MST
Review reason
The EDU schedule matches the design report's demand figures.
No evidence needs a decision
Every captured artifact has been verified and accepted. Change the view to inspect the full ledger.