FieldTrace plugs into the Hub as the field evidence and attribution engine.
FieldTrace captures field events, plots, assets, local actors, context and metadata. The Hub receives signed, hash-bound envelopes and routes them into the Assurance Layer so institutional reviewers can inspect evidence without Terra Vita substituting their authority.
From measurement inputs to institutional reliance.
The route is deliberately non-judgemental: capture, bind, verify, lock, package, rely, share and reconstruct. Decisions remain with capital providers, regulators, DFIs, insurers, ministries and authorised committees.
Governance
Roles · workflows · authority
Evidence
Programme data registry
Attribution
Responsibility · pathways
Controlled Sharing
Access · permissions · logs
Institutional Ledger
Immutable audit trail
Field Capture
Plots · assets · events
Context & Metadata
Time · location · method
Local Attribution
Actors · practices · outcomes
FieldTrace does not approve. It binds evidence into the Hub route.
The operational handoff is a controlled evidence route. The app captures structured events and the Hub receiver verifies the envelope before a protected review-intake row is opened.
| Stage | FieldTrace responsibility | Hub responsibility |
|---|---|---|
| Capture | Collect plot, asset, event, actor, location, time and method metadata. | Accept only scoped, route-valid envelopes for Hub ingestion. |
| Binding | Package field evidence with attribution and manifest references. | Verify signatures, manifest hashes and acknowledgement IDs. |
| Review | Remain an evidence channel, not a judgement surface. | Open protected review intake and route to authorised reviewers. |
| Assurance | Provide field-level source lineage. | Verify, lock, package, rely, share and reconstruct within the institutional boundary. |
Provisioned by request.
FieldTrace remains an approved-operator route. Operators sign in with scoped credentials; access is bound to organisation, programme, site and task context.
Deployable blueprint asset.
Field evidence reaches committee circulation only after Hub verification and assurance closure.
FieldTrace supplies attributable field events. Terra Vita Hub receives, verifies, routes and records them before any committee export package references field-level proof. The committee pack receives a controlled evidence map and reliance boundary, not a raw public data dump.
FieldTrace evidence routes into the protected assurance room before export release.
Signed field events support verification and evidence attribution. They remain protected evidence references inside the assurance room and are only surfaced in committee exports through controlled scope, redaction and register rules.
Full FieldTrace → Hub → Assurance → Export route
FieldTrace remains the field evidence and attribution capture layer. The Hub governs evidence mapping, verification, locking, admissibility, reliance and controlled export.
