Demo and proof surface

Reproduce the boundary. Test the claim.

This page is a reproducibility surface for VeriSigil's declared consequence-boundary controls. It is not a catalogue of unsupported product claims.

Current claim ceiling: production-wide authorization is not allowed to be claimed. Every result must be read within its declared test conditions and the authoritative evidence record.

Core proof flow

1. Establish current authority and conditions
2. Bind the exact consequential action and parameters
3. Evaluate the governed action
4. REFUSE when required conditions fail
5. Enforce ALLOW at the declared protected boundary
6. Produce cryptographic execution evidence
7. Independently verify the evidence

Current evidence snapshot

VERIFIED

STILL adversarial testing

11/11 demonstrated on the live Railway + Supabase reference environment.

VERIFIED

Receipt verification

Cryptographic receipt integrity and independent offline verification are demonstrated.

DEMONSTRATED

Tamper detection

Tampering with tested evidence is detected on the live endpoint.

DEMONSTRATED

Parameter binding

Commitment enforcement is demonstrated on the tested payment path.

PENDING

Delegation rerun

Independent confirmation of the live delegation result remains pending.

NOT PROVEN

Real Paystack transaction

The current evidence does not establish a real provider transaction reference.

Reference workflow classes

These are validation targets for generalization, not claims that every class is currently protected in production.

Financial action

Payment or refund where exact amount, destination, authority, freshness, and execution evidence matter.

Privileged data mutation

Database or record mutation where the exact operation and parameters must remain bound to the governed decision.

Production deployment

Infrastructure change where current authority and exact deployment parameters must be re-established at consequence.

Sensitive-data export

External transfer where the governed boundary must bind the exact destination and requested data operation.

External / government filing

A future validation class requiring an independently observable official submission result before success can be claimed.

Agent-to-agent action

A future validation class for delegated consequential actions and authority lineage.

How to challenge it

Try to falsify a bounded claim: alter parameters, use stale authority, replay an action, change the audience, violate delegation scope, tamper with evidence, or attempt a path that should be refused. Record the exact result as PASS, FAIL, NOT_DIAGNOSTIC, or NEW_FINDING.

Open CHALLENGE.mdOpen QUICKSTART.mdOpen Proof Report

Authoritative status

The Trust / Evidence page is authoritative for current evidence and limitations. The API/proof repository contains the underlying tests, verification tools, and artifacts.

GitHub proof repository