# Telegram-Visible Direct-Claim Capture Receipt

Generated UTC: `2026-07-10T03:01:26.898794+00:00`
Mode: `telegram_visible_direct_claim_capture_receipt`
Status: `awaiting_capture`
Receipt ready: `False`
Capture present: `False`
Telegram-visible messages sent: `False`
Production apply executed: `False`
Mutates DB: `False`

## Checks

- `authorization_text_matches`: `False`
- `capture_complete_for_scoring`: `False`
- `capture_present`: `False`
- `db_before_after_present`: `False`
- `empty_reply_prompt_ids`: `['DC-01', 'DC-02', 'DC-03', 'DC-04', 'DC-05', 'DC-06']`
- `final_visual_proof_present`: `False`
- `message_ids_exact`: `False`
- `missing_prompt_ids`: `['DC-01', 'DC-02', 'DC-03', 'DC-04', 'DC-05', 'DC-06']`
- `replies_nonempty`: `False`
- `score_passes`: `False`
- `sent_text_exact`: `False`
- `service_readback_present`: `False`
- `target_matches_packet`: `False`
- `text_mismatch_prompt_ids`: `[]`
- `unexpected_prompt_ids`: `[]`

## Capture Template

Populate `messages[].reply`, timestamp/id fields, `db_before_after`, `service_readback`, and `capture_source.final_screenshot` / `capture_source.final_accessibility`, then rerun this script with `--capture-json`.

## Claim Ceiling

This receipt validates retained Telegram-visible capture evidence only. It does not send Telegram messages, does not run production apply, and does not prove canonical DB mutation. A pass requires exact DC-01..DC-06 messages, matching operator authorization, nonempty visible replies, DB/service readbacks, visual proof, and a 6/6 direct-claim score.
