Init / Absorb / Derive / Ratchet — three-stage schedule
English one-page PDF · Reproduction script · Lean source
curl -fSLO https://kpp.kenosian.com/k-lean/deck/NICK-REPRODUCE.sh bash NICK-REPRODUCE.sh
Requires bash, curl, Python 3, Git, elan/Lake, network access to public dependencies, and at least 4 GiB available RAM. The script downloads pinned Lean/Mathlib dependencies; the existing local reproduction check reused their pinned cache. Source and proof definitions are unchanged.
A reproducible starting point for reviewing DECK state boundaries in draft-sullivan-tls-xof-schedule-00. Prepared by Peter Jang, Kenosian, for discussion with Nick Sullivan. This artifact fixes the draft revision and makes proof scope explicit.
Lean 4.14.0 and the existing K-Lean/Vault local checker accepted 23 named theorem results. Dependencies are limited to propext, Classical.choice and Quot.sound; there are no custom axiom declarations or admitted proofs. A separate Python SHAKE256 replay matches 21 Appendix D.1 vectors; 13 query encodings emitted by the Lean definitions match Python byte for byte. These are self-produced checks, available for independent reproduction. The K-Vault CLI freshly rechecked this exact file at 2026-10-16 05:34 UTC and sealed its SHA-256 in receipt a8e676b2f7ba1790a91070e9; the public receipt endpoint returned verified=true. [MEASURED: manifest.json, klean-result.json, vectors-result.json, DECK_Invariants.lean.receipt.json]
The attached NICK-REPRODUCE.sh checks the source receipt, then runs the source with the pinned Lean 4.14.0 project. Receipt checks authenticate digests and time; the local Lean command executes the kernel. The K-Vault submission path is restored; source review is held in an access-controlled repository. Independent reproduction uses the public standalone source and pinned public Mathlib dependencies, without access to our private repository. The reviewed DECK source is merged at commit 0cceaa16320d51004e84250c72771ad7a83bc7a8. Its 24 declarations (23 explicitly audited results plus Item.ext_data) are available through the Vault theorem API with source-bound compiled-artifact digests.
The XOF is an explicit length-indexed parameter. The artifact does not prove concrete Keccak security, physical memory erasure, output-key independence, or full TLS/MAC composition. The guessing bound does not establish the entropy premise or a reduction from concrete DECK recovery. Time freshness is not treated as a substitute for unknown secret entropy. Logical retirement is distinct from implementation zeroization.
Live Vault certificate: frame_injective
Confirm the framing, context tags and stage paths against your intended revision; agree the compromise/erasure model; then choose the first full-schedule composition or state-recovery reduction to mechanize together.
Standalone Lean code · Evidence manifest · Lean file receipt ·