IRS Chief Technology Officer — who sponsored the deployment
Parts of this entry are out of date. It is published anyway, because an incomplete record that invites correction is more useful than no record at all.
Chief Technology Officer of the Internal Revenue Service, and before that a senior technology executive at Boeing and EDS. One of the largest and most consequential technology estates in the United States government.
In 2013 he sponsored Resilient Network Systems for a nationwide rollout, and the relationship continued later with WebShield.
Each entry below carries its own provenance — the source, and how it was processed. That is the condition on which this graph can be extended by anyone without degrading.
The trail exists so that people who were there can reconstruct their own memories, recognize what they helped incubate, and add to or correct the record — or forward the few pages that belong to someone they know.
The corpus cites the IRS §6055 production deployment of 2014–16 — with Aetna, Experian Health and LexisNexis — as the proof of concept for the architecture: verification across organisational boundaries, in production, at national scale, in a compliance-critical setting.
Milholland is the reason it happened. A claim that something ran in production is considerably stronger when the person who sponsored it can be named.
The line from the December 2008 transition meeting to the IRS rollout is direct. The argument Jonathan Hare made to Reed Hundt's team — that verification across institutional boundaries, without disclosure, is the missing capability — is the same argument that was subsequently deployed at the IRS.
The financial regulators declined it; a tax authority ran it. Hare has email threads spanning both.
There is no single root. This is one view of the graph, from this node — what you see depends on where you enter and what you are looking for.
The trust network, and the intelligence years
Open →the same argument, five years earlierRegulatory Infrastructure for the 21st Century — presented while the meltdown was still happening
Open →Everything above is a distillation. The primary source is published in full, so that any claim on this page can be walked back to what was actually said — and where the two differ, the source governs.
This entry is deliberately incomplete. The gaps below are the things only certain people can settle — and settling one is a contribution like any other: recorded, timestamped and attributed to whoever made it.
Correct anything wrong, add what only you know, or claim this entry as your own. Write to evidence@qpncatalyst.io and Jonathan directly (both are on the button) — a timestamped confirmation comes back with your submission attached, as your own independent record. No account, no permission, no institutional standing required.
Public contributions earn Publicity Premium; bringing others who were there earns Cascade Premium. Everything is valued retrospectively as outcomes verify, so nothing has to be priced up front.
Correct this entry → Add a story, photo or link → Browse the graph →