Purpose and audience
Illustrate oversight while the separate Trust Center governs real scoped authority.
Intended users: Verified governance, security, finance and executive reviewers. Intended benefit: Make organizational accountability a prerequisite, not a hidden assumption.
Access and prerequisites
The existing /governance route is a public fictional demonstration, not staff authority. Real access would require: Server-side Trust permission, scope, MFA, independent approvals and non-browser-writable launch review.
What you can explore
Positive privileged lifecycle is unverified. Public oversight figures are illustrative, not measured Covenant House outcomes.
- Illustrative reporting
- Separate protected Trust Center
- Permission/MFA/launch-review design
- Proposed access review and audit lifecycle
Explore the prototype safely
Open the Governance demonstration using the module link. Read its notice before interacting. Inspect the relevant example view; use fictional, non-sensitive input only. Local changes demonstrate an idea, not an operational action.
Use the Connected Ecosystem map to inspect the Governance connections. Continue to a role tour to understand proposed approvals. Do not try to bypass unavailable registration, assignments or administrative controls.
Example scenario
In fictional Alex’s support scenario, Governance contributes only its permitted task. The input would be: Authorized, validated operational evidence; none is loaded into this public reference. The expected proposed output would be: Proposed audit evidence, access decisions and privacy-safe aggregates.
Inputs, outputs and connections
Receives: Authorized, validated operational evidence; none is loaded into this public reference.
Produces: Proposed audit evidence, access decisions and privacy-safe aggregates.
Related modules: Central, Sites, Clinical, Financial, Giving, Connect.
Privacy and approvals
Public module demos confer no authority. Private capabilities audit data stays outside public imports.
Server-side Trust permission, scope, MFA, independent approvals and non-browser-writable launch review.
Troubleshooting and limitations
Positive privileged lifecycle is unverified. Public oversight figures are illustrative, not measured Covenant House outcomes.
If a view is unavailable, do not submit personal details elsewhere to work around it. A simulated approval cannot activate a service or grant access. The help center cannot resolve an emergency or connect a live responder.
Status, evidence and operational dependencies
Current classification: Blocked. Source review: 18 October 2026. src/routes/governance.tsx; src/lib/trust.functions.ts; docs/covcare-v56-production-development-readiness.md
Before operation: validate server-side trust permission, scope, mfa, independent approvals and non-browser-writable launch review. and document recovery, audit, retention, user impact and separately approved tests. Source presence does not establish published-runtime or provider success.