FactoryWager ops Limits

Baseline provenance

Loading Tier 3 partner API + Tier 4 Caesars scrape status…

Partner limit patterns

Trace observed limit movement from partner to downline, sportsbook, jurisdiction, and ZIP cluster while keeping policy, license, prediction, and proof evidence directly inspectable. The signal window covers 48 hours and refreshes every 30 seconds.

Account limit control Definition Profile semantics Artifact

Review one evidence-backed control record per partner-tree account. Profile identity, jurisdiction and license readiness, observed sportsbook limits, effective policy bindings, and the event trace remain separate and directly inspectable.

Compliance policy KPIs

Decision metrics derived from governed policies and blocked-wager evidence. Each label opens its glossary definition.

Jurisdiction policy catalog

Effective internal policy codes projected from regulatory_limits. New states appear automatically when policy rows are added.

0 Changes observed rows
0% Raised share upward movements
$0 Net delta USD across selection
Avg influence scored changes
0 Accounts tree nodes with changes
0 Sportsbooks connected sources
0 Downline agents and sub-agents
0 States licensed jurisdictions
0 ZIP clusters three-digit prefixes
0% Coverage connected evidence

Loading prediction accuracy…

Model formula · bun-1.4.0-limit-v1 P(raise) = clamp(5%, 95%, 0.30F + 0.25T + 0.30I + 0.15W) F = seven-day raise frequency · T = normalized daily limit trend · I = multi-factor influence · W = UTC operating-window signal. Expected magnitude is the mean recent raise divided by the current limit.

Deterministic findings ranked from the connected 48-hour artifact; every finding names its evidence and remains reproducible from limit-raises.json.

No limit changes found. Seed connected data with bun tools/seed-limit-patterns.ts --force --bake.