{
  "id": 447,
  "rank": 2333,
  "name": "BTCUSD Scalping Intelligence Engine",
  "aka": [
    "BTCUSD Scalping AI",
    "BTCUSD Scalping Engine"
  ],
  "family": "E",
  "subtype": "E3",
  "one_liner": "Multi-timeframe BTCUSD scalping engine with layered decision logic and risk control.",
  "market_regime": "trending|ranging|volatile|breakout",
  "timeframes": [
    "H4",
    "H1",
    "M15",
    "M5",
    "Tick Flow"
  ],
  "symbols": [
    "BTCUSD"
  ],
  "sessions": [
    "WIB session mapping and preset override engine"
  ],
  "indicators": [
    {
      "name": "BTC_Scalping_ChartBrain",
      "params": {},
      "applied_to": "close"
    }
  ],
  "entry_long": [
    "BuySignal > 0",
    "BuyScore > 0",
    "SuggestedEntry > 0"
  ],
  "entry_short": [
    "SellSignal < 0",
    "SellScore < 0",
    "SuggestedEntry < 0"
  ],
  "exit_rules": [
    "SuggestedSL hit",
    "SuggestedTP1 hit",
    "SuggestedTP2 hit",
    "StopLoss hit",
    "TakeProfit hit",
    "ATR trailing stop"
  ],
  "filters": [
    "spread and tick-pressure filtering",
    "structure-based stop loss",
    "max consecutive loss guard",
    "max trades per day guard",
    "minimum risk/reward validation"
  ],
  "stop_loss": "ATR based",
  "take_profit": "ATR based with TP1 and TP2",
  "position_size": "risk-based lot sizing with max daily loss guard",
  "evidence_type": "backtest_shown",
  "completeness": 50.0,
  "signal_warnings": null,
  "claim_warnings": null,
  "opacity_warnings": [
    "UNDEFINED ENTRY TERM: the entry conditions are prose naming a concept with no numeric definition, so two readers would implement them differently. Advisory only -- this does not affect the score."
  ],
  "build_warnings": null,
  "canonical": "https://prismaticalgos.com/compendium/algo/447-btcusd-scalping-intelligence-engine",
  "snapshot": "2026-10-31 15:46 UTC",
  "source_url": "https://github.com/said00001/BTCUSD-Scalping-Intelligence-Engine",
  "limitations": "These are machine-extracted research records, not verified trading systems. Catalog rank measures specification detail and claimed evidence, not profitability. The catalog extraction pipeline did not independently backtest these records. Its separate selected testing ledger does not validate the wider corpus. Rules, labels and parameters can be incomplete or wrong; consult the original source and its reuse terms."
}