Proof-of-Silence™ — Live Demonstration

This page defines the exact behaviour the implementation must satisfy. Live signed demonstration is coming next.

Click. See the decision. Download the record. Verify it yourself.

Scenario A — WAIT

Agent knows what is missing. Agent does not act.

SCENARIO
  Agent proposes: REFUND €2,400

EVALUATION
  Evidence      ⚠️  INSUFFICIENT
  Permission    ✓   GRANTED
  Policy        ✓   BOUND
  Freshness     ✗   EXPIRED

VERDICT
  WAIT

REASON
  Authorization / evidence freshness requirement
  is not satisfied.

EXECUTION
  NOT EXECUTED

Scenario B — SILENCE

Agent cannot establish whether execution is justified. Agent does not act.

SCENARIO
  Agent proposes: TRANSFER ACCESS — external system

EVALUATION
  Evidence      ?   AMBIGUOUS
  Permission    ✓   GRANTED
  Policy        ✓   BOUND
  Freshness     ✓   CURRENT

VERDICT
  SILENCE

REASON
  Available evidence does not establish
  whether execution is justified.

EXECUTION
  NOT EXECUTED

Scenario C — ACT_NOW

All conditions met. Agent acts. Record is created.

SCENARIO
  Agent proposes: SEND STATUS REPORT — internal

EVALUATION
  Evidence      ✓   SUFFICIENT
  Permission    ✓   GRANTED
  Policy        ✓   BOUND
  Freshness     ✓   CURRENT

VERDICT
  ACT_NOW

REASON
  All required conditions satisfied.

EXECUTION
  EXECUTED

Scenario D — REJECT

Policy explicitly prohibits this action. Agent does not act.

SCENARIO
  Agent proposes: DELETE AUDIT LOG

EVALUATION
  Evidence      ✓   PRESENT
  Permission    ✗   DENIED
  Policy        ✗   EXPLICIT PROHIBITION
  Freshness     ✓   CURRENT

VERDICT
  REJECT

REASON
  Action explicitly prohibited by active policy.

EXECUTION
  NOT EXECUTED

What the record will contain

Each verdict produces a signed record. When the live backend is connected, you will be able to download and verify it independently.

{
  "record_id":   "...",
  "scenario":    "REFUND €2400",
  "verdict":     "WAIT",
  "reason":      "...",
  "policy_hash": "sha256:...",
  "timestamp":   "2026-...",
  "signature":   "ed25519:..."
}

How to verify

macOS / Linux:
  python verifier.py record.json public_key.pem

Expected output (clean record):
  record_integrity     VALID
  signature_validity   VALID
  policy_binding       VALID

Expected output (tampered record):
  signature_validity   INVALID

Current implementation status

DEMO LOADS                  ✔ PASS  (this page)
ONE SCENARIO DEFINED        ✔ PASS
4 VERDICTS REPRESENTED      ✔ PASS  (WAIT / SILENCE / ACT_NOW / REJECT)
EXECUTION STATE VISIBLE     ✔ PASS
SIGNED RECORD EXPORT        ⧗ PENDING  (backend not yet connected)
OFFLINE VERIFY PATH         ⧗ PENDING
LIMITATIONS VISIBLE         ✔ PASS
NO FAKE CERTIFIED CLAIM     ✔ PASS

Artefact status

EXECUTION:   SIMULATED
VERDICT:     DEMONSTRATION
SIGNATURE:   NOT YET GENERATED
RECORD:      SAMPLE / STATIC

This page will be updated when the live backend
is connected and independently verified.

What a valid signature proves

A matching hash confirms the record was not modified after signing.
It does not confirm the signed claim was true in the external world.
It does not confirm the AI decision was correct.
It does not constitute certification or regulatory compliance.

WHY DID THE AGENT NOT ACT?
Because the evidence required to authorize this action did not exist.

See full verification history →   Get Standard Edition — €49 →