← Non·Xero·Sum

Tool Library

Working tools, shipped with every issue.

Each week, Bernard's Solved Game ships with a new working tool — built on a real open-source project, source printed in full, yours to run immediately. Tools accumulate, never replaced. This is the archive.

About the tools

Every tool in this library is:

  • Working code. The tool is functional and runnable the week it ships. No prototypes, no promises.
  • Source-complete. The full source is printed in the issue. Nothing hidden behind a login or a paywall beyond your subscription.
  • Open-source. Every tool is built on open-source projects, and the work itself is shared freely.
  • Tested in production. Before it ships in the newsletter, it's been tested against real data and real failure modes.
  • Mechanism-grounded. The tool exists to solve a specific problem in mechanism design, game theory, or AI systems. It's not a generic utility.

The archive

Tools will appear here as they ship with each issue. New issues drop every Wednesday.

Subscribe to the newsletter to get access to working tools as they're released. A new tool ships with every Pro and Founder issue.

How to use the tools

  1. Read the issue to understand what the tool does and why it matters.
  2. Copy the code from the published issue.
  3. Run it against your own data. The issue always includes a worked example you can follow.
  4. Modify it for your needs. The code is simple enough that most builders can adapt it in an afternoon.

What you get with each subscription tier

  • Free tier: The Tape and The Read. No access to The Tool.
  • Pro ($15/mo or $250/yr): Full access to every shipped tool, including the archive. You can run the worked examples and modify the code for your own use.
  • Founder ($300/yr): Everything in Pro, plus early access to Studio Genesis, and direct email access to Bernard for questions about the tools.

Maintenance and deprecation

Tools are permanent once shipped. If a tool is superseded by a newer version or a better approach, both versions stay in the archive with a note explaining the relationship. Tools are never deleted.

If a tool depends on an external service or library that breaks, the issue documenting the tool will be updated with a workaround or deprecation notice.