What problem does it solve? Sessions often end with claims of completed work that were never verified — phantoms, narrated-as-done summaries, and stale status prose. This Skill turns session close into an audit: every claim of done/fixed/exists/passes must be bound to a checkable receipt, registered as broken, handed off, or retracted before the final summary is written. ## Core Features & Use Cases - Claim harvesting and receipt binding: Sweeps the session transcript for every completion claim and binds each to verifiable evidence such as commit hashes, pytest output, on-disk file paths, or spine receipt IDs. - Disposition routing: Routes unreceipted claims to exactly one outcome — appended to docs/state/BROKEN_REGISTER.md, handed off with an exact next command, or retracted from the summary. - Ledger receipt output: Writes a structured JSON ledger to ~/.dharma/session_ledgers/ and emits a LANDING LEDGER table in the final message that gates what the prose summary may claim. - Use Case: At the end of a coding session where you fixed tests, edited files, and drafted a summary, run the close-out to discover one claimed fix was never verified — it gets retracted instead of shipped as a phantom in the session summary. ## Quick Start Ask the agent to land the plane and produce a receipted session-close ledger for everything claimed in this session.
