Hunter advance and short pool — 2027-01-06 target

D-06 story. As a hunter (anyone paid to land an owner's rotation), I want to land another controller’s witnessed rotation and receive the model-defined reward, so that checkpoints can stay current without an appointed operator.

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 a registered checkpoint, a valid later KERI event and a pool with enough funds for the paid branch; when a hunter submits the advance; then the checkpoint advances and the hunter receives the specified premium (the fee the pool pays for landing a rotation); an invalid or stale competing advance is refused.

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 hunter lands a witnessed rotation and the paid branch shows its premium; the short pool follows the Lean unpaid or freeze branch. The relevant refusal is: A stale competing advance refuses. These are acceptance criteria, not observed results.

The card also asks, as an identity controller with a short hunter pool, to see the model's actual unpaid or freeze route with its bond effects. It does not specify blanket refusal.

Preprod operator play

The controller creates and witnesses a KERI rotation with keripy, then gives the CESR stream to a separate hunter. The hunter submits ckeri advance against the connected preprod checkpoint and reads back the checkpoint, pool, bond and payout. Repeat from a deliberately short pool: the hunter submits ckeri freeze with the same export, and the checkpoint is frozen on its old keys while the hunter receives the bond. Show the unpaid branch and the actual transaction effects of both. The deployed V1 preprod release does not implement this full hunter and registry story. No cast is attached until both preprod branches and their refusal receipts have been observed.

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 #323 hunter transaction, exact Lean short-pool branch, before/after pool and bonds, payout or freeze effect, and a named stale refusal. Short pool is not a blanket refusal.

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 hunter edges #323, owner datum and bonds #322.