Theme
Integrity for the emergent assurance
Security review, audit, and evaluation all end in a claim someone is asked to trust. The Integrity Suite is the set of standards beneath those claims, where secure, sound, and verified are defined precisely enough that your own conclusions can be checked, not just asserted. This is the five faces combined for that kind of work; combined by industry instead, they are on the industries page.
The signature move
Most security work happens in the middle. Formal verification proves an implementation does what its specification says; cryptographic verification and oracle networks carry a result onward intact. Every one of them takes two things as given: what the spec and the inputs actually were going in, and what the output owes going out. Those two ends are where the costliest failures actually live, and they are exactly where the Integrity Suite works.
In front, on what the work assumes: CRAFT makes the specification legible, ORE grades the sources feeding in, and CROSS’s entry gate fixes what a grant must declare before a dollar moves. Behind, on what the work emits: STRUCK states what an output owes the person who acts on it, and CROSS’s completion gate checks what was actually delivered. A proof against a flawed spec is the failure in front, faithfully verified and faithfully wrong. An output trusted because it never had to carry its own uncertainty is the failure behind.
The move is the same at whatever scale you point it. Around a whole evaluation chain, ORE in front and STRUCK behind. Around a single grant round, entry gate to completion gate. Around one judgment call, CRAFT sets the terms before anyone decides and holds the verdict to them after. Around one field on a form, WALKRI defines it before anyone answers and requires the data to leave carrying its own provenance. Same shape at the scale of the pipeline and at the scale of one measurement inside it.
One face holds the middle instead of the edges. Structure, the set of conditions a system has to keep under load while the work runs; something has to hold the center while everything else guards the two ends. The Suite does not replace the work in the middle. It owns the two places that work was never able to check on its own: what went in, and what came out.
Where it applies
A security review ends in a verdict: sound, or not. But the verdict is only as good as what sound was taken to mean and the reasoning that reached it, and most of that stays in the reviewer's head. The Suite makes the review's own chain legible, what was covered, what secure required, and how each finding became the conclusion, so the audit is something a client, a counterparty, or a skeptic can check rather than accept.
Every funding decision rests on a word like additional, impactful, or promising, and on a comparison between projects that rarely gets written down. Ask why one project won and another lost, and the honest answer is usually a story. The Suite turns the criteria into something declared in advance and the decision into something comparable and defensible, so a round can show its reasoning instead of asking to be trusted.
A model is called safe, an output verified, a result state of the art. Each is a measurement, and a measurement is only as sound as the definition under it and the chain that produced it. The Suite pins the terms and makes the evaluation chain legible end to end, so a score becomes a claim that can be checked rather than a number taken on faith.
The standards are free and open. Start with the specifications, or see how they hold up on the web3 frontier where the claims move fastest.