Skip to content

Governance Architecture

The architecture is organised around the seven-layer Governance Spine: identity, evidence, routing, assurance, MRV attachment, export and audit reconstruction.

Governance Spine Diagram

Public artefact boundary.

This page links only to public artefacts bundled in the v442 search index. Reliance-grade evidence, live programme records and reviewer notes remain in protected workspaces.

Stewardship Benchmarking (Governance Spine Placement)

Institutional Surface — Governance Spine Layer. Stewardship Benchmarking is a governed Hub module that reconstructs capital behaviour on land using attributable evidence from FieldTrace, land records, ownership records and transaction histories. It enables institutions to review land-use, capital and ecological behaviour through a canonical reviewer route, without issuing ratings, certifications or investment advice. All outputs are reviewer-grade, evidence-bound and aligned with the governance spine. This module provides the transparency required for land-use oversight, generational transition, and capital-behaviour accountability.

01

Hub placement

Governance Spine → Institutional Review Surfaces → Stewardship Benchmarking.

02

Reviewer route

Evidence Intake → Attribution → Behaviour Reconstruction → Reviewer Assessment → Benchmark Output.

03

Authority boundary

No regulatory substitution, ratings, certification, ESG scoring or investment advice.

Architecture now sits before assurance and evidence request.

Reviewers can move from orientation into the Governance Spine, then into the Assurance Layer and FieldTrace evidence route before requesting protected diligence.

  1. 01

    4-Page Brief

    Shared institutional orientation

  2. 02

    Review Index

    Legal, risk, MRV, procurement and audit routing

  3. 03

    Governance Architecture

    Governance Spine, authority boundaries and evidence flow

  4. 04

    Assurance Layer

    Verification, integrity lock, admissibility and reliance

  5. 05

    FieldTrace Integration

    Field evidence and attribution route into assurance

  6. 06

    Evidence Request

    Minimum proof before protected reliance review

  7. 07

    Protected Diligence

    Purpose-bound evidence access and reviewer action

Public orientationArchitecture + assurance reviewProtected diligence

FieldTrace → Hub Integration — signed field evidence envelopes into assurance.

FieldTrace envelopes enter Terra Vita Hub through a signed, hash-bound receiver. The receiver verifies the manifest and HMAC signature, records the ingest event, opens a protected review-intake row, and returns a deterministic Hub acknowledgement ID.

01

Public posture

Reviewer-facing architecture only: receiver posture, authority boundary, event-envelope route and search metadata.

02

Protected intake

Operator records, evidence files, review-intake rows and intake decisions remain in protected Hub workspaces.

03

Authority retained

FieldTrace receiver intake is non-binding until an institution, committee or authorised reviewer acts under its own authority.

FieldTrace outboxHub receiverProtected review intake

Assurance Layer — verification, locking, admissibility and reliance.

The Assurance Layer binds Governance, Evidence and Attribution into an institutionally admissible object. Controlled sharing and the Institutional Ledger preserve the reliance boundary after export.

01

Verification

Completeness, coherence, authority and attribution checks before reliance.

02

Integrity Lock

Freeze, hash and snapshot the programme state at institutional closure.

03

Reliance

Generate the institutional reliance statement without replacing judgement.