Ironbark
Sign in Open an account
Module map

What is built, and what comes next.

Thirty-three screens across five surfaces, running on eight engine files. This page is the honest account of which parts are working logic, which are represented, and what a production build adds underneath.

33screens, all open and all reachable
—product rules, none hardcoded into a screen
—production columns across three categories
—self-tests running on every page load
Where the work is

The engines

Screens are thin. Everything that would be hard to get right in production is in these files, and it is finished. A production build keeps them and puts a database, an API and authentication underneath.

Module by module

Every row below names what is real logic and what is represented — a representation is an interaction designed properly with nothing behind it, which is exactly what a scope conversation needs.

What a production build adds

Deliberately not built