Thanks for the comment - that's a fair distinction between observability and verifiable proof.

To clarify scope: this article is about the mechanics of pod termination itself (SIGTERM, the grace period, preStop hooks, and the readiness/signal ordering), not about settling a billing dispute between two parties. For what it does cover, the "proof" isn't a dashboard or a vendor badge - it's the cluster's own record: kubectl describe pod for the termination reason and exit code, kubelet logs for signal timing, and terminationGracePeriodSeconds in the pod spec, all of which any operator can query directly.

What you're describing - a signed, tamper-evident record of "what ran" that a buyer can independently verify in an invoice dispute - is a genuinely different and valid problem, closer to metering/attestation than to shutdown mechanics. It's just outside what this piece set out to do. Happy to discuss that separately if you'd like to go deeper on it.