Terra Vita Global B.V. · Rotterdam, NL
Terra VitaField Evidence & Attribution
Edition 2026.05 · KvK 98856332
§ 01 — Hero Class · Field App Form · Android, direct app Route · → Terra Vita Hub Status · Provisioned by request
Direct app Provisioned by request

Field evidence,
structured for institutional review.

A direct Android field evidence route. Visits, evidence, tasks and reviewer signals become attributable events, move through a Hub-aligned governance backend, and remain available for MRV, protected review and audit export.

Platform
Android · direct app
Output
Attributable field artefacts
Routes to
Terra Vita Hub
Posture
Audit-grade, non-judgemental
§ 02 / Reviewer route

One visual route from field envelope to export.

Reviewer route diagram showing envelope, backend acknowledgement, protected Hub queue and export, paired with architecture stack: client, service, transport and logic.
Reviewer mental model · event envelope → backend acknowledgement → protected Hub queue → export manifest; client → service → transport → logic.
Canonical chain · envelope → protected Hub queue → export
01 · Event envelope

Capture at source

Field action is bound to named operator, scope, geo, timestamp and integrity seal.

02 · Backend ACK

Sealed record

The backend validates identity and scope, acknowledges the action and writes the governed event.

03 · Protected Hub queue

Reviewer routing

Events move into protected review, MRV projection or follow-up paths without becoming a verdict.

04 · Export

Audit manifest

Submitted visits reconstruct into hash-bound manifests with evidence metadata and chronology intact.

Boundary
Signal, not decision
Record
Append-only chronology
Output
Reviewer-ready manifest

Field artefacts are structured through a Hub-aligned governance backend for protected review, MRV attachment and institutional export. The field app never approves, certifies, rates or finances.

§ 03 / Access

Request operator-scoped access.

For institutions and field counterparts.

Access is by request. The app is not a public download; it is provisioned against named operators and scoped institutional contexts.

Received via secured backend route
§ 04 / Architecture

Four layers inherit the governance spine.

Layer 01 · Client

Android app

Operator-scoped surface for visits, evidence, tasks and completion records.

Layer 02 · Service

Backend API

Authenticates operators, validates scope, seals artefacts and acknowledges commits.

Layer 03 · Transport

Hub event stream

Append-only, attributable chronology consumed by review, MRV and export.

Layer 04 · Logic

Rules engine

Evaluates thresholds and patterns. The engine flags; it does not decide.

§ 05 / Capabilities

Five motions in one reviewer table.

Motion Event class Institutional function Reviewer sees
Visits visit.opened Creates a discrete visit record bound to operator, site, task, geo and time. Reviewer console shows visit ID, operator, site and timestamp.
Evidence capture evidence.captured Attaches photo, file, note or form to the visit with an integrity envelope. Reviewer console shows metadata, storage reference, capture context and seal/hash posture.
Tasks task.completed Closes the loop between institutional assignment and field execution. Reviewer console shows task, expected evidence, completion status and response.
Reviews review.* Turns reviewer actions into attributable assurance events rather than informal commentary. Reviewer console shows confirmations, queries, reviewer identity and queue status.
Escalations escalation.signal Flags configured thresholds or anomalies for institutional attention without issuing a verdict. Reviewer console shows reason, severity, source events and non-decision boundary.

The table replaces a product-tour pattern with a reviewer-grade matrix: what happened, which event was created, why it matters institutionally, and what the reviewer can inspect.

§ 06 / Governance spine

App events mapped to the Hub spine.

Spine field Populated by app events Hub consumer Reviewer inspection point
Identityoperator.login, visit.opened, review.*Operator profiles, access scopeNamed principal, role, organisation, revocation
Evidenceevidence.captured, form.submittedEvidence item registry, protected storageMetadata, form version, capture context, seal/hash
Routingvisit.submitted, review.queuedReviewer queue, admin workloadRoute key, severity, queue status, reviewer assignment
MRVtask.completed, form.submittedMRV projection layerTask-to-evidence closure and structured observations
Assurancereview.in_review, review.accepted, follow_up.requestedReviewer console, event logReviewer trail, notes, status changes and chronology
Exportexport.prepared, export.issuedExport register, audit reconstructionManifest snapshot, SHA-256 hash, issued-to record
Authorityescalation.signal, review.*Authority boundary layerNon-binding until institutional decision
Authority boundary
Terra Vita does not rate, certify, approve, finance or replace institutional judgement.