Docs

Appearance

Results & Remediation ​

Results capture the outcome of test execution over time. Remediation is how you turn failures into concrete improvements in Controls, systems, and Evidence.

What this is ​

Testing is only valuable if it produces action:

  • Results tell you what happened.
  • Remediation tells you what to do next.

Where in Modulos ​

  • Project → Runtime Inspection → select a test → Results to see the run history and details
  • Project → Runtime Inspection → select a test to run the test manually and manage links to Controls
  • User → Notifications to see alerts generated from failed or error outcomes
Test detail page showing the Results tab, historical outcomes, and linked Controls.
A test detail page combines results, ownership, and links to Controls so failures can be routed and audited. UI shown in light mode.
  1. 1
    Results tab
    Review historical outcomes for the test.
  2. 2
    Test Now
    Run the test manually to confirm a change or investigate drift.
  3. 3
    Result history
    Each run is recorded with passed, failed, or error status.
  4. 4
    Assignee and status
    Route follow-up to an owner and enable or disable the test.
  5. 5
    Linked Controls
    Associate tests to Controls so outcomes become audit-relevant.

Result statuses ​

Each test run produces a result status:

  • Passed: the condition was met
  • Failed: the condition was not met
  • Error: the test could not be evaluated because the data path was not healthy

Typical causes of error include:

  • the Source connection is failing
  • the metric name is missing or not found in the Source
  • no recent datapoint exists in the lookback window

Who gets notified ​

Failed and error results are routed to the right owners:

  • the test assignee
  • users associated with linked Controls

Passed results are recorded for traceability but do not generally require attention.

What remediation looks like in practice ​

Modulos does not treat remediation as a separate silo. A practical loop looks like this:

  1. Triage
    • If the status is error, fix the integration or the metric first.
    • If the status is failed, treat it as drift in the system or Control implementation.
  2. Fix the root cause
    • change the system, process, or configuration that the metric reflects
  3. Update governance artifacts
    • update the Control narrative if needed
    • attach Evidence that proves what changed and when
  4. Re-verify
    • run the test manually, or monitor scheduled runs until the signal stabilizes

If a test is linked to a Control, use failures as a prompt to revisit whether the Control should still be considered executed and effective.

Tests & Schedules

How tests are defined, scheduled, and linked to Controls

Evidence

How to attach Evidence and keep it reviewable and auditable

Reviews, Statuses, and Readiness

How execution and review workflows work across governance objects

Operating Model

The end-to-end Runtime Inspection model in Modulos