unknown-delivery-reconciliationlisted
Install: claude install-skill tdw8147-crypto/skill-delivery-kit
# Unknown Delivery Reconciliation
Replace “it errored, send again” with a record that says what happened to the original request and what evidence would close it.
## When to use
- An upload times out after the server may have accepted it.
- The outbound service says `sent`, but acceptance requires `delivered`.
- Two status views disagree or use different identifiers for what may be one request.
- A same-named replacement attachment exists and the receipt must be matched to the submitted bytes.
- An operator needs a conclusion now even though the receipt console is unavailable.
## When NOT to use
- You are preparing a first submission that has not been attempted.
- The original request already has a trusted receipt at the required level; close it without reopening.
- The concern is whether form input registered before any submission.
- The user needs a general integration design, not a record about an existing attempt.
- The task is to diagnose a local draft-save error unrelated to any outbound action.
## Core rules
1. **Deliver a record from current evidence.** Missing fields should not delay an actionable conclusion.
2. **Never replay the same intent.** A new identifier, the original identifier, or a test click can all duplicate a request that already took effect; do not assume remote idempotency.
3. **Anchor identity at submission.** Target, time and submitted byte fingerprint distinguish lookalike requests and same-named replacements.
4. **Prefer the latest formal m