The registry
Software with human intention protected.
Every project here has put its IZ4 on the record: what it is for, who it is for, and the invariants that must stay true for them, on top of the foundation. Newest first. It is a list of declarations, never a ranking and never a score.
On the record
No card is public yet. Put yours on the record and it appears here.
A card reports declarations and recorded checks for one exact revision. Being listed means a publisher put an IZ4 on the record. It is not a certification, not a safety claim and not a score. What an IZ4 is.
Why put yours on the record?
Your IZ4 already says what your software is for. The register puts that on the record: dated, in your name, where the people it serves can see it.
The core invariants of all your software
One place for every project you look after: what each is for, who it’s for, and the invariants you choose to publish.
One URL, one answer
What your IZ4 declares, what was checked, and how current that is. Send the link and skip the meeting.
Evidence that stays put
Every result is tied to its exact revision. An old run can never pose as a fresh one.
A badge that stays honest
A live status badge for your README and a QR badge for your packaging. Both lead to the card, and both tell the truth.
See drift as it happens
A digest change, a coverage move, a check that flips. Named plainly, never blurred into a score.
Your repo stays home
Your CI sends counts and outcomes. We never open a private repo or read a private IZ4.
Your release stays yours
Every check is advisory, so you decide what ships and when. Nobody grades you.
The register proves you said it, when, and that it is still there. It does not prove the software is safe.