chemavxandClaude Opus 4.8
3a353c7e5b
CI/CD / build-and-push (push) Successful in 8s
Per-category coverage audit showed coverage_rate=0.0 across every category in the bot's current universe, so any edge Manifold produced was false edge. Retire it as an ACTIVE trading signal while keeping the full audit/coverage/cooldown trail for a future reactivation decision. Two module-level flags in bayesian.py (read from env): - MANIFOLD_SIGNAL_ENABLED (default False): when False, Manifold never touches the edge model — manifold_log_adj stays 0.0 (no posterior shift), no confidence bump, feat_mfld_lo=0.0 (so it can never be the dominant feature), no trade contribution, and mfld_audit_id is not propagated so the audit's used_in_trade stays FALSE. - MANIFOLD_AUDIT_ENABLED (default True): matcher still runs; audit/coverage rows and cooldowns are still written. The matcher is only called when a flag is on. When signal is disabled, logs and reasoning carry "Manifold: observational_only". Endpoints /api/metrics/manifold-matches and /api/metrics/manifold-coverage, cooldowns, audit tables and existing trades are unchanged. No code or tables removed. Other signals, thresholds, exposure, risk manager and the executor are untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>