Credential gated rehearsal — 2027-07-05 target

D-18 story. As a credential holder, I want a Cardano preprod transaction to pass with my synthetic credential chain and fail after a relevant revocation is recorded, so that the team can rehearse the first ACDC-gated action end to end.

Planned release tag: Cardano KERI v2.0.0 (credential-gate M2). This names the milestone target; intermediate plays use release candidates, and the tag waits for the D-19 release gate and its preprod evidence.

This is a dated review target from the live project card. Not yet playable as the connected target. No confirmed ledger outcome or release acceptance is claimed by this page.

Planned play and evidence

Given the verified four-link package, connected issuer and TEL state, and a gated spending or minting action on preprod; when the holder submits the valid action, a QVI revocation is recorded through the D-14 path, and the action is retried; then the first transaction is confirmed and the retry is refused by the on-chain gate for the recorded revocation.

sequenceDiagram
    participant A as Story actor
    participant M as Accepted model
    participant C as Cardano boundary
    A->>M: Prepare the stated evidence
    M-->>A: Check expected transition and refusal
    A->>C: Submit the connected action when implemented
    C-->>A: Read back the actual result or refusal

The intended positive observation is: A preprod action passes with the valid synthetic chain, a QVI revocation is recorded, then the same action is retried. The relevant refusal is: The retry is refused by the on-chain gate for the recorded revocation. These are acceptance criteria, not observed results.

Presenter path: 10–15 minutes when runnable

Time	Presenter action	Evidence to inspect
0–2 min	State the actor's goal and identify all synthetic inputs.	Pin the exact accepted model and release revisions.
2–5 min	Establish the card's given state through its connected prior operations.	Inspect the actual starting outputs and required evidence.
5–8 min	Run the planned positive action.	Compare fresh readback with the bound model transition.
8–11 min	Run the planned negative control.	Attribute the refusal to the actual boundary.
11–15 min	Review receipts and gaps.	Identify transactions, scripts, witnesses, values and uncovered behavior.

Missing interface or receipt

Connected preprod setup through keripy and ckeri, accepted action hash and readback, D-14 revocation-push hash, refused retry trace, script identities and execution units.

The model base visible in this checkout is Cardano KERI commit 0e638fadc987f0cd98f839edd3e3ecd5a09a1b91. It is a source identity for planning, not a claim that the later card is already modeled or accepted. Each claim must bind the accepted model revision for that behavior before promotion. The Lean correspondence register holds affected conflicts. A simulator or source fact cannot replace a confirmed transaction, and no cast of an accepted connected result is available here.

Tracking: First vertical of KERI M2 demo #45, consuming #31 and #32.