Response standard
Responses should remain factual, boundary-aware, and evidence-linked. Where a question cannot be answered from current artifacts, it becomes a condition with owner assignment.
v179 reviewer Q&A
Reviewer Questions & Responses
A protected question-and-response surface for ministries, DFIs, climate funds, auditors, and fiduciary teams reviewing the Hub before or during a protected walkthrough.
Use
This page gives reviewers controlled answers to common due-diligence questions. It is not legal, financial, or MRV methodology advice and does not alter decision authority.
Core reviewer questions
| Question | Response | Where to verify |
|---|---|---|
| Does Terra Vita Hub make decisions? | No. The Hub structures evidence, review, conditions, escalation, and export posture. Human authorities retain final decisions. | Institutional Review Summary |
| Does it replace MRV methodologies? | No. MRV methodologies and national authority remain external. The Hub preserves indicator lineage, evidence attachment, verification logic, and reporting outputs. | MRV attachment note |
| Who owns the data? | Institutions retain ownership and control. Hosting, residency, retention, export pathways, and access governance are configured by deployment requirements. | Sovereignty note |
| How are reviewer actions controlled? | Reviewer actions are attributable, bounded, timestamped, non-destructive, and linked to evidence, conditions, escalation, and export posture. | Resistance routing |
| What happens when a reviewer delays, blocks, or contradicts evidence? | Resistance becomes a routable governance object: stalled review, interpretation conflict, unsupported variance, or authorization drift. | Resistance routing |
| How does the public layer differ from the protected layer? | Public pages explain the model, limits, safeguards, and proof objects. Protected environments hold live evidence, personal data, programme records, reviewer actions, and committee packs. | Transparency & Integrity |
| What do donors and DFIs receive? | They receive a structured review path, artifact index, committee pack, evidence map, Q&A, and submission checklist, subject to authorized access. | Data Room Readiness Index |
| Are database changes executed from these pages? | No. Database readiness visibility is documentation only. SQL, schema, RLS, policy, and execution logic remain unchanged by this surface. | Database readiness note |
| When should a protected walkthrough be granted? | Only when there is a named institutional purpose, programme context, geography, funding route, procurement question, or governance review requirement. | Protected walkthrough request |
Committee-ready treatment
Questions that affect authority, safeguards, sovereignty, MRV attachment, reviewer accountability, or submission readiness should be included in committee notes rather than handled informally.