4.12 RuleChangeMonitor

1. Bot Identity

2. Purpose

Detect and emit any post-listing edit to a market's resolution rule.

3. Why This Bot Matters

• Resolution rule edited under an open position

  If a market's rule changes after a strategy entered, the basis for that trade may no longer exist. Without monitoring, the position is held through the change without anyone on the team being told.

• Cosmetic vs semantic edits not distinguished

  Many edits are punctuation or formatting; a few are substantive. Treating all edits the same either floods operators with false alarms or misses the one that matters.

• Audit trail of rule history missing

  Compliance and dispute reviews require a full history of every rule change with timestamps. Polymarket's UI does not expose this; the monitor builds the record the team needs.

• Strategies can't auto-pause on rule change

  A strategy that reads a rule-change event can decide to flatten or hold automatically. Without the event, the team is the only line of defence and must catch every edit by hand.

4. Required Polymarket Inputs

5. Required Internal Inputs

6. Parameter Guide

7. Detailed Parameter Instructions

{ "poll_interval_s": 300 }

if (p.poll_interval_s > p.hard) throw ConfigError('PARAMETER_CHANGE_REQUIRES_APPROVAL');

{ "max_markets_per_cycle": 500 }

if (p.max_markets_per_cycle > p.hard) throw ConfigError('PARAMETER_CHANGE_REQUIRES_APPROVAL');

8. Default Configuration

{
  "bot_id": "intel.rulechangemonitor",
  "version": "0.1.0",
  "mode": "planned",
  "defaults": {
    "poll_interval_s": 300,
    "max_markets_per_cycle": 500
  },
  "locked": {
    "poll_interval_s": {
      "max": 3600
    },
    "max_markets_per_cycle": {
      "max": 1000
    }
  }
}

9. Implementation Flow

— not yet authored —

10. Reference Implementation

Pseudocode is language-agnostic. FETCH = read input. EMIT = produce output. IF/THEN/ELSE = decision. Translate directly to TypeScript, Python, Go, or Rust.

FUNCTION monitorRuleChanges():
  // 0. KillSwitch check
  IF FETCH internal.killswitch.status == ACTIVE:
    RETURN

  // 1. Fetch active markets from Gamma
  markets = FETCH gamma.GET('/markets?status=active')
  IF len(markets) == 0:
    EMIT WARN 'STALE_DATA'
    RETURN

  // 2. Compare against stored snapshots
  FOR m IN markets:
    stored = db.get(m.condition_id)
    IF stored IS NULL:
      db.set(m.condition_id, snapshot(m))
      CONTINUE

    // 3. Detect rule or question changes
    IF hash(m.resolution_rules) != stored.rules_hash:
      EMIT WARN 'RULECHANGEMONITOR_RULE_CHANGED'
      EMIT ObservationReport with change_type='resolution_rules'
    IF hash(m.question) != stored.question_hash:
      EMIT WARN 'RULECHANGEMONITOR_QUESTION_CHANGED'
      EMIT ObservationReport with change_type='question'

    // 4. Update snapshot
    db.set(m.condition_id, snapshot(m))

SDK calls used

• gamma.GET('/markets?status=active')
• internal.killswitch.status

Complexity: O(M) per poll cycle where M = active markets

11. Wire Examples

Input — what arrives on the wire

{
  "label": "Gamma market response with changed resolution rules",
  "source": "gamma",
  "payload": {
    "condition_id": "0xf1a2b30000000000000000000000000000000000000000000000000000000000",
    "resolution_rules": "Resolves YES if Coinbase BTC/USD close price on Dec 31 2026 is >= 100000. UPDATED: Binance price also accepted.",
    "timestamp_ms": 1746703000000
  }
}

Output — what the bot emits

{
  "label": "ObservationReport — resolution rule changed",
  "payload": {
    "report_id": "rep_rcm_0xf1a2_1746703000000",
    "trace_id": "trc_0xbeef0102030405060713",
    "bot_id": "intel.rulechangemonitor",
    "kind": "ObservationReport",
    "condition_id": "0xf1a2b30000000000000000000000000000000000000000000000000000000000",
    "change_type": "resolution_rules",
    "old_hash": "0xabcd1234",
    "new_hash": "0xefgh5678",
    "emitted_at_ms": 1746703005000
  }
}

12. Decision Logic

13. Standard Decision Output

This bot returns a RiskVote object. See RiskVote schema.

{
  "report_id": "rep_rcm_0xf1a2_1746703000000",
  "trace_id": "trc_0xbeef0102030405060713",
  "bot_id": "intel.rulechangemonitor",
  "kind": "ObservationReport",
  "condition_id": "0xf1a2b30000000000000000000000000000000000000000000000000000000000",
  "change_type": "resolution_rules",
  "old_hash": "0xabcd1234",
  "new_hash": "0xefgh5678",
  "change_detected": true,
  "emitted_at_ms": 1746703005000
}

14. Reason Codes

15. Metrics & Logs

Metrics emitted

Alerts

Dashboards

• Grafana — Intelligence / RuleChangeMonitor rule-change event rate

16. Developer Reporting

{
  "bot_id": "intel.rulechangemonitor",
  "markets_checked": 312,
  "rule_changes_detected": 1,
  "question_changes_detected": 0,
  "gamma_response_ms": 850,
  "killswitch_active": false,
  "emitted_at_ms": 1746703005000
}

17. Plain-English Reporting

18. Failure-Mode Block

19. Failure-Injection Recipes

20. State & Persistence

Cold-start recovery

On cold start, reload all snapshots from Postgres; run full comparison on first cycle.

21. Concurrency & Idempotency

22. Dependencies

Depends on (must run first)

Emits to (downstream consumers)

Sibling bots (same OrderIntent)

External services

23. Security Surfaces

Abuse vectors considered

• Adversary manipulates Gamma API response to inject false rule-change signals
• High-frequency rule updates flood RuleChangeMonitor with WARN events

Mitigations

• Postgres audit log provides tamper-evident record of all rule changes
• Alert thresholds prevent single-event paging from minor text edits

24. Polymarket V2 Compatibility

API surfaces declared

Networks supported

25. Versioning & Migration

Migration history

26. Acceptance Tests

Unit Tests

Integration Tests

Property Tests

27. Operational Runbook

RuleChangeMonitor alerts on resolution rule or question changes. Any rule change during a live position must be reviewed immediately. Postgres audit log is the compliance record.

On-call actions

Manual overrides

• force_resync — POST /internal/rulechangemonitor/resync to force full snapshot comparison on all active markets — After Gamma API recovery or suspected missed changes

Healthcheck

Endpoint: /internal/health/rulechangemonitor | Green: Last poll < 30 min ago AND Postgres reachable AND Gamma API returning 200 | Red: No poll for > 1 h OR Postgres unreachable

28. Promotion Gates

A bot does not advance to the next readiness state until every gate below is green. Gates are observable from production data — no subjective sign-off.

Promote to Shadow

Promote to Limited live

Promote to General live

29. Developer Checklist

Ready-to-ship score: 27/27 sections complete · 100%