Institutional journey

Use one consistent public route across the site before protected entry: understand the infrastructure, walk through the model, circulate the review pack, then enter formal diligence.

Execution environments

Browse the operating environments before entering a protected workspace.

Terra Vita Hub separates public explanation from protected execution. Each environment page explains what the workspace governs, who it is for, and how it fits into the wider governance spine before any sign-in step is required.

1

Read the public overview

Understand the governance purpose and the audience for the environment.

2

Review operating logic

See the workflows, evidence logic, and reporting posture in plain language.

3

Choose the right path

Book a walkthrough, download the brief, or sign in if you already have access.

Public Projects

Governed project delivery environment

For public projects that need structured intake, implementation tracking, compliance, and reporting.

ProjectsApprovalsProtected workspace
Programmes

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 governance spine.

Programme environmentDistinct workflowsProtected workspace
Mining

Mining governance and rehabilitation environment

For concession oversight, rehabilitation evidence, compliance management, and ESG-linked reporting.

MiningRehabilitationProtected workspace
Blue Governance

Marine and coastal governance environment

For mangrove, coastal, and reef restoration programmes that need aligned evidence, MRV, and governance workflows.

Blue governanceModule basedProtected workspace
Programme examples

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 governance spine while preserving their own documents, actions, reporting surfaces, and operating context.

Next step

Use one consistent public-to-protected transition across the site.

Every environment now follows the same logic: public overview first, then protected workspace entry only for authorised users.