Skip to main content

Global Early Warning (Preview)

If a term is unfamiliar, open the Glossary.

This preview introduces the client-facing systemic anomaly detector.

What it does​

  • Accepts cross-sector anomaly signals for your workspace.
  • Produces a normalized anomaly score (0.0..1.0) and confidence band.
  • Emits explicit false-alarm controls:
    • minimum signal count
    • alert threshold
  • Stores privacy-preserving snapshot data (indicator_hash instead of raw indicator).

APIs​

  • POST /api/autonomous/systemic-anomaly/detect
  • GET /api/autonomous/systemic-anomaly/latest
  • GET /api/autonomous/systemic-anomaly/sector-dashboard
  • GET /api/autonomous/systemic-anomaly/scale
  • POST /api/autonomous/systemic-anomaly/workflows/start
  • GET /api/autonomous/systemic-anomaly/workflows/<workflow_id>
  • POST /api/autonomous/systemic-anomaly/workflows/<workflow_id>/retry
  • POST /api/autonomous/systemic-anomaly/workflows/<workflow_id>/approve
  • POST /api/autonomous/systemic-anomaly/workflows/<workflow_id>/rollback
  • GET /api/autonomous/systemic-anomaly/workflows/<workflow_id>/evidencepack
  • GET /api/autonomous/systemic-anomaly/workflows/<workflow_id>/evidencepack/verify
  • GET /api/autonomous/systemic-anomaly/memory
  • GET /api/autonomous/systemic-anomaly/memory/summary
  • GET /api/autonomous/systemic-anomaly/quality-monitor
  • POST /api/autonomous/systemic-anomaly/simulation-harness/run
  • POST /api/autonomous/systemic-anomaly/self-heal/reconcile
  • POST /api/autonomous/systemic-anomaly/performance-profile
  • POST /api/autonomous/systemic-anomaly/security-posture
  • GET /api/autonomous/contracts/systemic-anomaly-detector

UI route: #/sector-dashboards

From #/sector-dashboards you can trigger Start Response Workflow to run a workspace-bound systemic_anomaly_response_workflow with idempotent orchestration. The same page includes a Scale and workflow capacity panel that shows:

  • active workflow quota headroom
  • systemic memory usage by namespace (active/expired totals)

