Preprod cutover rehearsal — 2027-03-07 target

D-10 story. As the deployment operator, I want to rehearse the new registry and validator cutover against an inventory of existing identities, so that I can identify unsafe state before touching preprod.

Planned release tag: Cardano KERI v1.0.0 (identity-core M1). This names the milestone target; intermediate plays use release candidates, and the tag waits for the D-11 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 exact candidate release, the old preprod manifest and the inventory required by #279; when the team checks deployed script identities, proposed new manifests, parameters and each existing identity’s cutover disposition; then the rehearsal names every mismatch and blocks cutover for an ARMED or FROZEN checkpoint or an unaccounted identity.

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: The operator compares the candidate archive, old and new manifests, parameters and each existing identity disposition. The relevant refusal is: An ARMED, FROZEN or unaccounted identity blocks cutover. These are acceptance criteria, not observed results.

Preprod recording path

Use keripy kli to export the event history for the identities in the cutover inventory. Use the release-bound ckeri to query their current preprod checkpoints and verify the candidate manifest against deployed references. Only a permitted disposition may proceed to a connected candidate action. Record the block reason for every ARMED, FROZEN or unaccounted identity; no cutover cast is attached yet.

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

The #279 identity inventory, old/new manifest diff, candidate archive hash, deployed script verification and disposition for every identity.

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: KERI preprod cutover #328, inventory #279.