One shared Programme environment, multiple programme instances.
Terra Vita Hub uses a single Programme environment for programme instances that need actions, meetings, controlled documents, evidence-linked reporting, and committee-ready outputs on one governance spine. CARH in Ukraine, Jazira in Somalia, and Mary's Mount in Australia are programme instances running inside that shared environment, not separate environment classes.
Shared governance spine
Identity, review discipline, approvals, auditability, and export standards stay aligned across all programme instances.
Programme-specific operating logic
Each instance can keep its own actions, meetings, documents, safeguards, and reporting context without leaving the shared control architecture.
Public-to-protected boundary
The environment can be explained publicly first, then authorised teams move into protected workspaces only when execution or diligence requires it.
The environment stays shared even when operating realities differ.
CARH
A reconstruction-aligned agriculture and resilience programme using actions, meetings, controlled documents, and committee-ready reporting inside the shared Programme environment.
Jazira
A coastal regeneration programme where restoration evidence, safeguards, stewardship logic, and non-sovereign funding governance sit inside the same shared Programme environment.
Mary's Mount
A regional sustainability programme combining local delivery evidence, supplier visibility, and programme-level governance in one auditable operating environment.
Give procurement and review teams concrete proof objects before access is requested.
See a public, redacted pack that shows the committee-ready output standard Terra Vita Hub applies across projects, programmes, mining, and blue-governance environments.
Walk through intake, milestones, evidence, execution, readiness, committee routing, and release in one staged operating flow.
Review anonymised vignettes that show how the same governance spine is configured for reconstruction, coastal regeneration, and regional delivery.
Go deeper on roles, routing logic, approval control, auditability, and the public-to-protected boundary that underpins the Programme environment.
Public environment first, protected programme workspace second.
Programme teams can stay in the public route until review is complete. Authorised users can then move into the protected Programme workspace only when execution, diligence, or committee preparation requires it.
Need a controlled access review first? Use the institutional review page.