Navigable timeline
Operations, inputs, harvest, sales and settlement are ordered by verifiable milestone.
Each row keeps entity and evidence references when available.
Back home
Traceability
Evidence chain from parcel to report
Trace events, document registry and Merkle anchors connect operations, evidence and campaign states without depending on real on-chain signatures.
Linked documents
Tickets, certificates, invoices and field proofs are shown from the dossier.
The global library avoids duplicating evidence across screens.
Reproducible hashes
Bundles and subgraphs use canonical ordering to compare results.
The goal is to detect drift before publishing.
Public read-only
The public report allows inspection without admin or Studio actions.
The public route preserves the boundary between presentation and operation.
Provenance by design
Every conclusion can be traced to its source data and algorithm
uAgri distinguishes estimates, laboratory measurements, sensors and derivatives. Trust depends on preserving who produced data, when, with which version and resolution.
01Source
Verifiable origin
Each observation keeps acquisition identity and conditions.
- Provider, dataset and version
- Observation and retrieval dates
- Licence, coverage, CRS and resolution
02Process
Reproducible calculation
Derived results describe their transformation and limits.
- Algorithm, parameters and version
- Quality, uncertainty and freshness
- Estimate/lab/sensor distinction
03Evidence
Portable proof
Approved milestones can be packaged without publishing heavy data on-chain.
- Report hash, document reference and epoch
- EO baseline and plan/actual comparison
- v2 candidate kept separate from ERC-7943 v1
Trust chain
From data to dossier
- 01Capture source and licence
- 02Validate geometry and freshness
- 03Calculate and version
- 04Reference in plan, campaign and evidence