Programme environment
One shared Programme environment, multiple programme instances.
Terra Vita Hub uses one Programme environment for instances that need actions, meetings, controlled documents, evidence-linked reporting, and committee-ready outputs. CARH in Ukraine, Jazira in Somalia, and Mary's Mount in Australia are programme instances inside that shared environment, not separate environment classes.
Shared control architecture
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.
Sovereign programme governance
Programme environments use the same governance spine under sovereign and multi-programme review.
The visual below shows the layered control stack that keeps national authority, programme governance, evidence, assurance and protected diligence distinct while remaining audit-reconstructable.
90-second programme boundary
Programme is the environment; CARH, Jazira, and Mary’s Mount are instances.
Shared environment
Role logic, review discipline, document control, exports, and auditability remain aligned.
Instance context
Each programme keeps its own geography, team, evidence base, safeguards, funding posture, and reporting calendar.
Funding posture
Programme financing can be structured for grants, donors, technical assistance, guarantees, or non-sovereign pathways where needed.
Data sovereignty
Jurisdictional access, hosting, retention, and export-control requirements can be scoped per programme deployment.
Programme instances
The environment stays shared even when operating realities differ.
Ukraine
CARH
A reconstruction-aligned agriculture and resilience programme using actions, meetings, controlled documents, and committee-ready reporting inside the shared Programme environment.
Somalia
Jazira
A coastal regeneration programme where restoration evidence, safeguards, stewardship logic, and non-sovereign funding governance sit inside the same shared Programme environment.
Australia
Mary's Mount
A regional sustainability programme combining local delivery evidence, supplier visibility, and programme-level governance in one auditable operating environment.
Environmental evidence engine
Spatial Intelligence is configured across the established programme portfolio.
Jazira, CARH, Mary’s Mount, Opuntia and Blue Governance now have programme-specific environmental evidence profiles. Each profile defines relevant hazards, attributed subjects, FieldTrace verification requirements and governed downstream uses.
Configured
Programme geography, indicator library, subject types and verification route are defined.
Not yet reliance-grade
Live sources, calibration, reviewer acceptance and controlled release remain separately governed.
Negotiation boundary
Nigeria Digital Farmers Market is not activated. The soybean corridor remains a demonstration case only.
Proof layer
Give procurement and review teams concrete proof objects before access is requested.
Sample decision pack
See a public, redacted pack that shows the committee-ready output standard Terra Vita Hub applies across projects, programmes, mining, and blue-governance environments.
Guided demo
Walk through intake, milestones, evidence, execution, readiness, committee routing, and release in one staged operating flow.
Deployment examples
Review anonymised vignettes that show how the same control architecture is configured for reconstruction, coastal regeneration, and regional delivery.
Governance architecture
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.
Homepage governance alignment
Programme Environment inherits the Terra Vita governance spine.
This module reflects the homepage position: Terra Vita Hub is governance infrastructure, not a dashboard. Evidence intake, reviewer action, MRV attachment, escalation, audit reconstruction, and export posture remain connected inside one governed decision environment.
Evidence intakeReviewer actionMRV attachmentEscalationAudit reconstructionExport posture
Terra Vita OS · v500
Open the programme-centred operating environment.
Ground Evidence, Environmental Evidence, Governance, Funding and Reports now sit behind one programme record. Marketplace remains optional and hidden unless programme authority explicitly activates a formal economic pathway.