Fed FRB/US, rebuilt

FRB/US

Traces how a US funds-rate or fiscal shock moves output, unemployment and inflation, quarter by quarter.

Solver matches Fed code; one economic check passes. Evidence Solver: matches the Fed’s pyfrbus on a 100bp funds-rate shock. Economics: only the 100bp responses pass (within 10% of the Board’s run, on its 2020Q1 design); the rest are partial to failing. The baseline is the Board’s by construction and misses GDP growth and core PCE in 2026Q3.

Good for

  • Monetary and fiscal shocks through the Board’s own equations
  • Quarterly paths against the Board’s October 2026 baseline
  • Wage and hours paths for the incidence bridge (experimental)

Not for

  • PolicyEngine reforms: score_reform refuses it (limits)
  • Forward guidance: no model-consistent expectations in the hosted tools
  • Anything about the UK: OBR emulator

A worked example

The Fed raises the funds rate by one percentage point for one quarter (2026Q3, the first projected quarter of the October 2026 LONGBASE), under the default inertial Taylor rule.

Real GDP, trough−0.55%2028Q2 (quarter 8)
Output gap, trough−0.50pp2028Q1 (quarter 7)
Unemployment, peak+0.28pp2028Q3 (quarter 9)
Core PCE inflation, trough−0.034pp2028Q2 (quarter 8)

How far to trust it

Three checks, weakest included; each opens its evidence.

Trust the solver, not the economics. The match shows the Board’s equations are solved correctly, not that they are right (all limits).

Full scorecard and limits

Run it

The worked example above, three ways: a 100bp funds-rate tightening for one quarter.

In FRB/US, raise the federal funds rate by 100bp for one quarter from 2026Q3 under the inertial Taylor rule, and show real GDP, unemployment and core PCE inflation each quarter.The hosted server calls frbus_shock; no install. Connect

pe-macro frbus-shock --var rffintay_aerr --shock 1.0 --start 2026Q3
from frbus import Frbus, load_data
start, end = pd.Period("2026Q3"), pd.Period("2031Q2")
# load LONGBASE, set the demo fiscal switches, init_trac: see /frb-us/code#code-5
with_adds.loc[start, "rffintay_aerr"] += 1
sim = model.solve(start, end, with_adds)

Setup, every lever and output

With the microsimulation

Its labour-market path tells the microsimulation who bears a shock.

FRB/USwages · hours PolicyEngine microsimulationUS employment income Who bears it

frbus_shock_incidence scales US employment income with the wage and hours deviations, so federal and state taxes, SNAP and the EITC show who bears it (every join in the suite).

Uniform scaling is an experimental illustration. Real incidence concentrates in job losers.

Model cardinputs, outputs, horizon, data, access
Answers
How US output, unemployment, inflation and the funds rate respond to a monetary or fiscal shock
Inputs
One reviewed add-factor shock: a lever, a size and a policy rule
Outputs
GDP, unemployment, inflation, prices, federal funds rate
Horizon
Quarterly paths, read as deviations from the Board’s baseline
Data
The Board’s model.xml and October 2026 LONGBASE
Uncertainty
Not comprehensive: the hosted shock returns one deterministic path
Access
Hosted raw shocks, CLI, Python package (Code)
Runtime
About 3 seconds cold; under a second warm
Joins the microsimulation
Wage and hours paths scale US employment income (the join above, experimental)
Status
Replicates the Fed's pyfrbus (1.0.0 and 1.1.1) on one 100bp funds-rate shock, within a 1e-6 tolerance; a solver check, not a test of the economics
Cannot answer
PolicyEngine reforms; model-consistent expectations, so no forward guidance; anything about the UK