A signed mark on every merged PR: CI state, non-author review, which harness wrote it, supervision minutes — and, where zavet is present, the intent it implemented.
Install the GitHub AppGold is stamped 585, 750 or 999 for how much of it is really gold. Fineness is how much of your change is really evidenced. Tap a rung.
Install in five minutes, see "your hallmarks assay at 585", and the ladder above you is the roadmap.
Opt-in, per repo or org-wide. Every position is a position — none of them is the product.
A neutral check appears on every PR. Grades are recorded, the posture view fills up, and absolutely nothing about your workflow changes. Zero risk — this is where every org starts and where many happily stay.
The check now reports pass or fail against the assay policy your org declared — "750+, non-author review, guards clean." Whether that check is required is your branch-protection setting. GitHub enforces; proba only reports.
Proba manages branch-protection rulesets centrally across the org — the real enterprise pain nobody solves by hand on 400 repos. The only dial position with critical-path risk, which is exactly why it is a position and not the default.
Proba certifies provenance and process — never quality. The moment a mark implies "this code is good", it becomes an opinion, and the whole chain stops being checkable.
Public repos never pay. Private repos pay for the dial position they actually use.
Next — miara →Proba mints a signed, immutable record for each merged PR: who wrote it, which harness, whether a qualified human actually supervised it, and whether your own declared bar was met. It never scores your code.
Proba certifies provenance and process — never quality. It records that CI was green, that a non-author human reviewed, how many engaged supervision-minutes were spent, that guards were respected. It will never tell you a change is good.
Gold is stamped 585, 750 or 999 for how much of it is really gold. Fineness is how much of your change is really evidenced — and it rises as you install more of the suite.
Opt-in, per repo or org-wide. Every position is a position — none of them is the product. Move right when you're ready, never because we shipped an update.
A neutral check appears on every PR. Grades are recorded, the posture view fills up, and absolutely nothing about your workflow changes. Zero risk — this is where every org starts and where many happily stay.
The check now reports pass or fail against the assay policy your org declared — "750+, non-author review, guards clean." Whether that check is required is your branch-protection setting. GitHub enforces; proba only reports.
Proba manages branch-protection rulesets centrally across the org — the real enterprise pain nobody solves by hand on 400 repos. The only dial position with critical-path risk, which is exactly why it is a position and not the default.
Overrides are never prevented — they become evidence. Who overrode, when, and the stated reason all land inside the hallmark, permanently. A team that ships at 3am gets to ship at 3am; the record simply says so.
Proba has exactly three screens. If a fourth ever appears, something has gone wrong with the product.
One per merged change, shareable by link. The proof object — what you send to a customer, an auditor, or a sceptical VP.
Fineness distribution over time for a repo or the whole org — plus the changes that were never assayed at all.
Where you declare the bar — minimum fineness, review rules, guard requirements — and where the dial lives.
The Act asks for oversight that is real and a quality system that records it. Nobody argues with that; the problem is that the evidence lives in five places and expires. A hallmark collapses it into one signed artifact per merged change — minted at merge, never edited afterwards.
What a hallmark will never say is compliant. No product can certify you against the AI Act, and any dashboard printing that word is selling you an opinion dressed as a record. Proba states what was observed, at a declared fineness, and leaves the conclusion to the person whose signature is on it.
The full article-by-article mapping →Public repos never pay. Private repos pay for the dial position they actually use.
Install the GitHub App, ship nothing differently, and see what your merged code assays at.
Install free →