Explore a policy proof.

Edit a bounded policy and action log, generate a Groth16 proof, and inspect its public signals. This proof of concept is for experimentation, not production use.

The proof covers specified checks over a supplied log. It does not establish actual execution, log completeness, model identity, or whether a model assessment was correct. The included setup parameters are experimental.

Inputs

Policy JSON (up to 5 rules) Action log JSON (up to 8 calls)

Each call supports up to 4 string parameters. Names and values are limited to 64 UTF-8 bytes. Oversized inputs are rejected, never truncated.

Public proof result

The public signals are a salted policy commitment, a salted session root, and the compliance result. No model inference is proved.

Policy commitment

No proof yet

Session root

No proof yet

Expected policy commitment (optional) Expected session root (optional)

Import proof or session-proof bundle

A valid proof and a compliance result are separate facts. Without independently agreed commitments and a trusted verification key, verification alone does not identify an approved policy or an authentic session.