Compliance & Policy Management · Documentation
User Journey
The end-to-end path through Compliance & Policy Management, from trigger to outcome.
← Compliance & Policy Management- 1
Policy → check → resolution
The owner authors or versions a policy; policy.updated is emitted with the new version. Running a sweep over a domain produces findings against real activity — a refund approved against a deny recommendation is a violation, a KYC-flagged listing reaching the gate is a violation, a live listing with too few photos is a warning — and emits compliance.checked with the count. The owner resolves findings, and every action is audited.
- 2
Connections across the ecosystem
The active refund policy backs the refund-decision checks (#21); the partner KYC and rate-parity policy backs listing checks (#32, #33); the content standard flags thin listings. Because the sweep reads the shared C6 slice rather than a private copy, the findings reflect the same refunds, listings, and contracts the rest of the ecosystem is working with.