Regulators ask questions. The answers already exist.
Scheduled checks, continuous alerts, and ready-made evidence exports. Compliance is not a quarterly event — it runs with the platform.
A single 0–100 score with framework breakdowns and a traffic-light status.
Weekly bias checks and monthly drift detection are wired as scheduled jobs in the repo.
When score drops below threshold, AuraOne creates alerts and attempts delivery to email, Slack, and webhooks (env-gated).
One-click PDF report generation compiles recent runs and active alerts into an exportable artifact.
Example snapshot. Production scores are computed from real runs.
Email, Slack, and webhook deliveries are attempted when configured. Alert records are always created in the database.
Weekly bias checks and monthly drift detection are wired in the repo. Operational rollout depends on your environment and automation runner.
- Run: Bias, drift, retention, and audit checks execute on demand or on schedule.
- Score: Signals aggregate into a 0–100 score with framework rollups.
- Alert: Below-threshold scores create alerts and trigger best-effort notifications.
- Report: PDF exports capture snapshots suitable for audit preparation.
Compliance monitoring surfaces and exports are implemented in the repo. Passing third-party audits and meeting regulatory thresholds are external outcomes.