SENTINEL

Reference implementation of the Veraxis Execution Integrity Protocol

VEIP requires cryptographic evidence of authorization to be generated before a state transition crosses a declared execution boundary. Not logged during. Not recorded after. Generated before, and the action blocked until it is.

This site exposes the live implementation running inside the Qaori autonomous software factory. Every action the factory takes that crosses a consequential threshold, machine or human, emits a signed Authorization Evidence Pack (AEP). The signature is verifiable by anyone with the published public key, without access to internal systems.

Surfaces

REFERENCE

/reference

The protocol, the wire format, the canonical serialization rule, the verification procedure, the tier definitions, and the full enumerated boundary catalogue. Reads like an RFC. Cite from this page.

TELEMETRY

/telemetry

Live operational view of the running implementation. Counters, by-tier distribution, by-boundary histogram, recent AEP stream, fail-closed count. Proof that this is a production system, not a paper.

VERIFY

/verify

Paste an AEP, watch it cryptographically verify in your browser via WebCrypto. The math runs client-side against the published public key. Includes the offline openssl command for paranoid reviewers.

Substrate facts

Algorithm
Ed25519 (RFC 8032)
Hash
SHA-256 (FIPS 180-4)
Canonical JSON
Sorted keys, no whitespace (RFC 8785 §3.2.1)
Key id
qaori-aep-v1
Public key (PEM)
loading…
Evidence vault
s3://qaori-prod-evidence-vault/<YYYY>/<MM>/<DD>/<boundary>/<aep_id>.json
Declared boundaries
loading…
Reference code
shared/aep.py · shared/aep_boundaries.py
First AEP issued
2026-06-30 · build.pr_created (verifiable in /telemetry)

What an expert reviewer should do

  1. Read /reference §1 Wire Format — confirm the protocol shape is what you expect of an authorization evidence framework.
  2. Open /verify, click "Load test vector", confirm the in-browser verification succeeds. Paste your own AEP to verify any production evidence end-to-end.
  3. Inspect /telemetry; confirm the numbers are increasing and the fail-closed count is honest.
  4. Read the source: shared/aep.py. The file is intended to be readable as the spec, not just the implementation.