proof-of-work tooling

The tool that turned a folder of finished work into these pages, no client named

For our own tooling: the tool that turned a folder of finished work into these pages, no client named. A tool you point at a folder of projects or a GitHub account. We had done a lot of work and could point to almost none of it.

We built this one for ourselves: our own tooling. It earns its place here on the same evidence as any client project.

how do I show proof of my work when I cannot name the clients I did it for

A tool you point at a folder of projects or a GitHub account. Built and run out of Sarasota.

What was going wrong?

We had done a lot of work and could point to almost none of it. The client projects were under wraps, the internal builds sat in private repos, and writing them all up by hand would take days and still risk letting a client's name slip onto a public page. A portfolio you cannot show is the same as no portfolio at all.

What did we build?

A tool you point at a folder of projects or a GitHub account. It reads the real commit history of each one, you pick which to publish, and it turns each into a clean page in a fixed voice with the client's name stripped out and checked twice by two separate passes. Every page has to clear a gate of forty-six automated checks before it can be saved: one leaked name or one line of machine-written copy and the page is refused and never written to disk. Nothing publishes until a person says so. It made every other page in this portfolio.

What changed?

It produced every proof page here, and it blocks any page that would leak a client's name or read like AI before that page can be saved.

From our own build data.

How do we know this is real?

Build record: 6 tracked changes, 2,074 lines of working code. Every number here comes straight from the project's build history.