Dealer accepted local-validator campaign — 2026-09-08

This records a completed owned local-validator campaign. It is neither a devnet result nor a new checked release claim. The runtime is the preserved strict 7d checkpoint; the host is a separately committed Journey source.

Provenance

The host was exported from the exact committed tree, built on hbox through swarm-build with the locked dependency graph, and then launched by the existing fresh Dealer launcher against the preserved sealed gate. The focused native check was cargo check --locked --offline -p dclutch-journey-campaign; it completed before the release build.

The lock closure repair is host commit c04d95a0c (journey: remove stale relayed bundle lock edge). It removes the one stale lock-only edge that made the otherwise clean ad49 host reject --locked; it does not take the in-progress bundle-builder API changes into the campaign.

Runtime artifact set

Accepted Dealer execution

The transcript marks these stages executed: checked substrate; compile and found through Open; admit and fund taker; dealer-found; dealer-quote; dealer-fill; nonzero-fill poststates; and dealer-withdraw.

The four terminal Dealer transactions charged 300,000 lamports total. The campaign also executed its named substituted-refund-wallet refusal control; it is a refusal/rollback check, not a credited refund in this accepted Dealer balance path.

Read-back and conservation

The historical weakness was a zero-unit fill. This run refutes that weakness: the accepted Fill minted 9 claim units, or 27 atoms at 3 atoms per claim unit, and its later Withdraw transferred 1 claim unit, or 3 atoms.

The poststates close the relevant arithmetic:

• 9 × 3 = 27 minted atoms.
• The supply rises by 9 in each of the first three outcomes, or 27 total.
• Taker token balance falls by 9 atoms; the fill records 9 atoms on the taker-to-hoard leg and 18 on the fund-to-hoard leg, totaling 27.
• Fund cash changes 3,000,000 − 18 = 2,999,982 on Fill, then 2,999,982 − 3 = 2,999,979 on the one-unit Withdraw.

Durable reports

The evidence is bounded to this local-validator campaign and its source-split artifact set. It does not claim fresh runtime convergence, a final frame pair, selected-Series runtime coverage, devnet execution, or a deployed cohort.

Dated addendum — 2026-09-08 provenance names

The runtime provenance row above used the gate's source_tree_sha256 value. That is a SHA-256 digest of the gate's source-tree manifest, not a Git tree object. The two exact runtime identifiers are:

The sealed gate and its ELF hashes remain unchanged. This addendum corrects only the identifier label; it makes no new runtime, devnet, or release claim.

Dated addendum — 2026-09-09 terminal continuation

The same retained 691 runtime family later completed the Dealer child through failure resolution, terminal admission, two Dealer-owned Claims redemptions, full capital exit and physical Dealer close. The final five transactions were:

Conservation closes at the Dealer boundary: the fund moved 3,000,000 -> 2,999,982 -> 2,999,979 -> 2,999,997 -> 0 atoms; the Dealer supplied and recovered 18 atoms; and Hoard retained the taker's 9-atom backing at 500,000,010 atoms. Fund, rule, quote, Dealer Position, Dealer admission, Dealer vault and Dealer Trading replay were all absent at finalized slot 11,529. Rent return was 11,393,520 lamports and the sponsor principal return was 6,681,600 lamports, with zero native close surplus.

This is a Dealer capability-child close, not whole-Market retirement. The Market Hoard and Claims replay remain live, as do the wider Market roots that the Dealer close does not own. It also remains one founder-funded scoring Dealer, not the multiple-LP control required by C-06.

The durable result is hbox:/tank/dregg-build/dclutch-dealer-life-691-052-20260909-run4/campaign/RECOVERY_RESULT.json, SHA-256 15c1daa2a4e018f45f4705cb7ab0c906e89804b3758166d0c5cfb030591ee831. Its finalized post-close account capture has SHA-256 58d291b2fd543204b216a1793e84846e6c1e8f61650f57032f734a303854d917.