Operational workflows and governed public publication
What is operational today and how public-safe analytics, exports, and directory surfaces are produced.
Operationally modeled now
Role-based dashboards, coordinator logic, assignment states, closure readiness, third-party reporting, and fatality-pathway modeling are built as product workflows.
Live governed publication
Mwananchi public analytics, Uwazi analytics, public CSV export, and public partner directory surfaces now read from live governed rollups and verified organization records.
How to read the site today
Operational workflows and public publication rules are separated here.
- Dashboard and case workflow surfaces represent the intended operational model of the platform.
- Public analytics and exports are published from live governed rollups rather than direct operational case views.
- Public partner and directory pages are sourced from the verified organization layer rather than static seeded profiles.
- A public metric should still be read in the context of its methodology, update cadence, and suppression rules.
- Pilot readiness still depends on monitoring, retention enforcement, and partner governance staying aligned with the published trust policies.
Current publication boundary
Operational layer
Case intake, coordination, assignment handling, specialist workflows, and closure review continue to live inside protected role-based workspaces.
Public layer
Mwananchi, open-data exports, and public directory surfaces publish governed summaries and verified records instead of case-level operational data.