Skip to content

BLS deck: why we built the emulator, funding, versions and releases, Axiom, What's next - #74

Merged
MaxGhenis merged 18 commits into
mainfrom
bls-max-close
Oct 9, 2026
Merged

MaxGhenis merged 18 commits into
mainfrom
bls-max-close

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

Max's two items from yesterday's prep meetings (the motivation slide and the forward-looking close), plus Thesia Garner's question list (email of October 7) worked into the deck. Max asked for the answers to go where each one fits rather than on a slide of their own.

What changes

  • New slide 7, "Why we built a TAXSIM emulator" (1 min, Max). The hero is BEA running PolicyEngine for 2021 onward. The cards: microsimulation first (launched 2021); state taxes and TAXSIM35 validation both starting in April 2022 (#715, #704), with all states by April 2024; NBER's successor line from taxsim.nber.org; and one model serving both uses. The notes carry the spoken setup and what not to say: BEA's "discontinued" footnote, the "fully compatible" line, and anything about Dan Feenberg's plans.
  • PolicyEngine today (slide 5) gains a funding strip (the PSL Foundation as fiscal sponsor, plus the funders on the public supporters page). Recounted today: 4,932 YAML test files (the slide said 4,693) and 136 contributors (it said 133). The notes answer the funding and staffing questions.
  • New slide 13, "Versions and releases" (2 min), in the emulator section before the demo:
    • 286 PolicyEngine US releases and 15 emulator releases in the last 90 days.
    • Every release computes every tax year.
    • The pin command uv tool install policyengine-taxsim==3.0.1 --with policyengine-us==2.25.2 resolves (checked with uv pip compile).
    • Changelog typing, support on the public tracker (median first reply to NBER's reports: 23.5 h), and the 3.0.0 S-corporation default change.
    • The notes answer the release-schedule, version-notes, tax-law-change-list, input/output-change and support questions, with the honest caveats: the output has no version stamp, PyPI holds PolicyEngine US only from May 2026 onward, and the documentation's pin example (1.555.0) is no longer on PyPI.
  • Section 05 is now "What's next": the 2026 rules (moved up), then new slide 29, "Axiom: our next-generation rules engine" (2 min), then the CE pilot. The Axiom slide has three stages:
    • Today: PolicyEngine US powers the emulator.
    • Planned: Axiom on the backend, with PolicyEngine wrappers.
    • Throughout: backwards compatible, and we keep powering TAXSIM as long as it is needed.
    • Its footnote states the boundary: Axiom does not yet compute a complete federal return (rulespec-us #1318).
  • Notes on existing slides now carry the matching answers: in-kind valuation (NSLP, WIC, Medicaid) on slide 25, testing on slide 16, the annual update on slide 28, and the open-source logic on slide 4. The agenda notes map every question to its slide.
  • Timing stays at 60 minutes plus 30 of Q&A. Added: why-emulator 1, releases 2, axiom-plan 2, and a 2-minute Axiom walk-through still to come in a follow-up commit. Trimmed: what-is-pe 3→2, nber 3→2, demo 13→10, imputation 3→2, ce-pilot 3→2.

Every figure was checked this morning against PyPI, the GitHub API, the policyengine-us and rulespec-us trees, taxsim.nber.org, the BEA technical document and policyengine.org. An adversarial pass removed one claim: the Axiom-vs-TAXSIM federal run on 87,519 tax units, which compares Axiom with a 2026 TAXSIM test build rather than with the emulator.

🤖 Generated with Claude Code

MaxGhenis and others added 2 commits October 8, 2026 11:04
…se them yet)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lan, What's next section

Adds the motivation slide (why PolicyEngine built a TAXSIM emulator), a funding
strip and recounted test files and contributors on PolicyEngine today, a
Versions and releases slide, and an Axiom transition-plan slide. Section 05
becomes What's next: the 2026 rules, Axiom, then the CE pilot. Thesia Garner's
question list is answered in the notes of the slides that cover each question.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
policyengine-slides Ready Ready Preview Oct 8, 2026 5:45pm UTC

Request Review

Releases: several merges can share one release; CI checks changelog entries
but does not block merges; the pin example needs Python 3.11; PyPI does not
keep every PolicyEngine US release. Motivation: the October 2021 launch was
PolicyEngine UK, the April 2024 all-states launch was a beta, and the
successor quote is attributed to Dan Feenberg's TAXSIM page. Contributors stay
at 133 (the API's 136 includes three bots). The #1248 note is updated: NBER
closed it on September 29. Axiom slide cites the shipped Belgium pilot of
policyengine.py on Axiom.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds slide 30, the federal child and dependent care credit (26 USC 21) running
live in Axiom, with the household, the arithmetic, the preview caveats and
fallbacks in the notes. SPEAKER-NOTES.md, VALIDATION-SCRIPT.md and README.md
now follow the 34-slide order, timings and components, and the checklist adds
warming the web runner and rehearsing the Axiom run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… Axiom demo title

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…in its own tab

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…creens

At 1280x720 the releases cards and the funding strip ran under the footer.
Same approach as DropInTabs: CSS zoom below 820px and 740px of height.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 2021 expansion sits behind an input flag and 2022-2025 law is not encoded;
EITC and the other sections do not run live yet (the error varies); the first
API call can take about 5 seconds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er, review fixes

Order now follows the speakers: Max (01 introduction), Pavel (02 emulator and
demo, 03 beyond TAXSIM), David (04 validation, now ending on the 2026 rules
slide he built), Max (05 benefit imputation, a new section, and 06 what's
next). Each section divider names its presenter. Agenda, notes, README,
SPEAKER-NOTES and VALIDATION-SCRIPT follow the 35-slide order.

Review fixes: 'TAXSIM's author on a successor' replaces 'NBER names a
successor'; 'could run on Axiom'; the funding strip says grants to date with
NSF POSE Phase I dated 2025-26; the pin note says to archive the environment;
'about 1 day' median reply; open-source AI skills; 9 states and DC for heating
assistance; deck description no longer CE-only. Layout: short-screen zoom for
the Axiom plan and the validation triangle, the 2026 timeline's change panels
hide below 960px of height (their content is in the notes), and the cover
title clears the logo at 720px.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Notes follow the new order (benefit imputation covers missing data; the demo
leads into Beyond TAXSIM); the 2026 timeline notes carry the change panels
hidden on short screens; 'Funders to date' on the funding strip; checklist and
section-comment fixes. The ce-pilot intro line was removed earlier on purpose:
the four numbered steps already say it, and it freed room at 720px.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis and others added 2 commits October 8, 2026 13:06
… axiom.org

Slide 7 drops the BEA hero, which read as the motivation; the cards now go
microsimulation first, state taxes needed a benchmark, TAXSIM's author on a
successor, one model for both uses. The BEA fact moves to the slide 6 notes.
Slide 31 embeds axiom.org itself (the home page's rule graph), and the notes and
footnote give the path to 26 USC 21: Explore the law, search 'dependent care',
graph, Run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Max: listing NBER on 'PolicyEngine today' was odd, since NBER is the day's
topic, and the logos already sit on the next slide. The model's figures (95,000+
parameters, 6,000+ variables, 4,932 test files, 103 programs, 133 contributors)
move to slide 4, and slide 5 becomes 'Who uses and funds PolicyEngine', with a
funders row (Arnold Ventures, NSF, Nuffield, NEO Philanthropy, Pritzker
Children's Initiative; logos from policyengine-app-v2's supporters page). The
funding and staffing answers move into the notes of slides 5 and 4. Slide 4
gets the freed minute; the deck is 34 slides and still 60 plus 30 minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eld and NEO)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tivation

Two one-minute live slides after 'Who uses and funds PolicyEngine': the OBBBA
Household Explorer (57,240 records, 21 provisions each) and CliffWatch on a DC
household. They set up why every record's taxes must be right. Slide 4 and the
origins slide give up a minute each to keep 60 plus 30; slide numbers from 6 on
move up by two in the agenda notes, README, SPEAKER-NOTES and VALIDATION-SCRIPT.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis
MaxGhenis merged commit 5b14cbf into main Oct 9, 2026
5 checks passed
@MaxGhenis

Copy link
Copy Markdown
Contributor Author

Merged at reviewed head ef76850 after:

  • two-lens review (claims + build) at 577a845: approve with fixes, all applied;
  • delta review of the restructure at 8494e1a: approve, nits applied;
  • final independent review (Subfleet, standard tier) of 5793df8..ef76850: approve, conditional on tsc and eslint, both of which pass locally.

CI green (Build, Lint, Tests, Vercel). Deck as presented at BLS on 2026-10-08.

🤖 Generated with Claude Code

This branch was successfully deployed

1 active deployment
Preview – policyengine-slides — ef76850e Deployed Oct 8, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant