Deviation monitoring and runtime diagnosis
Check operational changes against data, decision, execution and accounting records. Present differences, their impact and evidence coverage to support further diagnosis and validation.
Local read-only diagnosis. Inspect authorised data, configuration and runtime records to produce findings and review recommendations. The inspected systems and records remain unchanged.
In-system monitoring. Connect strategy and runtime evidence to compare states and results continuously within the scope enabled in the current release.
Diagnostic records distinguish known facts, causal hypotheses and recommended actions. Further tests take place in an isolated environment; relevant results are checked again before recovery.
| Category | Checks |
|---|---|
| Data | Missing and duplicate records, security identities, corporate actions and point-in-time availability. |
| Research | Data snapshots, strategy versions, parameters, configuration and dependencies. |
| Backtesting | Trading calendars, fill assumptions, costs and market constraints. |
| Portfolio | Target weights, cash conditions and risk adjustments. |
| Execution and accounts | Orders, fills, positions, cash and profit-and-loss records. |
| Incidents and recovery | Issues, actions taken, validation results and recovery conditions. |
Conclusions state the evidence coverage and the areas not yet verified.
Diagnosis reads authorised material; testing takes place in a separate workspace. Any action that restricts, pauses or resumes operation must comply with current-release capabilities, project rules and authorisation requirements.
