[MaxGhenis]

Since we deployed PolicyEngine/cliff-watch#47 on November 8, CliffWatch has taken the household's county from its ZIP code. slideshows/appam-2026/EVIDENCE.md line 202 and SPEAKER-NOTES.md line 198 still said CliffWatch passes PolicyEngine US the state and no county, so the model computes premium tax credits from Barnstable County's benchmark plan. Both lines now date that behavior to the November 4 capture behind slide 11 and say what changed. No other line in the repository names Barnstable.

The notes now answer "Yes, by county". PolicyEngine US 1.755.5, which CliffWatch runs, picks the premium tax credit's rating area by county and gives Middlesex County area 3. CMS lists Massachusetts's rating areas by three-digit ZIP code and puts Cambridge's 021 in area 5. On November 9, we merged PolicyEngine/policyengine-us#10682, which moves Middlesex County to area 5 from 2026. CliffWatch still runs 1.755.5, so it computes this household's premium tax credits from area 3's benchmark plan.

Slide 11's CliffWatch link, for ZIP code 02139, now opens a chart for Middlesex County. At 21:44Z on November 8, the live page printed "Middlesex County, Massachusetts · 1 adult · 2 dependents" and "refined to $100/year around 4 cliff zones". Its cliff report put the four drops at $18,250, $37,750, $42,500 and $83,375 of earnings, and the screenshot marks the first three. CliffWatch's /api/metadata still reports PolicyEngine US 1.755.5, so the ledger's first sentence, which names that version, stands.

The slide, its screenshot, its links and its alt text stay as they are.

At a326a78, bun run test passes all 447 tests in 13 files.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
policyengine-slides	Ready	Preview	Nov 9, 2026 5:00pm UTC

[MaxGhenis]

Max approved these two lines, and we merged a326a78 as 4131837. At a326a78, gh pr checks exited 0 with all five checks passing, and the PR read MERGEABLE, CLEAN and ready for review, with no review asking for changes. With no Subfleet lane open, an independent Opus 5.5 reviewer read e673f79 and asked for three changes. "Yes" claimed more than CliffWatch does, "slide 11's link" didn't say which of the slide's two links, and the ledger's "now opens" gave no date for its reading. Commit a326a78 makes all three. The same reviewer approved it, and we took its two suggestions for this description. At 17:07Z on November 9, slide 11's CliffWatch link still opened a chart for Middlesex County with four cliff zones, at the same four drops as on November 8. CliffWatch's /api/metadata still reported PolicyEngine US 1.755.5. On main at 4131837, Lint, Tests and Build passed, and Vercel finished deploying it to production.