Skip to content
How it works

Evidence

La Paz 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.

Captured45 of 45 parcels
Hash verified45 of 45 parcels
Accepted45 of 45 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

juniper-flat-edu-schedule.csv

Accepted
Basis import
Evidence type
Basis import
SHA-256
44c7b59ed9d1c7da068fad3eaa347231daf84fdc624ee846c2aef588a7f5c5e0
Captured by
Freeboard demonstration fixture
Source
evidence/artifacts/juniper-flat-edu-schedule.csv
Review outcome
Accepted
Reviewed by
Freeboard demonstration fixture
Reviewed at
Jul 29, 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.