Public posture
Reviewer-facing architecture only: receiver posture, authority boundary, event-envelope route and search metadata.
Governance Architecture
The architecture is organised around the seven-layer Governance Spine: identity, evidence, routing, assurance, MRV attachment, export and audit reconstruction.
Governance Spine Whitepaper Governance Spine Diagram Data Flow And Auditability Diagram Assurance Layer FieldTrace Integration Open document library
Public artefact boundary.
This page links only to public artefacts bundled in the v376 search index. Reliance-grade evidence, live programme records and reviewer notes remain in protected workspaces.
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.
-
01
4-Page Brief
Shared institutional orientation
-
02
Review Index
Legal, risk, MRV, procurement and audit routing
-
03
Governance Architecture
Governance Spine, authority boundaries and evidence flow
-
04
Assurance Layer
Verification, integrity lock, admissibility and reliance
-
05
FieldTrace Integration
Field evidence and attribution route into assurance
-
06
Evidence Request
Minimum proof before protected reliance review
-
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.
Protected intake
Operator records, evidence files, review-intake rows and intake decisions remain in protected Hub workspaces.
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.
Verification
Completeness, coherence, authority and attribution checks before reliance.
Integrity Lock
Freeze, hash and snapshot the programme state at institutional closure.
Reliance
Generate the institutional reliance statement without replacing judgement.