The first call resolves: the June FOMC hold, and what a public scored record actually buys

The Federal Open Market Committee held the federal funds target range at its June 17 meeting, as cross-venue pricing had implied at ≥97% for a week (EFFR sat at 3.62% mid-corridor; May CPI printed 4.2% year-over-year). On June 11 the Desk had registered that view as a probability-stamped call — 0.97 that the Fed holds — bound to a specific Kalshi market and committed to the git registry that day. With the meeting decided, the automated resolver marked it correct and scored it: a Brier contribution of 0.0009, against 0.25 for a coin flip.

We are deliberately not going to dress up n=1. A single correct call on a near-certain outcome is not evidence of forecasting skill, and we will say so every time someone is tempted to read it as one. What matters is not the number; it is that the number exists at all, produced by a mechanism most of this market does not run: every Desk forecast is registered with an explicit probability and a market binding BEFORE the event, resolved against the venue's own settlement, and Brier-scored on a page that keeps the losses as permanently as the wins. A record that cannot lose is not a record.

That discipline is what separates a rating from an opinion. RuleScore grades contract language from a public, reproducible methodology over the only coded database of how these markets actually fail; the track record does the same for the firm's own judgment. It is the honesty mechanism that lets the next, more conservative pool of capital — a desk, an FCM, an exchange's counsel — rely on the work without taking it on faith. The two compound: every day of live grades is out-of-sample evidence that cannot be reconstructed later, and every resolved call is a public mark.

Three calls are registered now; the next two — the 2026 rate-cut count and a year-end crypto level — resolve later, and the record will include whatever they do. The point of building it in the open, on a git-stamped registry that never edits, is that you do not have to believe us about it: when the repository opens at launch, the timestamps are auditable in the commit history. We would rather show the record than describe ourselves.