GitHub repository 27-GROUP/kveritas-go introduces K-Veritas CLI, a tool for tamper-evident verification of computational experiments. It binds published results to the exact code, hardware, and execution time via a cryptographically signed PDF that anyone can verify. The tool works with any programming language, has zero runtime dependencies, and distributes as a single static binary across Linux, macOS, and Windows platforms.

Installation is available via prebuilt binaries or building from source with Go 1.22+. Quick start commands include `kveritas init` to begin a session, `kveritas run` to execute commands under monitoring, `kveritas seal` to generate a signed PDF report, and `kveritas verify` to validate reports. Protocol lines like `KVERITAS_METRIC`, `KVERITAS_PHASE`, `KVERITAS_CLAIM`, and `KVERITAS_ARTIFACT` enable structured recording of metrics, phases, claims, and artifacts.

The HMCA (execution coherence) engine performs metric-blind verification by sampling per-process telemetry at ~10 Hz during execution. It scores whether CPU, memory, GPU utilization, and other channels co-fluctuate as shadows of a single genuine process, producing verdicts of PASS, WARN, FAIL, or N/A. Compute-cost attestation checks declared FLOPs against hardware physical limits across time, energy, and memory bounds, flagging violations as FABRICATION-IMPOSSIBLE. Provenance uses signed, Merkle-linked timelines with configurable disclosure levels (redacted, names, open) controlling report visibility while maintaining integrity.