Evidence-map discipline
Every committee claim should be backed by a linked page, artifact, or protected control surface. Unsupported claims are held as conditions, not hidden in narrative copy.
v179 committee evidence map
Committee Submission Evidence Map
A protected evidence map that connects likely committee questions to the artifacts, governance controls, and export-readiness surfaces that answer them.
Purpose
This map prevents the committee pack from becoming a loose collection of files. Each review question is tied to an evidence source, a protected location, and a submission treatment.
Committee evidence map
| Committee question | Evidence source | Submission treatment |
|---|---|---|
| What authority does Terra Vita Hub have? | Institutional Review Summary and Governance Architecture. | Clarifies that the Hub structures governance but does not replace statutory, legal, financial, or MRV authority. |
| Why would an institution use it? | Why Institutions Use Terra Vita Hub. | Frames the value proposition in governance, fiduciary, MRV, and audit language. |
| Who is the platform for? | Who Terra Vita Hub Is For. | Lets ministries, DFIs, climate funds, auditors, and implementers self-identify. |
| What governance failure modes does it solve? | What Terra Vita Hub Solves. | Names fragmentation, informal approval chains, undocumented review, MRV drift, and audit reconstruction gaps. |
| How are safeguards and risk covered? | Donor Readiness Artifact Index. | Routes reviewers to risk assurance, safeguards, readiness memo, simulation, and posture documents. |
| How is MRV attached without replacement? | MRV Attachment & Indicator Lineage. | Shows methodology, indicator, evidence, verification, and output lineage while preserving national authority. |
| How is data sovereignty handled? | Data Sovereignty & Hosting Configuration. | Documents hosting, residency, export controls, access policy, retention, and ownership posture. |
| How are reviewers held accountable? | Governance Resistance Spine. | Shows attributable reviewer actions, resistance as routed case types, bounded discretion, and escalation controls. |
| Is the platform technically submission-ready? | Database Readiness Note and Protected Surface QA Closeout. | Separates readiness visibility from SQL execution and confirms protected surfaces inherit the governance spine. |
| Can this be circulated as a donor pack? | Final Submission Checklist. | Defines the final submission gate and owner treatment for unresolved conditions. |
Externalization rule
Material should only move into donor or committee circulation when export posture, unresolved risks, and owner assignments are clear.