Kveritas Go

Tamper-evident verification for computational experiments. It binds a published result to the exact code, hardware, and time that produced it, in a cryptographically signed PDF anyone can verify. Works with any language, zero runtime dependencies, single static binary.

Platform. Verify, seal, proofs, checkout, benchmark artifacts, provenance, and disclosure levels are cross-platform. The file/subprocess activity map and per-process hardware attribution are Linux-only today; elsewhere they fall back to system-wide readings.

Print these to stdout in any language; everything captured is bound into the signed record.

Common metrics are also auto-detected (Keras history, sklearn CV, metric-like locals), so simple runs need no lines.

When a run declares a model card, seal produces a certificate checking the declared FLOPs against what the hardware could physically deliver.

Each run is a signed timeline of content-addressed snapshots (source state at run start, each phase, and run end, plus what changed), Merkle-linked and bound into the signature. You choose per session how much is revealed; this controls disclosure only, integrity is always committed.