Compliance & Policy Management · Documentation
How to Use This Demo
Driving Compliance & Policy Management in the host, the Cloud/OSS inspector, and the operator console — with honest labels.
← Compliance & Policy Management- 1
Signing in + the policy library
The ecosystem is gated — sign in as the universal owner (admin / admin@123) or the read-only viewer; an unauthorized visitor sees only the sign-in card. Open Compliance & Policy Management from the launcher; it mounts in the operator console. Browse the five policy domains — refund, content, data, partner, security — each versioned with an active flag.
- 2
Edit a policy + run a sweep
The owner can edit a policy body (the version bumps and policy.updated is emitted), toggle it active or inactive, run a compliance sweep over a domain to list findings, and resolve a finding. Policy editing and check resolution are owner-only and audited; a viewer reads the library and the findings. Editing the refund policy here changes the rule the refund assistant (#21) is measured against. There is no metered AI stage, so the inspector shows the event and audit flow.