trade-path-audit

The audit identifies safety-gate violations by checking the executor against predefined error classes and adversarial personas. It generates a severity-ranked findings report with file:line citations and actionable fix recommendations for remediation.

Trading executor safety checks are predefined gates, error classes, and adversarial checks that prevent unsafe execution. You need to audit them when retrofitting safety checks to existing code or reviewing live and paper trading implementations against known bug classes.

Provide the executor path, such as executors/<name>/, and run the retroactive audit. It produces a severity-ranked findings report with file:line citations and actionable fix recommendations for remediation.

Yes, you can retrofit safety gates onto a live trading executor. The audit reviews live or paper implementations against known bug classes, error classes, and adversarial checks defined in the build-executor references.

The best way to review a trading executor against known bug classes is to run a retroactive audit. This leverages build-executor references for error classes, adversarial personas, parity checks, and handicaps to guide the comprehensive review.

No, the trading executor audit does not require any specific external dependencies to run. It operates directly on the executors/<name>/ directory and loads guidance from the local build-executor references.