> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sleuthintel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sleuth × Polymarket - RFB Alignment

> Original Sleuth document.

<div style={{ margin: "-24px -32px", width: "calc(100% + 64px)" }}>
  <iframe title="Sleuth × Polymarket - RFB Alignment" srcDoc={"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"UTF-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n<title>Sleuth \u00d7 Polymarket \u00b7 RFB Alignment</title>\n<link href=\"https://fonts.googleapis.com/css2?family=Orbitron:wght@500;700;900&family=Share+Tech+Mono&display=swap\" rel=\"stylesheet\">\n<style>\n:root{\n  --green:#00FF66; --green-dim:#00cc52; --green-glow:rgba(0,255,102,0.3);\n  --green-faint:rgba(0,255,102,0.06); --bg:#060606; --card:#0c0c0c;\n  --border:#1a1a1a; --text:#FFD700; --gold:#FFD700; --gold-glow:rgba(255,215,0,0.25);\n}\n*{margin:0;padding:0;box-sizing:border-box;}\nbody{background:var(--bg);color:var(--text);font-family:'Share Tech Mono',monospace;line-height:1.65;overflow-x:hidden;}\n.wrap{position:relative;z-index:1;max-width:1020px;margin:0 auto;padding:0 24px 60px;}\n\n.hero{padding:90px 0 40px;text-align:left;border-bottom:1px solid var(--border);}\n.hero .vtag{color:var(--gold);opacity:0.75;font-size:0.75rem;letter-spacing:2.5px;margin-bottom:22px;}\n.hero h1{font-family:'Orbitron',sans-serif;font-weight:900;font-size:clamp(1.9rem,5vw,3.1rem);\n  color:var(--green);letter-spacing:4px;line-height:1.2;text-shadow:0 0 24px var(--green-glow);}\n.hero .lead{color:var(--gold);margin-top:22px;font-size:1rem;max-width:840px;}\n\n.section{padding:70px 0 20px;}\n.eyebrow{color:var(--gold);font-size:0.8rem;letter-spacing:3px;margin-bottom:10px;}\nh2{font-family:'Orbitron',sans-serif;font-weight:700;color:var(--green);font-size:clamp(1.3rem,3vw,1.9rem);\n  letter-spacing:2px;margin-bottom:20px;text-shadow:0 0 14px var(--green-glow);}\nh3{font-family:'Orbitron',sans-serif;font-weight:700;color:var(--green);font-size:1.02rem;\n  letter-spacing:1.5px;margin:30px 0 12px;}\np{margin:12px 0;}\nul{margin:12px 0 12px 22px;}\nli{margin:7px 0;}\nstrong{color:var(--green);}\nem{color:var(--gold);font-style:normal;border-bottom:1px dashed var(--gold);}\n\n.match{border:1px solid var(--border);background:var(--card);border-radius:3px;margin:26px 0;overflow:hidden;}\n.match-head{display:flex;align-items:center;justify-content:space-between;gap:14px;flex-wrap:wrap;\n  padding:18px 24px;border-bottom:1px solid var(--border);background:rgba(0,255,102,0.03);}\n.match-title{font-family:'Orbitron',sans-serif;font-weight:700;color:var(--green);letter-spacing:1.5px;font-size:1rem;}\n.badge{font-family:'Orbitron',sans-serif;font-weight:700;font-size:0.68rem;letter-spacing:1.5px;\n  padding:6px 12px;border-radius:3px;white-space:nowrap;}\n.badge.live{color:#060606;background:var(--green);box-shadow:0 0 12px var(--green-glow);}\n.badge.engine{color:var(--green);border:1px solid var(--green-dim);background:rgba(0,255,102,0.05);}\n.badge.ship{color:var(--gold);border:1px solid var(--gold);background:rgba(255,215,0,0.05);}\n.match-body{padding:8px 24px 22px;}\n.rfb-quote{border-left:2px solid var(--gold);padding:10px 16px;margin:16px 0;color:var(--gold);\n  background:rgba(255,215,0,0.03);font-size:0.92rem;}\n.rfb-quote .src{font-size:0.72rem;letter-spacing:2px;opacity:0.7;display:block;margin-bottom:6px;}\n\ntable{width:100%;border-collapse:collapse;margin:22px 0;font-size:0.88rem;}\nth{color:var(--gold);text-align:left;padding:10px 12px;border-bottom:1px solid var(--green-dim);\n  letter-spacing:1px;font-weight:400;}\ntd{padding:10px 12px;border-bottom:1px solid var(--border);vertical-align:top;}\ntr:hover td{background:var(--green-faint);}\n.tablewrap{overflow-x:auto;}\n\n.callout{border:1px solid var(--green-dim);background:rgba(0,255,102,0.04);padding:24px 28px;\n  margin:26px 0;border-radius:2px;}\n.callout .ct{font-family:'Orbitron',sans-serif;color:var(--green);letter-spacing:2px;font-size:0.95rem;margin-bottom:10px;}\n\n.copy-block{border:1px dashed var(--gold);background:rgba(255,215,0,0.03);padding:22px 26px;margin:24px 0;border-radius:2px;}\n.copy-title{font-family:'Orbitron',sans-serif;color:var(--gold);letter-spacing:2px;font-size:0.85rem;margin-bottom:12px;}\n.copy-note{color:var(--gold);opacity:0.6;font-size:0.75rem;margin-top:12px;letter-spacing:1px;}\n.internal-strip{border-top:2px solid var(--gold);margin-top:70px;padding-top:10px;}\n.internal-strip .warn{font-family:'Orbitron',sans-serif;color:var(--gold);letter-spacing:2px;font-size:0.8rem;}\n\n.footer{border-top:1px solid var(--border);margin-top:70px;padding-top:24px;font-size:0.75rem;\n  color:var(--green-dim);letter-spacing:2px;display:flex;justify-content:space-between;flex-wrap:wrap;gap:10px;}\n@media(max-width:640px){.match-head{flex-direction:column;align-items:flex-start;}}\n</style>\n</head>\n<body>\n<div class=\"wrap\">\n\n<div class=\"hero\">\n  <div class=\"vtag\">SLEUTH \u00d7 POLYMARKET \u00b7 BUILDERS PROGRAM \u00b7 RFB ALIGNMENT \u00b7 JULY 2026</div>\n  <h1>YOUR RFB PAGE DESCRIBES OUR ARCHITECTURE.</h1>\n  <p class=\"lead\">The Explore Ideas board at builders.polymarket.com asks for three things under Forecasting, Data, AI Agents and Reputation Systems: composable resolved-market data, reputation-weighted resolvers, and crowdsourced forecasting agents. Sleuth is one of those outright, has already built the engine for the second, and can ship the third as a grant deliverable on infrastructure that is running today. This doc maps each request to what exists, precisely, with no inflation.</p>\n</div>\n\n<!-- \u2500\u2500 01 \u2500\u2500 -->\n<section class=\"section\">\n  <div class=\"eyebrow\">// 01</div>\n  <h2>The Three Requests, Mapped</h2>\n\n  <div class=\"match\">\n    <div class=\"match-head\">\n      <div class=\"match-title\">CROWDSOURCED FORECASTING AGENTS</div>\n      <span class=\"badge live\">THIS IS SLEUTH</span>\n    </div>\n    <div class=\"match-body\">\n      <div class=\"rfb-quote\"><span class=\"src\">RFB \u00b7 EXPLORE IDEAS</span>\"Swarms of agents reading news, onchain data, and social signals to coordinate positions. Crypto-native quant at scale.\"</div>\n      <p>That sentence is the Sleuth pitch, written by someone else. Our whole design is agent-first:</p>\n      <ul>\n        <li><strong>Agents are first-class economic citizens.</strong> Same contribution rates, same rules, same slashing as humans. An agent earns reputation and wages under identical mechanics. This is in the whitepaper as a core design principle, not a feature bullet.</li>\n        <li><strong>The three signal sources named in the RFB are our three product pillars.</strong> News and narrative: Signals tracks narrative velocity across social, exchange and on-chain sources. Onchain data: wallet discovery, cluster mapping, transaction pattern intelligence. Social signals: alpha account tracking and accuracy scoring over time.</li>\n        <li><strong>Native agent access.</strong> The platform is built to be called by agents via API and MCP, not scraped by them. An agent queries trader positions, market flow and narrative signals through the same endpoints a human dashboard uses.</li>\n        <li><strong>The swarm is the workforce.</strong> The contribution economy pays agents for accepted intel from contribution one. The RFB asks for swarms that coordinate positions. We built the economy that recruits, pays and polices that swarm.</li>\n      </ul>\n      <p><em>Status: live product on Polymarket data today. Six product sections in production including a full trader leaderboard with profile-level positions and a live market heatmap.</em></p>\n    </div>\n  </div>\n\n  <div class=\"match\">\n    <div class=\"match-head\">\n      <div class=\"match-title\">REPUTATION-WEIGHTED RESOLVERS</div>\n      <span class=\"badge engine\">ENGINE BUILT \u00b7 NEW TARGET</span>\n    </div>\n    <div class=\"match-body\">\n      <div class=\"rfb-quote\"><span class=\"src\">RFB \u00b7 EXPLORE IDEAS</span>\"Score market resolvers by accuracy, dispute history, and capital at stake. A clear signal on which markets are safe.\"</div>\n      <p>Break that request into its three components and each one is a mechanic Sleuth already runs:</p>\n      <ul>\n        <li><strong>Accuracy scoring.</strong> aSLEUTH is a reputation ledger that can only be earned through verified, graded contributions. It cannot be bought at any price. Every verifier on the platform carries an accuracy score that tracks how their verdicts hold up over time, and that score decides how much weight they get.</li>\n        <li><strong>Dispute history.</strong> Our head hunting layer pays contributors to find and flag bad data. Every flag, every upheld dispute, every appeal is recorded against the offender's ledger. Dispute history is not a field we would add. It is a first-class output of the system.</li>\n        <li><strong>Capital at stake.</strong> Slashing burns earned reputation and forfeits unvested wages on bad data. Grade 1 conduct is a 100% burn. Contributors have real, accumulated value on the line with every submission.</li>\n      </ul>\n      <p>Today this engine points at intel contributors and verifiers. The RFB asks for it pointed at market resolvers. <strong>That is a retargeting of live machinery, not a new build.</strong> Resolver identities, resolution outcomes and dispute records are public data. Feeding them through the scoring engine we already operate produces exactly the safety signal the RFB describes.</p>\n      <p><em>Status: reputation mechanics specified in full in the whitepaper and running through adversarial simulation. Resolver scoring is a scoped extension, and a natural grant deliverable.</em></p>\n    </div>\n  </div>\n\n  <div class=\"match\">\n    <div class=\"match-head\">\n      <div class=\"match-title\">COMPOSABLE RESOLVED-MARKET DATA</div>\n      <span class=\"badge ship\">PIPES LIVE \u00b7 FEED SHIPPABLE</span>\n    </div>\n    <div class=\"match-body\">\n      <div class=\"rfb-quote\"><span class=\"src\">RFB \u00b7 EXPLORE IDEAS</span>\"Queryable feeds of settled markets. High-confidence ground truth that other protocols can build on.\"</div>\n      <p>The two halves of this request sit on infrastructure we already run:</p>\n      <ul>\n        <li><strong>Queryable feeds.</strong> Sleuth already serves Polymarket market data through structured API endpoints built for machine consumption. A settled-markets feed is a thin layer on pipes that exist, not a new data platform.</li>\n        <li><strong>High-confidence ground truth.</strong> \"Outcome verification of resolved markets\" is already a named, paid contribution category in our whitepaper. The swarm gets paid to verify settled outcomes, verifiers stake reputation on those verifications, and bad verifications get slashed. That is what turns a feed of settled markets into ground truth other protocols can trust: every data point carries accountable reputation behind it.</li>\n      </ul>\n      <p>Most teams could ship a resolved-markets API. What they cannot ship is the confidence layer, because that requires a reputation economy underneath the data. We have one.</p>\n      <p><em>Status: data infrastructure live, verification category specified. The composable settled-markets feed is a defined deliverable, not a live feature.</em></p>\n    </div>\n  </div>\n</section>\n\n<!-- \u2500\u2500 02 \u2500\u2500 -->\n<section class=\"section\">\n  <div class=\"eyebrow\">// 02</div>\n  <h2>Why the Fit Is Structural, Not Coincidental</h2>\n  <div class=\"callout\">\n    <div class=\"ct\">ONE ENGINE, THREE OUTPUTS</div>\n    <p>The three RFB ideas are usually pitched by three different teams: a data team, a reputation team, an agent team. On Sleuth they are one system. Agents consume the data feeds, the reputation economy guarantees the data quality, and the same reputation economy governs the agents. Fund one of the three ideas through us and the other two get stronger for free. That is what composable actually means.</p>\n  </div>\n  <div class=\"tablewrap\"><table>\n    <tr><th>RFB Idea</th><th>What Sleuth Has</th><th>Status</th><th>Grant Role</th></tr>\n    <tr><td>Crowdsourced forecasting agents</td><td>Agent-first platform, API and MCP access, agents as equal economic citizens, Pulse + onchain + social signal coverage</td><td>Live on Polymarket data</td><td>The anchor. Proof we are the right team.</td></tr>\n    <tr><td>Reputation-weighted resolvers</td><td>aSLEUTH earned reputation, verifier accuracy scores, dispute layer, slashing with real value at stake</td><td>Engine specified and simulated</td><td>Deliverable: point the engine at resolvers</td></tr>\n    <tr><td>Composable resolved-market data</td><td>Structured market data API in production, outcome verification as a paid contribution category</td><td>Pipes live, feed scoped</td><td>Deliverable: settled-markets ground truth feed</td></tr>\n  </table></div>\n</section>\n\n<!-- \u2500\u2500 03 \u2500\u2500 -->\n<section class=\"section\">\n  <div class=\"eyebrow\">// 03</div>\n  <h2>Why We Are a Strong Grant Candidate</h2>\n  <ul>\n    <li><strong>Live product, not a deck.</strong> Six product sections in production with Polymarket coverage today. Trader leaderboard, profile-level positions and history, live market heatmap. The grant funds extensions to a running platform.</li>\n    <li><strong>Documentation depth unusual for our stage.</strong> Full whitepaper, deck and lite paper covering token mechanics, platform economics and an adversarial simulation of our own reward system. We attacked our own economy before asking anyone to fund it.</li>\n    <li><strong>Volume alignment, not just grant alignment.</strong> Builder code registered, order routing in active development. Every trader profile view and every agent monitoring a position becomes attributed Polymarket volume. We are building toward the weekly rewards, which means our incentives and Polymarket's point the same direction long after any grant.</li>\n    <li><strong>Honest status labels.</strong> Everything above is marked live, specified or scoped. Nothing unbuilt is claimed as shipped. A grader can verify every live claim on the platform today.</li>\n  </ul>\n</section>\n\n<!-- \u2500\u2500 INTERNAL \u2500\u2500 -->\n<div class=\"internal-strip\">\n  <div class=\"warn\">// INTERNAL FROM HERE DOWN \u00b7 STRIP THIS SECTION BEFORE SENDING TO POLYMARKET</div>\n</div>\n\n<section class=\"section\">\n  <div class=\"eyebrow\">// A1 \u00b7 Internal</div>\n  <h2>Application Form Copy</h2>\n\n  <div class=\"copy-block\">\n    <div class=\"copy-title\">RFB alignment paragraph \u00b7 drop into the grant application</div>\n    <p>Your Explore Ideas board asks for composable resolved-market data, reputation-weighted resolvers, and crowdsourced forecasting agents. Sleuth is the third one today: a live, agent-first intelligence platform on Polymarket data, with six product sections in production and native API and MCP access built for agents reading narrative, onchain and social signals. The other two are extensions of machinery we already run. Our earned-reputation system scores contributors by accuracy, records dispute history, and puts slashed value at stake, which is exactly the mechanism resolver scoring needs, pointed at a new target. And outcome verification of resolved markets is already a paid contribution category in our economy, which is what turns a settled-markets feed into ground truth other protocols can build on. One platform covers your whole category, and the parts that are live are verifiable today.</p>\n    <div class=\"copy-note\">// keep the live vs scoped distinction intact if edited. never claim resolver scoring or the settled feed as live.</div>\n  </div>\n\n  <div class=\"copy-block\">\n    <div class=\"copy-title\">Deliverables list \u00b7 grant scope</div>\n    <p>1. Settled-markets feed: queryable API and MCP endpoints for resolved Polymarket markets with swarm-verified outcomes. 2. Resolver reputation module: accuracy, dispute history and stake-weighted scoring for market resolvers, surfaced in PM Markets and via API. 3. Agent access hardening: documented MCP toolset so third-party agents consume both of the above natively.</p>\n    <div class=\"copy-note\">// sequence intentionally: feed first, resolver scoring second, since scoring consumes the feed.</div>\n  </div>\n\n  <div class=\"copy-block\">\n    <div class=\"copy-title\">One-liner if asked why us</div>\n    <p>The three ideas on your board are one system on ours: agents consume the data, reputation guarantees the data, and the same reputation governs the agents.</p>\n  </div>\n</section>\n\n<section class=\"section\">\n  <div class=\"eyebrow\">// A2 \u00b7 Internal</div>\n  <h2>Notes Before Sending</h2>\n  <ul>\n    <li><strong>MCP wording.</strong> The doc says access is \"built for\" agents via API and MCP, matching the approved baseline in grants v4. If the BD asks for a live MCP demo, the honest answer is beta rollout. Confirm MCP status with dev before this goes out.</li>\n    <li><strong>Timing.</strong> This doc works standalone for the BD now. The grant application itself still forks on the routing timeline per grants v4. This alignment piece strengthens either Option A or Option B.</li>\n    <li><strong>The UI point.</strong> BD flagged UI and MCP section cleanup, dev delivery next week. Consider holding the send until the new UI is live so his first click after reading lands on the cleaned version.</li>\n  </ul>\n</section>\n\n<div class=\"footer\"><span>Sleuth \u2014 Internal until stripped</span><span>Polymarket RFB Alignment \u00b7 v1 \u00b7 July 2026</span></div>\n\n</div>\n</body>\n</html>\n" } style={{ width: "100%", minHeight: "100vh", border: "none", display: "block", background: "#060606" }} />
</div>
