iz4™ · the register

Why register an IZ4?

Your IZ4 already says what your software is for, and that people come first. Registering it puts that on the record, dated, in your name, where the people it serves can see it.

For maintainers

One URL answers the question

What it declares, what was checked, how current. Send a link, skip the meeting.

Evidence that stays put

Every result is tied to its revision. Old runs cannot pose as fresh.

The IZ4 badge

A licensed QR mark for your README or packaging. It leads to the live card.

For teams and CTOs

Switch AI tools, keep your intent

An IZ4 is plain text any model can read. Change assistant, model or vendor and the file stays exactly as it was.

Your repo stays home

Your CI sends counts and outcomes. We never access a private repo or its IZ4.

See your dependencies

"18 of 30 direct dependencies declare an IZ4", with changes flagged as they move.

See drift as it happens

A digest change, a coverage move, a check that flips. Named plainly, never blurred into a score.

Certification a private repo can carry

The IZ4 badge certifies a valid IZ4 exists. The file never leaves your machines.

One answer across the estate

Every repo registered means "what is this supposed to do" has one answer, for humans and agents.

Invariant Zero™ is good for everyone

Software in service of human thriving ships with every IZ4. You do not build that part. You inherit it, and the register puts it on the record. It turns out to be good business too.

Procurement gets shorter

Buyers ask how your software treats people. Answer with a link, not a PDF.

Agents get a rule they cannot argue with

They read it first, and it settles trade-offs in favour of people. Software and AI working together, for the people on the other side of the screen.

Trust where the decision is made

The card and the badge carry the commitment into your README and your sales deck.

Teams decide faster

A written top priority ends the argument.

Ask your supply chain the same question

Coverage shows which dependencies carry it, and which do not.

The record outlasts the quarter

Dated and append-only. Corrections supersede, nothing is rewritten.

The register proves you said it, when, and that it is still there. It does not prove the software is safe, and we will never say it does. What Invariant Zero says, and why.

What the register will not do

Block your release. Every check is advisory.
Grade you. There is never a quality score.
Access a private repo or divulge a private IZ4, ever. A public repo may be checked only to confirm its declared IZ4 is valid.