Adverse Action Notice Compliance
Builds a denial notice from the ranked scoring factors, then checks it against Regulation B completeness rules and the prohibited vague-code list.
AINumbers Helm · guided walkthrough
See a workflow, then verify its evidence
This page is a fixed guided walkthrough of what Helm produces. Everything on it was baked in when the page was published, so it works with no download, no account, and no network connection after the page loads. Read a compiled workflow, then check a real signed evidence bundle and the tampered copy of it, using the same verifier Helm puts inside every export.
Read only01 · What a compiled workflow looks like
Inputs, pinned steps, signed evidence
A Helm workflow is compiled before it runs. Compiling pins each step to an exact kernel and its digest, so the thing that runs later is the thing that was reviewed. Below is one shipped workflow, printed exactly as it is stored. Nothing runs on this page.
Compiled workflow
Adverse Action Notice Compliance
workflow manifest digest sha256:58f26bc331fc6b3817e019089cd888bba9cbd45f233a5a07488c89e91cdeb8b7
-
Step 1art-228-build-adverse-action-noticepinned kernel digest
sha256:f6fa0d528022c256b20f095c3a94e08923c4338008aba9689e96eea2395612ad -
Step 2art-227-validate-adverse-action-noticepinned kernel digest
sha256:68a2b118857650ebe9fb5729f49dad91a524e942c1634d0ac6b6e7997dd2a667
InputsThe application decision, the scoring factors behind it, and who is asking. Entered on your own machine.
RunEach step runs locally against its pinned kernel. Every input, output, and running hash lands in an append-only journal.
EvidenceThe run exports as a signed bundle. That bundle is what section 02 verifies.
02 · Verify a bundle, right here
The same check an auditor would run
Two evidence bundles are baked into this page: a real signed one, and a copy of it with a single byte changed. Both are checked by the identical verifier script Helm embeds in every exported bundle, so what you see is not a simulation of the result. There is no upload here and nothing to pick: the fixtures are part of the page.
Pick a fixture
Verifying.
- Checked here
- Every object's signature envelope. Every entry's digest, kind, and trust label against the signed manifest. That no secret-shaped field survived into the export. That each checkpoint's running hash is self consistent, and that any timestamp anchor is bound to the checkpoint it claims to cover.
- Not checked here
- Whether the underlying real world event was true. A timestamp authority's certificate chain back to a root. Whether this matches a live journal, since this page has no engine behind it.
03 · A sample of the library
Workflows that ship compiled
219 workflows ship compiled with Helm, each pinned to kernel digests the same way section 01 shows. Six of them are printed here. This is a fixed sample baked into the page, not a live index.
AI Decision Log Conformance
Classifies a system against the EU AI Act, then tests whether its decision logging meets the Article 12 record-keeping duty.
Agent Audit Trail Conformance
Produces an Article 12 conformant decision record for an automated agent and checks the trail it leaves behind.
Anchored Extract Verification
Checks that an extract really belongs to the dataset it claims, by testing its Merkle inclusion against an externally anchored root.
AI Vendor Onboarding Packet
Risk-classifies an AI vendor, pulls the matching contractual clauses, and assembles the onboarding packet.
Agent Identity Verification (RFC 9421 Web Bot Auth)
Checks an agent's published identity credentials before anything downstream is allowed to trust them.
04 · Look first, install second
Two ways in, and one of them needs nothing
This walkthrough is fixed and read only. It walks a compiled workflow and verifies a real signed evidence bundle in your own tab, using the same verifier Helm puts inside every export. Nothing is downloaded, nothing is uploaded, and there is no account. It is the fastest way to see what the evidence actually looks like before you commit anything.
Doing the work takes the engine. Install helmd and it serves the full Helm interface to your browser from 127.0.0.1 on your own machine. Choosing a pack, connecting a service, running it, reviewing the journal, and exporting a bundle are shipped screens. Both run in your browser. The difference is whether the local engine is there.
05 · Run it for real
Install the engine
This walkthrough is fixed. To run your own workflows, connect your own systems, keep a durable journal, and export your own evidence bundles, you install the engine. It is a single file called helmd. It runs on your machine and serves the full Helm interface to this same browser from 127.0.0.1, so nothing you work on leaves the machine.
Get the engine
Download helmd for your platform and read the setup steps. Both live on the Helm page.
Install helmdAlready running it
If helmd is already listening on your machine, open its interface directly.
Open Helm on 127.0.0.1This is an ordinary link. This page never probes your machine to find out whether the engine is there, so the link is shown to everyone and simply fails to load if nothing is listening.
06 · If we are ever not around to ask
Your evidence outlives the vendor, by construction
The bundle you just checked above carried its own verifier inside itself and ran every check from that one file, with no server in the loop. That is what happens for any bundle you export from your own journal too. It is not a commitment about how long we will be around to honor; it is a property of how the file is built. A bundle you already hold stays checkable by anyone, on any machine, with nothing installed and no account to sign into, whether or not the people who built Helm are still reachable.
The journal it comes from lives on your machine, as files on your own disk, not in a cloud we operate. There is no license check that phones out and no step in verification that depends on us continuing to run anything.