Governance spine
Evidence, reviewer identity, escalation logic, MRV signals, funding posture, and export outputs remain connected through one governed chain.
Protected workspace → Governance Architecture
Risk & assurance framework for institutional reviewers.
This protected layer holds the deeper governance, fiduciary, safeguards, sovereignty, MRV, and export-posture materials that ministries, DFIs, climate funds, and auditors review after understanding the governance spine.
Reviewer route
Transparency & Integrity → Institutional Brief → Governance Architecture → walkthrough only when there is a named institutional purpose.
Authority boundary
The Hub structures evidence and governance posture. It does not replace statutory, fiduciary, procurement, financial, or programme authority.
Escalation Logic
Escalation remains human, attributable, and inspectable.
Evidence intake
Records capture source context, location, intervention type, evidence requirements, and risk flags.
Reviewer action
Conditions, exceptions, gaps, and reviewer rationale are logged rather than handled informally.
Committee posture
Records move into committee preparation, conditional release, blocked posture, or export readiness through controlled states.
Audit and export
Decision posture remains traceable to the record, reviewer identity, MRV attachment, and evidence chain.
Risk & Assurance Framework
Risk Assurance Note (DFI-Grade)
Terra Vita Hub provides a governed environment for institutional evidence, review, escalation, and approval. It does not automate statutory, financial, or programme decisions. All authority remains with ministries, DFIs, and designated committees.
- Attributable reviewer identity
- Logged conditions, overrides, and escalation routes
- Evidence lineage from field to committee
- Exportable decision posture for audit and donor reporting
- Separation of public transparency from protected evidence workspaces
Overall assurance posture: High. Residual risks relate to institutional onboarding, reviewer discipline, and clarity of role mapping. These are mitigated through structured onboarding, governance-boundary briefings, and committee-level endorsement of the evidence spine.
DFI-facing Institutional Readiness Memo
Institutional readiness is documented for donor due diligence.
This protected memo positions Terra Vita Hub as governance and MRV infrastructure for DFIs, climate funds, MDBs, and sovereign oversight bodies. It explains the authority boundary, fiduciary safeguards, MRV attachment logic, sovereignty controls, continuity posture, and evidence objects reviewers should test.
- Confirms that the Hub does not automate statutory, fiduciary, procurement, or programme decisions.
- Explains how evidence, reviewer identity, escalation, MRV signals, funding posture, and exports stay connected.
- Identifies the deployment conditions DFIs will expect before scale-up: sovereignty memo, role mapping, access controls, continuity, and production hardening.
Donor Review Simulation
What a DFI reviewer will likely say in committee.
This internal reviewer-preparation artifact anticipates the questions DFIs and climate funds will raise in committee: risk assurance, data sovereignty, MRV attachment, safeguards, audit trail, and donor-submission readiness. It should remain inside the protected governance workspace and be used to prepare walkthroughs, not as homepage copy.
- Maps likely committee questions to the institutional answer Terra Vita Hub should provide.
- Identifies the protected evidence objects that should be opened during a DFI walkthrough.
- Clarifies likely approval conditions: role discipline, sovereignty configuration, RLS/access separation, continuity arrangements, and evidence-quality procedures.
Institutional Safeguards & Compliance Framework
Safeguards sit between escalation logic and MRV/reporting.
Terra Vita Hub embeds safeguards and compliance requirements directly into the governance spine. The platform does not replace legal, statutory, or fiduciary authority. Instead, it ensures that all decisions are grounded in verifiable evidence and attributable reviewer actions.
- Separation of public transparency from protected evidence workspaces
- Reviewer identity, role mapping, and least-privilege access
- Logged conditions, overrides, and escalation pathways
- Integration of safeguards records, grievance logs, and consultation evidence
- MRV attachment with indicator lineage and audit-ready reporting
- Data-sovereignty configuration aligned with national and donor requirements
Compliance posture is strengthened through persistent evidence storage, exportable committee packs, and governance-boundary enforcement.
MRV & Reporting
MRV remains an attached, governed layer.
National MRV methodologies, baselines, factors, and verification rules remain the methodological authority. The Hub binds those signals to programme records, evidence, approval conditions, reporting posture, and funding alignment without replacing national systems.
v175 Sovereignty, MRV & Donor Readiness
Protected donor-readiness documents now sit behind the governance workspace.
These additions document hosting-region options, data residency constraints, access-policy governance, retention posture, institutional ownership boundaries, MRV indicator lineage, and donor-pack indexing. They are documentation/export-readiness surfaces only and do not change auth, schema, RLS, SQL, functions, role-save logic, or protected business logic.
v176 Donor Pack QA, Traceability & Resistance Routing
Reviewer accountability now treats resistance as attributable governance data.
The protected workspace now includes a donor-pack QA checklist, evidence traceability matrix, submission status overview, and resistance-routing note. Resistance is documented as visible, attributed, timestamped, routable, escalated, resolved, and externally reviewable in the same way evidence is made visible.
v177 Protected Surface Unification & Live QA Closeout
Protected module routes now have a reviewer-facing QA closeout and route registry.
The protected workspace now includes a route registry and QA closeout note for styling consistency, logout visibility, donor-pack links, unified CTA language, and preservation of restricted logic. This is a presentation and documentation layer only.
v178 Donor Submission Finalisation & Committee Review Pack
Committee-facing donor submission surfaces now have a final cover, review index, DFI walkthrough, and final checklist.
This documentation/export-readiness layer brings the Institutional Review Summary sequence into the protected donor pack without changing auth, Supabase, SQL, schema, RLS, admin APIs, Netlify Functions, sign-in routing, role-save logic, or protected business logic.
Existing Governance Documents
Reference documents
This workspace also preserves existing governance material already used in the Hub.
Module assurance card
Protected Governance Architecture inherits the Terra Vita governance spine.
Protected Governance Architecture assurance: Sovereignty, MRV attachment, donor readiness, resistance routing, traceability, and route governance are visible to authorised reviewers inside the governed chain.
This workspace does not replace human authority. It makes readiness, exceptions, conditions, reviewer posture, and export posture visible so authorised users can make defensible decisions.