Institution-specific setup for programmes, public projects, blue governance, mining, or portfolio oversight.
Operating scope and boundaries
Commercial Scope
The commercial scope defines what Terra Vita Hub configures, supports, and explicitly does not replace.
Included in scope
Reviewer roles, permission posture, access pathways, and governance accountability.
Document intake, evidence linking, reviewer action capture, conditions, exceptions, and export readiness.
Attachment of methodologies, indicators, evidence objects, verification logic, and reporting outputs.
Committee-ready packs, data-room indexes, export posture, and donor-readiness materials.
Configuration, alignment, walkthrough support, and deployment-readiness review.
Explicit exclusions
- statutory authority
- lending decisions
- procurement decisions
- legal approvals
- MRV methodology approval
- automated approvals or release decisions
- rating-engine, investment-advisory, or portfolio-management services
Regulatory and authority boundary
Terra Vita Hub is not a regulated financial institution, rating engine, investment advisor, portfolio-management tool, verifier, statutory authority, procurement authority, or lender. Institutions retain responsibility for programme design, legal compliance, procurement, approved methodologies, and final decisions. Terra Vita Hub is responsible for the governed operation of the evidence and reviewer environment as contracted.
Contractual responsibility and liability allocation are governed by the applicable agreement and institutional mandate.
Procurement-ready summary
Configured deployment of governed workspaces, evidence routes, reviewer controls, programme contexts, and export surfaces.
Implementation, onboarding, configuration, review-path support, and deployment-readiness guidance.
Hosting region, data-residency posture, retention, access-policy governance, and export control can be configured by deployment.
MRV, documents, satellite/GIS, funding, evidence, and reporting layers attach to the governed record instead of creating parallel systems.
Reviewer attribution, audit reconstruction, evidence lineage, exception routing, and export posture remain inspectable.
Operational guarantees, integrations, and safeguards
Operational commitments are deployment-specific and should be documented in the applicable SLA, security pack, integration schedule, and protected walkthrough. The public review route now separates what the Hub can describe publicly from the evidence procurement, security, IT, risk, and safeguard teams should test.
Target uptime band, maintenance windows, monitoring and alerting boundaries, incident-response route, redundancy posture, RPO/RTO expectations, backup/restore evidence, change-management controls, and regional failover design where required.
APIs, secure file drops, satellite/remote-sensing ingestion, registry connectors, export/reporting formats, machine-readable committee-pack outputs, and SAML/OIDC identity federation where configured.
Safeguard framework mapping, ESG/ESS/IFC alignment where applicable, incident/grievance pathways, data lifecycle and residency commitments, and credit/operational/environmental/fiduciary risk interfaces through governed exports and evidence registers.
Reviewer takeaway
Terra Vita Hub is governed infrastructure, not a financial, legal, procurement, or statutory decision-maker.