The same page now includes workflow action controls:

  • Refresh Status
  • Approve Workflow (for pending approvals)
  • Retry Workflow (for failed runs)
  • Rollback Workflow (for succeeded runs)
  • Get EvidencePack (Dralvia's exportable evidence report)
  • Verify EvidencePack

It also includes a Systemic Memory Store panel that shows:

  • namespace totals (active/expired entries)
  • latest systemic memory entries
  • workflow snapshot pointers (workflow:<workflow_id> and latest)

And a Model Drift + Quality Monitoring panel that shows:

  • drift alerts by systemic action
  • EMA quality trend per action
  • workflow outcome quality summary
  • latest detector health snapshot

And a Simulation Harness Expansion panel that shows:

  • deterministic replay status
  • scenario count and pass rate
  • latest persisted harness memory pointer
  • replay summary linked to the latest systemic snapshot

And a Self-healing Routines panel that shows:

  • recovered transient systemic workflows
  • workflow scope and reconcile timestamp
  • per-workflow MTTR and retry attempts

And a Performance Profiling panel that shows:

  • workflow success/failure totals and success rate
  • execution and end-to-end latency percentiles (p50/p95)
  • target compliance status and latest persisted profile key

And a Systemic security hardening posture panel that shows:

  • posture state (OK or Needs action)
  • missing required systemic policy actions
  • hardening gate pass/fail summary
  • tracked vulnerability exception count and recommended next actions

Minimal request example​

{
  "signals": [
    { "sector": "finance", "signal_type": "credential_stuffing", "confidence": 0.9, "indicator": "198.51.100.10" },
    { "sector": "energy", "signal_type": "api_abuse", "confidence": 0.86, "indicator": "edge-node-2" },
    { "sector": "healthcare", "signal_type": "token_replay", "confidence": 0.84, "indicator": "token:xyz" }
  ]
}

Response highlights​

  • alert
  • anomaly_score
  • confidence.score
  • confidence.band
  • false_alarm_controls
  • sector_breakdown

Governance and safety​

  • Workspace isolation is enforced on all detector endpoints.
  • Detector, memory, quality, simulation, self-heal, performance, security posture, and response actions are policy-gated (systemic_anomaly.detect, systemic_anomaly.read, systemic_anomaly.memory.read, systemic_anomaly.quality.read, systemic_anomaly.simulation.run, systemic_anomaly.self_heal.reconcile, systemic_anomaly.performance.read, systemic_anomaly.security.read, workflow.start, workflow.approve, workflow.retry, workflow.rollback).
  • Raw indicator material is not persisted in detector snapshots.

Who this is for​

This guide is for workspace owners, admins, and security operators who need clear, repeatable steps without support intervention for day-to-day execution.

Role-based start here​

  • Workspace Owner: Start with Before you start, then complete Step-by-step and Known limits and rate limits.
  • Admin: Focus on Step-by-step, What each button does, and API and automation.
  • Security Analyst: Start at Day-2 operations and Troubleshooting, then use API error quick reference.
  • Integrator/Engineer: Start at API and automation, then validate with Step-by-step and FAQ.

Before you start​

Use this short checklist before making changes:

  1. Confirm you are signed into the correct workspace account.
  2. Confirm your role includes the permissions needed for this page.
  3. Confirm your browser session is fresh (if pages behave unexpectedly, sign out/in once).
  4. Confirm required prerequisites (API keys, agent enrollment, license, upstream integrations) are already in place.

Step-by-step​

Follow this sequence for predictable results:

  1. Open the workspace from the account menu.
  2. Review current status/health/last update indicators before making changes.
  3. Apply one change at a time and save.
  4. Run the available validate/probe/refresh action.
  5. Confirm the expected output appears (status change, new event, successful result).
  6. If behavior is not as expected, use Troubleshooting below before repeating actions.

Day-2 operations​

After initial setup, keep this surface healthy with a simple routine:

  1. Daily: verify data freshness and error banners.
  2. Weekly: review trends, limits, and failed actions.
  3. Monthly: review permissions, keys/tokens, and stale entities.
  4. After any incident: capture evidence and update your internal operating notes.

What each button does​

Button labels can vary by module, but behavior is consistent:

  • Refresh: reloads the latest data from backend APIs without changing configuration.
  • Save: persists workspace-scoped configuration changes.
  • Run/Probe/Validate: executes a non-destructive health or verification action.
  • Download: fetches workspace-scoped artifact(s) (for example bundle, checksum, signature, or report).
  • Verify: checks integrity/consistency and returns pass/fail details.
  • Enable/Disable: toggles module behavior for your workspace; audit evidence should be recorded.

If a button appears disabled, check role permissions, required fields, and plan/feature entitlement first.

Self-check playbook​

Use this 5-step isolation flow before escalating:

  1. Configuration: confirm required inputs are present and formatted correctly.
  2. Permission: confirm your role can perform the action (401/403 usually indicates authz/authn mismatch).
  3. License/feature: confirm the feature is enabled for your plan and module toggles.
  4. Quota/rate limit: check for 429 responses and cooldown windows.
  5. Service health: if you see 5xx, retry once after 30-60 seconds and capture exact error text.

If still failing, escalate with workspace ID, UTC timestamp, route, action, payload shape (no secrets), and screenshot/error response.

Troubleshooting​

Use this quick triage order to reduce time-to-fix:

  1. Auth/session: refresh token by signing out/in.
  2. Workspace context: confirm you are in the correct workspace.
  3. Inputs/config: verify required fields and formats.
  4. Quota/license: confirm limits and feature entitlement.
  5. Service health: retry after short delay if backend is transiently degraded.

For escalation, include workspace ID, timestamp (UTC), route name, action attempted, and full error message.

API and automation​

Everything in this page should remain workspace-scoped. If your team prefers automation, use the corresponding API endpoints with the same guardrails as the UI:

  • Use authenticated requests bound to your workspace context.
  • Use idempotency/retry controls where available.
  • Validate outcomes in the UI after automated runs.

If your endpoint mapping is not obvious, start from Help Center and follow the linked API docs.

Next best actions​

After finishing this page, continue with related workflows so your workspace setup stays end-to-end complete:

FAQ​

Q: I clicked save but nothing changed. A: Refresh once, confirm permissions, and verify required fields.

Q: Why do I see missing API key/unauthorized errors? A: Confirm your workspace API key/session is valid and mapped to the correct workspace scope.

Q: Can non-admin users use this page? A: Usually read-only access is possible; write actions require admin or equivalent roles.

Next steps​

After finishing this guide:

  1. Validate the result in the related dashboard/workspace.
  2. Export or capture evidence if this affects compliance/incident operations.
  3. Share the same runbook internally so other operators follow identical steps.
  4. Return to Help Center for adjacent workflows.

API error quick reference​

Use this matrix when a UI action fails with an HTTP/API error.

ErrorMeaningWhat to do now
401 UnauthorizedSession token is missing/expired or request is not authenticated.Sign out/in, refresh once, then retry. Confirm your session is active in the correct workspace.
403 ForbiddenYou are authenticated but your role is not allowed to perform this action.Confirm your role includes the required permission for this button/action. Ask an admin to grant access.
404 Not FoundThe route/resource does not exist in current workspace context (or feature not enabled).Confirm URL/route, workspace context, and feature availability. Refresh and retry; if persistent, capture timestamp and route and contact support.
429 Too Many RequestsRate limit/quota window was exceeded.Wait for cooldown/reset window, retry once, then reduce burst traffic/backoff if automated.
500 Internal Server ErrorBackend failed unexpectedly while processing the request.Retry after 30-60 seconds. If still failing, escalate with workspace ID, UTC time, route, action, and full error text.

Known limits and rate limits​

These limits can vary by plan and feature, but behavior is consistent:

  • Burst traffic can trigger 429 Too Many Requests.
  • Workspace quotas apply per feature/module and reset on configured windows.
  • Repeated retries without backoff can extend recovery time during saturation.

Recommended operator behavior:

  1. Retry once after cooldown for 429 responses.
  2. Use exponential backoff in automation.
  3. Monitor usage/quota dashboards for sustained high utilization.
  4. Request quota review when normal workload regularly approaches limits.