Public orientation pack
Committee members begin with public, non-sensitive materials: the four-page brief, Review Index, Governance Architecture, Assurance Layer and FieldTrace integration route.
This public page shows how Terra Vita Hub converts a verified, locked and admissible programme state into a committee-ready export posture. It is an orientation route only; protected evidence, reviewer notes, identity-bound logs and live programme records remain outside the public surface.
The public pack orients reviewers. The protected room tests evidence. The Assurance Layer verifies and locks the programme state. Only then can a committee export package be assembled with a clear reliance boundary, evidence map, conditions register and reconstruction path.
Committee members begin with public, non-sensitive materials: the four-page brief, Review Index, Governance Architecture, Assurance Layer and FieldTrace integration route.
Reviewers request only the proof needed to test governance, evidence, attribution, assurance, MRV attachment, export posture and audit reconstruction.
Approved reviewers inspect live programme records, evidence attachments, FieldTrace events, reviewer comments, conditions and decision-support materials under access control.
The Verification Engine, Integrity Lock, Admissibility Layer and Reliance Engine create the bounded assurance object used for institutional circulation.
Committee circulation receives a controlled export package with executive brief, evidence map, gap register, reliance boundary, sharing manifest and ledger references.
The institution decides under its own mandate. Terra Vita does not approve the programme; it provides the governed evidence and assurance route.
Each object is tied to a source layer and a boundary. The package is designed for committee review, DFI/donor circulation, audit reconstruction and controlled institutional handover.
| Object | Source route | Committee use | Boundary |
|---|---|---|---|
| Executive committee brief | Public brief + protected reviewer synthesis | Shared orientation, risk posture, open questions and decision context. | Not a recommendation, rating or approval. |
| Verification report | Verification Engine | Completeness, coherence, authority-boundary and workflow-integrity status. | Status is evidence posture, not committee decision. |
| Locked programme state | Integrity Lock | Snapshot ID, integrity hash, timestamp and freeze boundary for the version under review. | Locks the evidence state; it does not certify outcomes. |
| Admissibility certificate | Admissibility Layer | Structured export package for DFI, ministry, audit, insurer or supervisory review. | Admissibility is reviewability, not regulatory approval. |
| Reliance statement | Reliance Engine | Bounded summary of what can be relied on and under which evidence, role and authority conditions. | Reliance remains conditional on stated scope and institutional judgement. |
| Assured sharing log | Controlled Sharing Enforcement | Records who received what, under which permissions, and whether revocation rules apply. | Sharing is governed; circulation does not broaden authority. |
| Institutional ledger pathway | Institutional Ledger | Audit reconstruction route across verification, locking, admissibility, reliance and export events. | Ledger records events; institutions still interpret significance. |
| Conditions and gaps register | Protected diligence workspace | Open proof gaps, conditions, reviewer questions and unresolved dependencies before release. | Unresolved items remain visible; they are not hidden by pack generation. |
The committee pack should not be released as a substitute for a decision. It is released as a controlled evidence-and-assurance object with a clear reliance version, scope, recipient boundary and reconstruction pathway.
For public reviewers, continue through the Review Index and Assurance Layer. For approved institutional reviewers, request access to protected diligence where live evidence, reviewer actions, FieldTrace events and export manifests can be inspected under the correct authority boundary.
v376 defines the protected workflow that tests the verification dossier, locks the review state, records conditions, prepares controlled sharing and aligns the export register before committee circulation.
The export register records locked evidence, admissible evidence, reliance, export, revocation and reconstruction as one institutional memory pathway.