note
A Confidence Level Is Not a Latency Measurement
Reader question: does the September 2026 FOMC projections item say anything about how long a system takes to decide? It reports projected levels of GDP, unemployment, and inflation, not timing, so decision speed stays unaddressed. I filed this as a DEFER: near-zero reliability, because the source cannot test the question rather than disprove it.
What the projections item actually covers
Reader question: does the September 2026 FOMC projections item say anything about how long a system takes to decide, or only about projected levels? The item the Federal Reserve published for release at 2:00 p.m. EDT on September 16, 2026, is a Summary of Economic Projections: participants submitted their most likely outcomes for real GDP growth, the unemployment rate, and inflation from 2026 through 2029 and over the longer run, based on information available at the meeting plus their assumptions about appropriate policy. Its tables report median, central-tendency, and range values for those variables. Nothing in the supplied text is a timing or latency measurement, so the reader's original question — how fast a system decides — is simply not addressed by this artifact.
I recorded my own view as a deferral with essentially no reliability, and I want to be explicit that this is not a disguised verdict. The honest status is 'untested,' not 'false': a page about projected levels cannot confirm or refute a claim about decision speed, so I hold no belief either way rather than dressing up silence as evidence. Separating what a source reports from what it cannot speak to is the same discipline the checklist article on this site applies to return charts — an unfilled field admits every outcome, so it falsifies nothing.
The mechanism, and what would change my view
Supported quote: the participants' projections were 'based on information available at the time of the meeting.' That phrase scopes the inputs to a meeting window; it does not timestamp how long any participant or system took to reach a decision within it. Interpretation: a projections table measures levels, so it is testimony about intended outcomes, not about process speed — the two are different axes, and reading one as the other would be the category error behind treating forecast accuracy as trading profit.
Hypothetical: naming one latency value plus its falsifier would make the timing question checkable — for example, a stated median decision interval of, say, X minutes, falsified if an independent trace showed a materially different distribution across the same meeting. Until a source supplies that kind of value, the reliable move is to leave the belief deferred and say so, rather than upgrading my confidence to match the official presentation. Not investment advice.