[–] dang 11 hours ago
[–] RGS1811 11 hours ago
[–] darksim905 1 day ago
[–] timcobb 1 day ago
[–] RGS1811 1 day ago
In more detail:
- every line of every form gets a YAML representation which includes the source text, a data type, and an expression built from a small set of lean atoms, plus a citation pointing to the exact location of the rule in the original official document.
- underneath the yaml layer there's a lean formalization of the atoms showing that they behave as specified, that all comuptations use only the allowed atoms and operations, etc. There's also a typescript evaluator that's used to cross check the lean for agreement, so we have the arithmetic represented two ways.
The critical failure point for an LLM-produced formalization like this is the interpretation of the form text. Since I'm not a tax lawyer and don't intend to become one, this is an explicitly owned weakness and one I've structured the project around. Publicly available tax calculators (PolicyEngine, UsTaxes, OpenTaxSolver, etc.) are used to cross check derived numbers from this system. Mutation testing ensures the test suite is robust against bugs and arithmetic errors. Interpretations are cross checked by different model families (Claude, GPT, Deepseek). Etc.
The idea is to derive confidence from the formal properties of the system itself, and to allow theoretical future users of such a system to derive confidence in the interpretation of specific forms by making it easy to cross check line-level formalizations against the source documents.
There's a lot more detail in the (alas, Claude-authored) README. When I have time I'm going to write my own version of the README expressing my vision of the project, but I'm not there yet.
[–] celestialcheese 1 day ago
[–] dang 11 hours ago
IRS Direct File - https://news.ycombinator.com/item?id=44131901 - May 2025 (65 comments)
[–] timcobb 15 hours ago
[–] vatsachak 1 day ago
[–] RGS1811 1 day ago
[–] amelius 1 day ago
[–] RGS1811 1 day ago
And to be clear: my vision here isn't "have an agent do your taxes", it's to have agents build a hardened and thoroughly verified deterministic tool that can help you navigate the (somewhat bewildering) forms and instructions decision tree when filing your own taxes.
[–] singhrac 1 day ago
[–] ToucanLoucan 1 day ago
[–] ordersofmag 1 day ago
https://www.irs.gov/filing/where-to-file-paper-tax-returns-w...
[–] ToucanLoucan 17 hours ago
[–] ryandrake 1 day ago
[–] rbhelt 1 day ago
[–] ClikeX 1 day ago
[–] rbhelt 1 day ago
[–] what 1 day ago
Anyway, my point is that for 95% of people they have all the information already and you shouldn’t have to file.
[–] thenewnewguy 1 day ago
[–] NichoPaolucci 1 day ago
(If a painter knew that the camera was coming out I would not want them to throw their canvas away)
[–] ForHackernews 1 day ago
There's an article about it here https://biggo.com/news/202510160717_IRS-Fact-Graph-Public-Re...
These were artifacts from the IRS Direct File program (RIP)
Maybe your project could (re)productionize this dataset.
[–] RGS1811 16 hours ago
- It's oriented toward the IRS's internal XML API in a way that's not really useful for this project, since no consumer of my code is going to digitally submit to the IRS.
- The semantics of FactGraph are largely undefined, and the maintainers themselves seem to acknowledge that its development trajectory went off in a bad direction and it needs major divisions.
- It's super verbose.
- It's the year of Lean, so I wanted to find an excuse to use Lean.
Other work has been done in this domain, though. The biggest example is Catala[0], though Prof. Sarah Lawsky at Northwestern seems to have made some strides toward formalizing the Internal Revenue Code.
(Posting here since we don't have another way to contact you, and of course that thread will be better with you in it...)