Browse the operating environments before entering a protected workspace.
Terra Vita Hub separates public explanation from protected execution. Environments define how work is governed; sectors define where the work applies; programme instances sit inside the Programme environment.
Read the public overview
Understand the governance purpose and the audience for the environment.
Review operating logic
See the workflows, evidence logic, and reporting posture in plain language.
Choose the right path
Book a walkthrough, download the brief, or sign in if you already have access.
Public Projects
When to use: accountable project delivery with registration, milestones, approvals, and committee-ready outputs.
Scenario: a public-facing agriculture, restoration, or infrastructure project that needs visible governance before protected execution.
Programmes
When to use: multiple programme instances need actions, meetings, controlled documents, and reporting on one shared control architecture.
Scenario: a ministry-led or donor-backed programme such as CARH, Jazira, or Mary’s Mount with distinct records inside one Programme environment.
Mining
When to use: concession obligations, incidents, remediation, and ESG-linked compliance reporting need one governed execution path.
Scenario: a regulator-facing rehabilitation or closure programme that needs obligations, evidence, and reporting kept attributable.
Blue Governance
When to use: coastal and marine restoration modules require aligned evidence, MRV, safeguards, and funding-facing auditability.
Scenario: a coastal regeneration or blue-economy programme with mangroves, reefs, fisheries, aquaculture, safeguards, and donor oversight.
Do not confuse environment, sector, deployment, and programme instance.
The governed operating space: Public Projects, Programmes, Mining, or Blue Governance.
The thematic domain where the work applies: agriculture, climate, coastal and marine, or mining and rehabilitation.
The institutional operating model: sovereign, programme, consortium, or portfolio.
A named programme such as CARH, Jazira, or Mary’s Mount inside the Programme environment.
Choose the environment by governance need, not by website category.
Use for a discrete project record with intake, implementation evidence, approvals, and committee packaging.
Use when programme instances require shared governance but separate documents, actions, meetings, and reporting surfaces.
Use when obligations, incidents, rehabilitation, permits, community agreements, and ESG evidence require controlled review.
Use when coastal, marine, blue carbon, fisheries, reef, and aquaculture evidence must connect to MRV and funding readiness.
Governed project delivery environment
For public projects that need structured intake, implementation tracking, compliance, and reporting. Use when: the institution needs one accountable project record with evidence, approvals, milestones, and export posture.
Shared programme environment
For programme instances such as CARH in Ukraine, Jazira in Somalia, and Mary's Mount in Australia that need actions, meetings, document controls, and committee-ready reporting on the same control architecture. Use when: one shared Programme environment must preserve distinct programme-instance records.
Mining governance and rehabilitation environment
For concession oversight, rehabilitation evidence, compliance management, and ESG-linked reporting. Use when: permits, obligations, incidents, remediation, and regulator-facing outputs must remain traceable.
Marine and coastal governance environment
For mangrove, coastal, reef, fisheries, aquaculture, and blue-carbon programmes that need aligned evidence, MRV, safeguards, and governance workflows. Use when: coastal restoration, livelihoods, and funding readiness must be reviewed together.
Programme instances sit inside the Programme environment rather than creating separate environment classes.
CARH in Ukraine, Jazira in Somalia, and Mary's Mount in Australia are examples of programme instances. They use the same Programme environment and control architecture while preserving their own documents, actions, reporting surfaces, and operating context.