The tax-oss manifestov2 · September 2026 · CC BY 4.0

Tax is public law. Its software should be too.

Four things we won't negotiate, what we stand against, and what we promise to anyone who builds or uses the open tax stack.

Every tax rule that applies to you was written down, debated, voted on and published. Anyone can read it. The code that applies that rule to your numbers is a different story: licensed per seat, priced per entity, closed to inspection, and owned by a handful of vendors who charge an annual uplift for the privilege of renting back your own expertise.

We think that is backwards. Not because vendors are villains, but because the rules of a public system deserve public code, and because the people who know tax best should own the tools that carry their judgement. A tax system runs on trust, and trust needs checking. The statute has been open to checking for centuries; the code that applies it is only now following. The corporate tax function is next. This page says what we stand for while we build it.

A countermovement against
per-seat licencesclosed rule enginesblack-box answersrenting back your own expertisethe annual uplift
I.

Law is already open.

The statute is public. The directive is public. The rulings, the guidance, the treaty texts: public. The only closed part of the chain is the software that turns them into a number on a return. That is an accident of history, not a requirement of the work.

When the code that applies a rule can be read, it can be checked against the article it claims to implement. When it cannot, you are trusting a vendor's reading of the law, and paying for the trust.

Anyone can read the statute. The code that applies it deserves the same scrutiny.

II.

Rules, reviewed in public.

A rule written as code has a history. Every change is dated, attributed, and sits next to the reason for it. A threshold moves in the budget; the diff shows the line that moved, the test that proves it, and the person who signed it.

This is how software has been reviewed for decades. It is also, not by coincidence, how a Tax Control Framework wants a tax position to be reviewed. Open rules give a tax function the audit trail it is already required to keep, for free, at the source.

Every rule traceable to its source. Every change visible, dated and attributable.

III.

Advisors own their tools.

A tax adviser's expertise is the product. The tool that packages it, whether a spreadsheet, a rule engine or an agent skill, should compound in the adviser's hands, not accrue to a licence holder. If you wrote the reverse-charge check, you should be able to read it, change it, run it anywhere, and give it to a colleague without asking permission.

Open source is the only licensing model under which that is simply true. Everything else is a lease.

Your expertise should compound in your hands, not be rented back to you per seat.

IV.

Agents with receipts.

Agents will do more of the work: research, extraction, reconciliation, monitoring, drafting. We welcome that, on one condition. Every answer cites the statute, the ruling or the dataset it rests on, and every action is logged so a person can retrace it. No citation, no answer.

And the person stays. No agent selects a material tax position, settles an audit or signs a return. Autonomy is for the bounded, reversible work. Accountability is for humans, with names.

Every AI answer cites the statute, the case or the dataset behind it. No citation, no answer.

In practice

What we promise

  1. Every entry in the index has an open licence, a public repository or dataset, and a clear use in tax work. That is the whole bar, and we hold it.
  2. We say where the shelves are empty. A gap on the map is information, not embarrassment.
  3. We name no vendor and disparage none. The argument is with the model, not with the people who work under it.
  4. Every tax statement on this site cites its article. Every learning lesson uses a real project and real statute. Nothing here is tax advice.
  5. We index what exists, whoever wrote it. If a vendor opens its code, it goes on the shelf like everyone else's.
  6. This site is itself open: the code, the data, the lessons. Fork it. Correct us in public.
Of you

What we ask

  1. If you know a project that belongs on the shelf, submit it. If you maintain one, keep it maintained.
  2. If you are a fiscalist, write one skill. One bounded task, your sources, your stopping rule. It is the shortest path from your expertise to something that runs.
  3. Before you accept an AI answer about tax, ask for the citation, the log and the benchmark. Then read the article yourself.
Sign the manifesto

Put your name under it.

Signatures are published with name and affiliation, nothing else, and only after you confirm by email. Your email is never shown.

Read how we handle your name and email in our privacy notice.

Set in Instrument Serif and Geist. Print it. Pin it above the desk.v2 · September 2026 · Propose a change on GitHub