What a receipt claims
Trust & Boundaries
What a receipt proves, and what it does not.
A receipt proves that a given input, normalized into a canonical form, was evaluated under a specific public rule profile by a specific engine identity, and that the recorded result matches that evaluation, byte for byte.
- 01
The rightness, fairness, or legality of the policy itself.
- 02
The truth or provenance of the input.
- 03
The actual enforcement, timing, or attribution of the decision. Signatures and timestamps are a separate layer.
- 04
Semantic equivalence across whole languages.
- 05
Fitness for regulatory or audit purposes.
Verification covers the checked subset of Lispex, the CSK Profile. Nothing outside that subset is claimed.
The two execution paths share some foundations. This design catches divergence between paths. It is not an audit by an unrelated third party.
Honest boundaries are the product.
Explore every field