PulseEngine

AI writes the code. Who proves it’s safe?

Verification, traceability, and attestation for safety-critical software. Open source. Built in Rust.

Evidence, as read at this build

site claims holding 73/73 claims hold each bound to evidence re-derived from the tree claims declared in claims.yaml: 45 points, 5 on 2026-09-30 to 73 on 2026-11-02; lowest 5 on 2026-10-14 as of 2026-11-02 current varve layer 2026.10.35 issued 2026-10-29 sha256:8ac0af1b889a… signed payloads per pulseengine layer, by issue date: 55 points, 44 on 2026-09-09 to 58 on 2026-10-29; lowest 44 on 2026-09-30 as of 2026-11-02 requirements with a verifying test 44/46 a verifies link in rivet 46/46 traced to a feature · rivet 0.39.0 no recorded history as of 2026-11-02

as of 2026-11-02 07:47 UTC · commit 55406bb · each tile links to its source · greyed once its source is more than 7 days old

Built by Ralf Anton Beier — 22 years automotive software architecture. 8 patents. Distinguished engineer.

November 02, 2026
Read ASPICE as a pattern: 302 of gale's 329 software requirements have a check linked, none has a result
Read as a pattern, ASPICE's engineering processes ask that every requirement be traceable to a verification measure that can fail, and to a recorded result. Measured in gale on 26 October 2026: 302 of 329 software requirements have a verification measure linked, none has a recorded result, and 25 requirements marked verified without results sit in releases rivet reports as cuttable.
October 28, 2026
The orchestrator: who does what when bottlenecks won't go away
Hardware contention, CI queues, decision queues and cross-repo seams stay with us. jess integrates, relay builds the flight stack, gale provides the kernel, and one orchestrator directs the agents across all three. The contracts between them come from real issues.

Run the same factory

The tools are open, and so is the way they are driven.

the toolchain
varve

The nine tools as one signed, dated, digest-pinned layer. A committed pin decides which binaries a project runs; outside one the shims refuse rather than quietly fall back to PATH.

Pin a project →
the method
pulseengine-claude

The procedural skills, the methodology memory and the session hooks. The loop that produced everything on this site, as an installable Claude Code plugin.

Install the plugin →

The rolling channel is provisional and makes no qualification promise — its trust root rotates at a v1.0 ceremony that has not happened, and there is no key rotation or revocation yet. How it works →