Validance

A validated execution kernel. Validance runs declarative workflows with a tamper-evident audit trail, kernel-enforced approval gates, and a language-agnostic REST contract. The kernel is immutable and validated as a frozen artifact: workflows change weekly, the engine doesn't change, and a customer doesn't re-validate what doesn't change.

Temporal guarantees that your workflow replays correctly. Validance guarantees you can prove what happened and why.

Validance is built for systems where execution itself needs to be evidence — regulated industries (GxP, 21 CFR Part 11), treasury and payments operations, and AI agent platforms where every action must be gated, logged, and explainable.

What makes the architecture different:

• An immutable kernel with declarative contracts. Workflows are data; the engine that runs them is frozen and validated once.
• Cryptographic provenance per execution. Every state transition lands in a dual hash chain: tamper-evident, independently verifiable, fail-closed.
• Approval and policy enforced by the kernel, not the caller. An LLM agent cannot police itself; the engine does.

Read more

• Architecture: the three layers, the boundary discipline, the kernel-caller split.
• SDK reference: how to declare tasks and workflows in Python.
• REST API reference: the wire format, every endpoint.