6.8 StrategyRegistry

1. Bot Identity

2. Purpose

StrategyRegistry is the single source of truth for which strategy is at which lifecycle stage and under what authority. It stores stage metadata, promotion history, linked artefacts, and live-cap policy.

3. Why This Bot Matters

• No centralised registry

  Multiple bots may execute strategies at conflicting stages, making audits impossible.

• Promotion without recorded approval

  Compliance audit finds no evidence trail; promotion may need to be reversed.

No worked examples on this bot yet. Worked examples are optional but strongly recommended — they turn an abstract failure mode into something a developer can verify in a fixture.

4. Required Polymarket Inputs

5. Required Internal Inputs

6. Parameter Guide

7. Detailed Parameter Instructions

{ "require_two_person_promotion": ["to_limited_live", "to_general_live"] }

if stage in p.require_two_person_promotion and approvers.count < 2: raise ConfigError

{ "min_shadow_days": 3 }

if shadow_days < p.min_shadow_days: raise PromotionError('PROMOTION_GATE_FAILED')

8. Default Configuration

{
  "bot_id": "gov.strategyregistry",
  "version": "0.1.0",
  "mode": "shadow_only",
  "defaults": {
    "require_two_person_promotion": [
      "to_limited_live",
      "to_general_live"
    ],
    "min_shadow_days": 3,
    "min_backtest_days": 7,
    "auto_demote_on_drift": true
  }
}

9. Implementation Flow

1. On startup, load the strategy registry table from Postgres; index by slug.
2. When a promotion request arrives, validate artefacts and approver count against promotion gates.
3. Write stage change to registry with timestamp, approver IDs, and linked artefact references.
4. Emit OperationsReport(event_type=STRATEGY_PROMOTED) to polytraders.reports.operations.
5. On drift signal from ExperimentTracker, auto-demote to previous stage if auto_demote_on_drift=true.
6. Provide read API for other bots to query current strategy stage and live-cap.

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.

// ---- STARTUP ----
FUNCTION init():
  registry = postgres.loadAll('strategy_registry')
  indexBySlug(registry)

// ---- PROMOTION REQUEST ----
FUNCTION handlePromotionRequest(req):
  entry = registry.get(req.slug)
  IF entry IS NULL: RAISE 'STRATEGY_NOT_FOUND'
  IF NOT artefactsPresent(entry, req.to_stage): RAISE 'PROMOTION_GATE_FAILED'
  IF req.to_stage IN config.require_two_person_promotion:
    IF len(req.approvers) < 2: RAISE 'PROMOTION_GATE_FAILED'
  IF entry.stage == 'shadow' AND entry.shadow_days < config.min_shadow_days:
    RAISE 'PROMOTION_GATE_FAILED'
  entry.stage = req.to_stage
  entry.updated_at = now()
  postgres.upsert('strategy_registry', entry)
  EMIT OperationsReport(event_type='STRATEGY_PROMOTED', slug=req.slug,
    from_stage=entry.prev_stage, to_stage=req.to_stage,
    approvers=req.approvers)

// ---- DRIFT AUTO-DEMOTE ----
FUNCTION onDriftSignal(slug):
  IF config.auto_demote_on_drift:
    entry = registry.get(slug)
    entry.stage = entry.prev_stage
    postgres.upsert('strategy_registry', entry)
    EMIT OperationsReport(event_type='STRATEGY_DEMOTED', slug=slug)
  ELSE:
    EMIT OperationsReport(event_type='STRATEGY_DRIFT_DETECTED', slug=slug)

SDK calls used

• postgres.loadAll('strategy_registry')
• postgres.upsert('strategy_registry', entry)
• alerting.emit('PROMOTION_GATE_FAILED', metadata)

Complexity: O(1) per promotion request; O(N) on startup where N = registered strategies

11. Wire Examples

Input — what arrives on the wire

{
  "label": "Promotion request",
  "source": "governance_pod",
  "payload": {
    "slug": "sports-model",
    "from_stage": "shadow",
    "to_stage": "limited_live",
    "approvers": [
      "alice@polytraders",
      "bob@polytraders"
    ],
    "artefacts": {
      "shadow_report": "sh_01HX9Y"
    }
  }
}

Output — what the bot emits

{
  "label": "OperationsReport — STRATEGY_PROMOTED",
  "payload": {
    "report_id": "ops_strategyregistry_01HX9Z",
    "bot_id": "gov.strategyregistry",
    "event_type": "STRATEGY_PROMOTED",
    "slug": "sports-model",
    "to_stage": "limited_live",
    "report_kind": "OperationsReport",
    "topic": "polytraders.reports.operations"
  }
}

12. Decision Logic

13. Standard Decision Output

This bot returns a OperationsReport object. See OperationsReport schema.

{
  "report_id": "ops_strategyregistry_01HX9Z",
  "bot_id": "gov.strategyregistry",
  "event_type": "STRATEGY_PROMOTED",
  "slug": "sports-model",
  "from_stage": "shadow",
  "to_stage": "limited_live",
  "approvers": [
    "alice@polytraders",
    "bob@polytraders"
  ],
  "artefacts": {
    "backtest_report": "bt_01HX8Z",
    "shadow_report": "sh_01HX9Y"
  },
  "report_kind": "OperationsReport",
  "topic": "polytraders.reports.operations",
  "retained_until": "2027-05-09"
}

14. Reason Codes

15. Metrics & Logs

Metrics emitted

Alerts

16. Developer Reporting

{
  "bot_id": "gov.strategyregistry",
  "event_type": "REGISTRY_QUERY",
  "slug": "sports-model",
  "stage": "limited_live",
  "queried_at_ms": 1746792060000
}

17. Plain-English Reporting

18. Failure-Mode Block

19. Failure-Injection Recipes

20. State & Persistence

Cold-start recovery

On restart, reload registry from Postgres immediately.

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

• Submitting a promotion request with forged approver identity
• Bypassing two-person rule by replaying a previous approval token

Mitigations

• Approver identities are verified via internal auth; promotion events are immutably audit-logged
• Idempotency key prevents replay of a previous approval

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

StrategyRegistry incidents involve DB unavailability or unexpected demotions. Every PROMOTION_GATE_FAILED is informational unless it blocks a scheduled launch.

On-call actions

Manual overrides

• —

Healthcheck

/internal/health/strategyregistry → green if Postgres reachable; registry loaded; last write < 1h ago; red if Postgres unreachable or registry empty

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%