Decionis
Start Now

Layer 5 — The proof

Inspect the decision. Verify the evidence.

Run a decision, inspect the signed record and reproduce the verification with public tools and research.

How can I check a Decionis decision?

Decionis records each decision in an Ed25519-signed Decision Dossier. You can inspect the proposed action, policy context and verdict, then verify the signature against published public keys. Open verification tools and a public synthetic corpus let you reproduce the checks. Research explains the methods and the limits of what those checks establish.

  • Run a live decision with synthetic data.
  • Inspect its signed Decision Dossier.
  • Verify a downloaded record independently.
  • Read the corpus methodology and research.
Open the public corpus and verification tools

Synthetic tests demonstrate specific technical properties. They do not establish customer adoption, financial savings or independent certification.

The Proof — Open, verifiable, and developer-friendly.Four forms of evidence orbiting one protocol. The Sandbox: try Decionis, verify the proof. The Policy Exchange: discover, reuse, and share policies. Connectors: bring Decionis to where you work. GitHub: the public govern Action and Node SDK, plus independently verifiable Decision Dossiers. These are not four products in a navigation bar; they are four answers to four different doubts. Transparency builds trust, and proof drives adoption.SANDBOXTry Decionis.Verify the proof.POLICY EXCHANGEDiscover, reuse,and share policies.CONNECTORSBring Decionisto where you work.GITHUBPublic Action & SDK.Verifiable dossiers.DECIONISProtocol
Four forms of evidence orbiting one protocol. The Sandbox: try Decionis, verify the proof. The Policy Exchange: discover, reuse, and share policies. Connectors: bring Decionis to where you work. GitHub: the public govern Action and Node SDK, plus independently verifiable Decision Dossiers. These are not four products in a navigation bar; they are four answers to four different doubts. Transparency builds trust, and proof drives adoption.
Transparency builds trust. Proof drives adoption.

Four forms of evidence

“Is this a real system or a landing page?”

GitHub

Proof we are real.

The govern Action and the Node SDK are public, and every Decision Dossier can be verified against our published JWKS without trusting our code.

“Does the protocol actually stop anything?”

Sandbox

Proof the protocol works.

Try to overspend, violate policy, delete production, expose secrets or bypass approval, and watch the verdict come back. No account required.

“Can we express our own authority in it?”

Policy Exchange

Proof people can build on it.

The policy packs the Decionis evaluator ships, each a versioned bundle of rules, shown rule by rule in the order the evaluator tries them.

“Can we actually deploy it where we work?”

Connectors

Proof it is deployable.

Every place Decionis becomes available — checkout, ERP, ITSM, agent tool calls — reached without rewriting the system it governs.

Published distribution proof

Zapier reviewed and published these templates on August 4, 2026. Each activation route is tied to the published template id, not a guessed directory URL.

Which proof do you need?

Pick the role you are reading as. Each route lists the questions that audience actually asks, and where each one is answered.

Developer

You will wire this into a codebase and need to know how it behaves under failure.

What you are asking

  • “How long does the setup actually take?”
  • “What does the call look like, and what comes back?”
  • “Is it deterministic — same input, same verdict?”
  • “What is the added latency?”
  • “What happens when Decionis is unreachable?”
  • “Can I test it locally without an account?”

Where it is answered

Security & compliance

You have to defend this in an audit and know exactly what is retained and where.

What you are asking

  • “Which policy version governed a given action?”
  • “How do I verify a signature without trusting you?”
  • “Who held the authority, and is it separated from execution?”
  • “What is retained, for how long, and where does it run?”
  • “How does this map onto our control framework?”

Where it is answered

Business buyer

You are deciding whether this pays for itself and how risky the rollout is.

What you are asking

  • “How much money would this have protected?”
  • “How many actions would have been restrained?”
  • “What is the false-positive rate on my own traffic?”
  • “How long until I see a number I can defend?”
  • “What is the risk of turning it on?”

Where it is answered

Platform partner

You are evaluating whether to list, co-sell or build against Decionis.

What you are asking

  • “Is there real demand from your shared users?”
  • “How mature is the integration, honestly?”
  • “What support burden lands on us?”
  • “What is the security posture for a review?”
  • “Which joint use cases actually close?”

Where it is answered

If you want to go further

Evidence for the specific claims teams push back on hardest — money, signatures, drift, and compliance posture.

Prevented-loss methodology

How a blocked action becomes a defensible number, and where we refuse to claim one.

Verify a Decision Dossier

Check an Ed25519 signature against the published JWKS yourself.

Public dossier corpus

Synthetic dossiers signed by a published key, archived with a DOI (10.5281/zenodo.22692903) and checked with @decionis/verify — the verifier's behaviour, reproducible without an account.

Public drift dashboard

Live policy-drift signals, published rather than described.

Trust and compliance posture

The exact certification status, stated without rounding up.

Published Zapier workflows

Three reviewed templates with durable activation ids for Google Sheets, HubSpot, and Shopify.

Transparency builds trust. Proof drives adoption.

Independently checkable

Verify it with our service switched off.

Every claim on this page about evidence rests on one test: can a party who does not trust Decionis check the record without Decionis in the loop? The public corpus and the open verifier let you run that test now, with no account and no network call to us.

  1. Step 1
    Download the evidence

    The Decision Dossier corpus — v0.1.4, Apache-2.0, archived with a DOI — is a set of signed dossiers with their inputs snapshot, execution binding and JSON-LD, plus the negative cases a verifier must refuse. The signing key is published on purpose, so you can regenerate the corpus instead of trusting the fixtures.

    DOI 10.5281/zenodo.22692903
  2. Step 2
    Leave Decionis out of the loop

    @decionis/verify is an open verifier that runs from two local files: the dossier and the key set. It recomputes the RFC 8785 canonical form, checks the Ed25519 signature and the execution-binding and dossier digests, and refuses anything altered. Disconnect if you like; it needs nothing from us.

    @decionis/verify@0.4.0
  3. Step 3
    Verify the decision

    The corpus proves the verifier behaves correctly, including when it should refuse. It does not prove that a production dossier verifies — that needs a real dossier and the live JWKS, and the repository documents that check separately rather than shipping a production artifact it should not have. The technical note walks through both halves, including the live key set a production dossier is checked against.

    Verify a Decision Dossier without an account
npx -y @decionis/verify \
  --file dossiers/vectors/owned-execution-bound.json \
  --jwks dossiers/corpus-jwks.json

For a regulated institution this is the test that matters: evidence that remains checkable by a party who does not trust the operator, and that stays checkable if the operator disappears.

Verify a dossier on this siteCorpus on GitHubProduction signing keys (JWKS)

Next — step 6 of 7DevelopersThe public artifacts and the fastest path to a first verdict.

Everything under Proof

What you can check yourself, before you trust any of it.

Common questions

Do I need an account to verify a dossier?

No account is needed to verify a downloaded Decision Dossier against the published public keys. Access to a private dossier still requires its authorized share link or workspace access. Signature verification and permission to read a record are separate checks.

Verify a Decision Dossier

What does the public corpus demonstrate?

The public corpus contains synthetic signed dossiers and a reproducible verification method. It lets you test signature and record-verification behavior. It does not contain customer activity, measure production adoption, or prove that a customer saved money.

Research and methodology

Where can I read implementation examples?

The published use cases describe workflows and the evidence available for each. Named company examples retain their stated affiliation and scope. Use the linked source and methodology to distinguish a technical demonstration, a design-partner implementation and a measured commercial result.

Published use cases

Updated · Published by Decionis, Inc. · Contact the team