Evidence Pack™

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.

Apply for pilotShadow mode contractDelegated Auditability™

Evidence Pack™ demo, stage by stage

Demo data

You learn: The flow this page describes, one stage at a time. You can: Run it end to end.

  1. Observed Action production_action_blocked: false

    KYE Protocol™

    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).

  2. Shadow Evaluation simulated_requires_approval production_action_blocked: false

    KYE Protocol™

    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.

  3. Authority Gap missing_authority_grant · high

    KYE Protocol™

    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.

  4. Guard Recommendation authority_gate · rollout: shadow

    KYE Protocol™

    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.

How this widget is built
Demonstrates
KYE™ runtime
Components
  • The stages this page describes
Flow
Each stage in order, as the page sets it out. Architecture diagram
Used on

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.

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…

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…

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…

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.

  • observed-action-payment-prepare.json — validates against kye.evidence.observed_action.v1
  • shadow-evaluation-payment-prepare.json — validates against kye.decision.shadow_evaluation.v1
  • authority-gap-001.json — validates against kye.authority.gap.v1
  • guard-recommendation-001.json — validates against kye.operating_model.guard_recommendation.v1
  • evidence-pack-demo.json — the bundle manifest
Apply for pilotHow shadow mode works

Canonical KYE™ surfaces referenced on this page: Audit Pilot · Delegated Auditability · Evidence Pack™ · KYE Protocol™.