Reviewers receive public explanations of the governance spine, authority boundary, safeguards, institutional suitability, data sovereignty, deployment models, and reviewer accountability before protected access is considered.
v182 external reviewer experience
What Reviewers Can Expect
A public explanation of the reviewer experience before protected access: what is visible, what remains bounded, how questions are handled, and when export packs can circulate.
Expectation principle
External reviewers should know what will be visible, what will remain protected, how questions are handled, and which materials can be exported before they enter a protected diligence room.
What reviewers can expect
Protected access is aligned to a named organisation, review purpose, programme or geography, and access scope. It is not open-ended browsing.
Evidence maps preserve context, source posture, conditions, gaps, reviewer actions, MRV attachment, and export treatment.
Reviewer questions become structured evidence requests with a response owner, expected response path, status, and final treatment.
Export packs disclose readiness, unresolved conditions, exclusions, open questions, access boundaries, and authority limitations.
Review access, external sharing, and data-room handoff are closed or renewed through governed steps rather than informal continuation.
Review boundaries
| Reviewer question | Answer |
|---|---|
| Can reviewers see live programme records? | Only when the review purpose, access scope, and protected environment permissions justify it. |
| Can the Hub approve or reject programme decisions? | No. Terra Vita Hub governs evidence routing, reviewer actions, conditions, escalation, and export posture; human institutional authorities retain final decisions. |
| Can reviewers request additional evidence? | Yes, through a governed request log that preserves ownership, response status, and supporting materials. |
| Can export packs circulate externally? | Only after the release gate confirms completeness, conditions, access boundaries, and unresolved items. |
Expected protected review sequence
Review purpose confirmed
The review is tied to an institution, mandate, geography, programme, or funding route.
Access boundary agreed
Permissions matrix, share register, and data-room access protocol define what can be seen.
Evidence requests logged
Questions are routed into an evidence request log rather than handled privately.
Release gate applied
Export packs are held until readiness, exclusions, and open questions are visible.