Environment overview
Public Projects is the governed environment for public project delivery.
This environment is for project registration, implementation tracking, accountable approvals, evidence-linked reporting, and institutional review. It uses the shared control architecture while staying distinct from programme, mining, and blue-governance workspaces.
What it governs
Project intake, approvals, implementation milestones, compliance evidence, reporting, and committee-ready outputs.
Who it is for
Public institutions, delivery units, funders, and oversight teams that need a controlled public-project workflow.
Structured registration
Projects enter through controlled intake with accountable evidence requirements.
Governed implementation
Tasks, approvals, and execution milestones remain visible and attributable.
Institutional reporting
Outputs stay committee-ready, exportable, and audit-legible for public review and funder oversight.
90-second environment fit
Use Public Projects when the unit of governance is a discrete project.
Definition
A Public Project is a governed project record with intake, milestones, evidence, approvals, reporting, and export posture.
Use when
The work needs accountable project delivery rather than a multi-instance programme environment.
Commercial scope
Scope usually follows setup effort, project volume, evidence requirements, reporting needs, and support depth.
Data residency and control
Access, retention, export, and jurisdictional requirements can be defined before protected workspace entry.
Archetypal project flow
Show the Public Projects environment through one concrete governed sequence.
An institutional reviewer should be able to see how the environment works without signing in first. This archetype mirrors the operating logic used in the guided demo.
1. Register project
Create the project record, assign owners, and define required evidence and milestones.
2. Capture evidence
Upload supporting documents, field records, safeguards material, and implementation proof against the live record.
3. Review and route
Move the project through accountable checks, approvals, and exception handling before the next decision gate.
4. Track delivery
Keep milestones, bottlenecks, and responsible parties visible to programme owners and funders.
5. Export and report
Generate committee-ready outputs, audit trails, and funder-legible reporting from the same governed records.
Proof layer
Bring Public Projects up to the same proof standard as the Programme environment.
Guided demo
Use the staged operating flow to see how intake, evidence, review, and reporting behave in practice.
Sample decision pack
Review a redacted export object that shows the output standard expected once a project reaches committee or lender review.
Governance diagrams
See the system architecture and onboarding / eligibility diagrams that explain how the public route connects to protected execution.
Deployment fit
Compare how a project-led environment differs from programme, mining, and portfolio-oriented deployment choices.
Enter the workspace only after the public overview.
The protected Public Projects workspace is available to authorised users. If you are evaluating the environment, book a walkthrough or download the brief first. If you already have access, sign in to continue.
Need formal access review? Use the institutional review page.
Homepage governance alignment
Public Projects 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