Evidence Pack™ · supplier payment demo

See an AI-agent action produce four signed artefacts you can verify in your terminal.

A live, signed evidence pack. Verifiable in your terminal. JWKS public, payload signed, replay seed embedded.

Plain take

Plain take

A signed proof. You verify it. You replay it. You ship.

  • One JSON file. Signed by the issuer.
  • Public key in the JWKS. Hash in the chain.
  • Replay seed in the seal. Same input, same output.
  • Verifier is open source. So is the schema.
The four artefacts

Observed Action → Shadow Evaluation → Authority Gap → Guard Recommendation.

You read the same bundle your auditor reads. Each artefact references the prior one. The bundle replays offline. The flag production_action_blocked reads false on every record.

visibility 1. Observed Action production_action_blocked: false

The customer's API gateway streams an Observed Action to the KYE Evidence Gateway™. Signed by the Stack Binding's customer-side signing key (algorithm internals are proprietary).

Loading observed-action-payment-prepare.json…

policy 2. Shadow Evaluation simulated_requires_approval production_action_blocked: false

Every engine runs. Five of six checks fail. The simulated decision is simulated_requires_approval. The Decision Map™ is sealed but no production action is blocked.

Loading shadow-evaluation-payment-prepare.json…

report 3. Authority Gap missing_authority_grant · high

The Authority Gap classifier groups the failure into the locked missing_authority_grant class. References both the Observed Action and the Shadow Evaluation — the gap is fully traceable.

Loading authority-gap-001.json…

verified_user 4. Guard Recommendation authority_gate · rollout: shadow

The Guard Recommendation proposes an Authority Gate for the single agent + action pair. Twelve actions in the pilot would have been blocked had this been enforcing.

Loading guard-recommendation-001.json…
Raw JSON

Each artefact is a real public/examples file.

Download the raw JSON. Validate each file against its schema with any tool. Verify the signature with the publisher's JWKS. No KYE™ binary required to inspect the bundle.