Name Your Address preprod stretch — 30 October target

As Bob, I want to lock funds against the ordered names Alice then Bob, so Alice can claim at her current destination after recovery and I can claim only after Alice's name ends permanently. This dated project card is not yet playable as a connected preprod journey.

Planned release tag: Singular v2.0.0 (naming and escrow milestone). This is a milestone target; the tag waits for the 30 October release gate, a built archive and connected preprod receipts. Candidate plays do not publish it.

Planned play

sequenceDiagram
    participant Bob
    participant Names as Singular naming records
    participant Escrow
    participant Alice
    Bob->>Escrow: Lock against [Alice, Bob]
    Alice->>Names: Recover control and set destination
    Alice->>Escrow: Claim at current destination
    Escrow-->>Alice: Pay if active name and destination match
    Note over Names,Escrow: Second connected run
    Alice->>Names: Retire and complete retirement
    Names-->>Escrow: Terminal witness
    Bob->>Escrow: Claim after Alice ends
    Escrow-->>Bob: Pay current destination if witness valid

The accepted Singular model at a6e5edbc2dafa82eb34116a1de2b6503f87c6692 supplies the registry edges and naming lifecycle. Their synthetic model address bytes are not a preprod wallet. The 23 October naming play is also awaiting connected kli, ckeri and Singular commands. There is no cast of an accepted preprod escrow payment here.

Presenter path: 10–15 minutes when runnable

Time	Action	Required observation
0–2 min	Identify Alice, Bob and the ordered names as synthetic demo identities.	Release archive hash, installed CLI and preprod manifest are visible.
2–5 min	Lock and run Alice's recovery then claim.	Confirmed lock and claim transactions; destination read at claim time.
5–8 min	Start a second lock, retire Alice and complete retirement.	The terminal witness is minted after completion.
8–10 min	Bob claims at his current destination.	Confirmed payment and fresh node readback.
10–13 min	Attempt Bob's early claim, wrong destination and missing witness.	Each refusal is attributed to its actual script boundary.
13–15 min	Review the evidence package.	Script and policy IDs, archive hash, transaction IDs and gaps are explicit.

Missing interface and evidence

The escrow validator ticket, CLI ticket, preprod journey and completion repair must yield one connected runnable script from a downloaded release. This page has no release or preprod receipt, and the two claims and three refusals have not been observed here. No timeout, refund route or payer privilege is inferred.