⌕Jump to template, rule, fund…⌘K

Help ◔ L

Runs · Run #14237 · Debug section

Why was Risk warning hidden?

Section 06 of Q4 Aberdeen Global Equity factsheet, generated 16 May 2026 09:24.

⚠ Hidden in this run

Document preview

Aberdeen Global Equity Fund

Q4 factsheet · Institutional share class

01CoverShown

02Fund overviewShown

03PerformanceShown

04HoldingsShown

05Performance commentaryShown

08DisclaimersShown

Run#14237

Generated16 May 09:24

Data snapshot2026-Q1 (16 May)

Triggered byScheduled run

Rule Show risk warning for high-vol funds Open in library →

Then Show Risk warning

Volatility = High Actual: High · matched

✓

AND both conditions must pass for the section to show

Doc type ≠ Institutional Actual: Institutional · condition not met

✗

Outcome Conditions did not all pass → section was hidden The rule requires both Volatility = High AND Doc type ≠ Institutional. The fund's volatility matched, but this is an institutional share class, so the section was not shown.

Why this screen looks the way it does

Numbered points map to the blue chips on the screen above.

Hidden sections stay in the preview

Striped pattern marks them as hidden but they keep their place. The user can still scan all sections and click into the ones that didn't appear. Deleting them from the list would hide the problem.

Run metadata is forensic

Run ID, timestamp, data snapshot version. This is what the audit trail looks like in a regulated environment. "What did the report look like at the time it was generated, with what data?"

Actual values alongside the rule

The rule alone ("Doc type ≠ Institutional") is abstract. Pairing it with "Actual: Institutional" turns it into a concrete story. Operators don't reason in abstractions.

One pass, one fail, then the connector

The AND/OR connector explains how individual condition results combine into the section outcome. Makes the logic concrete: "Volatility passed but Doc type did not, so the AND failed."

Outcome explained in plain English

Same echo pattern from the rule builder (screen 02) and the stress test (screen 04). The system reads back what happened. Closes the loop between intent and result.

Edit is primary, override is quieter

The user is here to diagnose, and the diagnosis usually leads to fixing the rule, not patching this run. Override is an emergency action so it sits separately in ghost treatment to reduce the chance of accidental use.