Identify false assurance.
Features that look protective but are not. Step 5 does not find another type of risk. It finds mechanisms that make existing risk harder to see — reducing the investor's scrutiny rather than their exposure.
- How false assurance operates — the gap between what a feature appears to do and what it actually does.
- Four mechanisms: user-configured risk settings, mismatched capital bases, risk of ruin underreporting, verified vs. audited.
- The inversion — these mechanisms reduce scrutiny, not risk.
- How the Institute applies Step 5 in published ratings.
Steps 2 through 4 examine specific categories of risk. Step 5 asks a fundamentally different question. It does not look for another type of risk. It looks for mechanisms that make existing risk harder to see.
False assurance refers to features, claims, and presentation choices that create the appearance of safety without reducing actual exposure. These mechanisms do not make a system less risky. They make the investor less likely to investigate whether the system is risky.
The effect on capital is identical to having no protection at all, but the investor's perception suggests otherwise.
How false assurance operates.
Each mechanism appears to address a legitimate concern: risk management, drawdown exposure, system failure probability, third-party validation. An investor encountering these features has a reasonable basis for believing the system has been designed with their protection in mind. That belief reduces the motivation to investigate further.
The false assurance mechanisms.
The inversion.
This inversion — from risk reduction to scrutiny reduction — is the analytical contribution that distinguishes Step 5. Steps 2 through 4 identify conditions in the system. Step 5 identifies conditions in the evaluation process itself. It is an audit of the investor's own analytical defenses.
Frequently asked questions.
False assurance refers to features and claims that make an algorithmic system appear safer than it actually is. In the Algo Institute's framework, false assurance reduces the investor's motivation to investigate further rather than reducing actual risk. Common examples include user-configured risk settings, mismatched capital bases, and verification claims that do not constitute independent audit.
If the system needs the user to set a risk threshold, the system itself lacks internal risk management. The setting functions as a kill switch on unrealized exposure, not a risk management tool. It appears to give the investor control. It actually reveals that the system has no built-in mechanism to manage its own risk.
Verification confirms specific data points — that trades occurred and numbers match records. Independent audit examines methodology, risk exposure, and structural characteristics. "Verified" performance can still carry unexamined structural risk. The distinction matters because verification can satisfy an investor's desire for validation without actually validating structural soundness.