A local control plane you can replay
Helm runs automation on your own machine, keeps an append-only journal of every step, and re-computes the work to prove it happened the way the record says. The result is evidence a regulator or auditor can check without trusting us, and without a network connection.
Phase 1 in buildFive clicks, no command line
Everything below is a button or a switch. No terminal required.
Download Helm for your OS
Pick your platform. Each button downloads a single file, the helmd binary. There is nothing else to install.
Links point at the v0.1.0 pre-release. The repository is private during the Phase 1 build, so they go live the moment it opens. Not sure which Mac you have? Apple menu, then About This Mac: an Apple M-series chip is Apple Silicon, an Intel chip is Intel.
Run the file you downloaded
On Windows, double-click the .exe. SmartScreen may warn because the pre-release build is not yet code-signed: click "More info" then "Run anyway". On macOS or Linux, mark it runnable first with chmod +x helmd-macos-arm64, and on macOS right-click the file and choose Open the first time so Gatekeeper lets it through.
Your browser opens Helm, already connected
helmd starts on your machine and opens a paired browser tab automatically. No token to type in.
Click Connect, approve the service
The consent screen shows exactly which service and which scope you are authorizing. No blanket permissions.
Run a workflow, then click Verify
Verify checks the evidence bundle's signatures, hashes, and anchors. It reads the file on disk, so it works even with no network connection.
More ways to install, verify, and build
Verify your download
Every release ships a manifest of SHA-256 digests plus a dual-signed DSSE envelope. Download release-manifest.json and release-manifest.dsse.json from the same release, then confirm your file before you run it.
Windows (PowerShell)
Get-FileHash helmd-windows-x64.exe -Algorithm SHA256macOS or Linux
shasum -a 256 helmd-macos-arm64Compare the printed digest against the one in release-manifest.json. The DSSE envelope carries Ed25519 and ML-DSA-44 signatures over that manifest, so a tampered binary or a manifest signed by any other key fails the check. Once Helm is running you can drop the envelope into the Verify tab to check it in your browser, no command line needed.
Build it yourself from source
The hub is TypeScript on Node, with no compiled native dependencies. You need Node 22.5 or newer.
git clone https://github.com/PostOakLabs/ainumbers-helm
cd ainumbers-helm
npm install
npm run build:seaThat produces the same single-file helmd binary the releases ship. Full steps live in docs/INSTALL.md once the repository is public.
Prefer a package manager?
At launch you can skip the manual download and let a package manager handle updates for you.
Windows
winget install AINumbers.HelmmacOS
brew install ainumbers/helm/helmAny platform with Node 22.5 or newer
npm install -g @ainumbers/helm-cliThe npm install downloads the platform binary and checks its SHA-256 against the signed release manifest before first use, aborting on any mismatch.
Runs on your machine, not ours
The Helm hub is a small daemon you install. Its browser interface talks to it over a padlocked loopback link on your own computer, and the hub calls your services directly. Nothing routes through an AINumbers server, so there is no involuntary egress to a cloud you do not control.
Signed logs say what happened. Helm re-computes it.
Each run flows through a trigger, a connector fetch, a deterministic kernel, and an evidence bundle. The kernel stamps its inputs and version into a hash. Feed the same inputs back through the same kernel and the same hash appears, so the recorded work can be reproduced on demand rather than taken on faith.
Five precise labels, each with a boundary
A single "verified" badge hides more than it shows. Helm classifies every claim with exactly one of five labels, and each one states plainly what it does and does not assert. A connector reporting a value is not a statement that the value is true.
Your journal, your machine, anchored to authorities we do not control
Entries chain left to right with running-hash links, so the record shows completeness alongside membership. Periodic checkpoints anchor to independent authorities over RFC 3161 timestamping and OpenTimestamps. Alter one entry in the middle and every downstream link breaks.
A governed step inside the workflow you already have
Point your existing orchestrator at Helm with a webhook. It hands off one step, Helm runs it under governance, and returns the result with a reference to the evidence. Helm adds a governed, evidenced step to the automation you have built.
Verify offline, with no network
An evidence bundle is a self-contained archive. Drop it into a verifier and it checks signatures, running hashes, and anchors with zero network access. Signatures use Ed25519 alongside post-quantum ML-DSA-44. A tampered copy of the same bundle fails a verification row in plain view.
Reconstructable records, by design
The EU AI Act Article 12 record-keeping obligation asks that high-risk system activity be reconstructable over a period. Helm's journal carries the named fields that mapping needs, and its evidence bundles let an outside party rebuild what happened from signed records alone. The obligation applies from 2026-08-02.
Helm is in Phase 1 development. The OCG Control Plane profile is drafted as SPEC section 26. Security contact: [email protected]