# Telegram-Visible Direct-Claim Preflight

Generated UTC: `2026-07-10T02:55:21.031274+00:00`
Mode: `telegram_visible_direct_claim_preflight_readonly`
Status: `fail`
Ready for authorized Telegram-visible DC run: `False`
Telegram-visible messages sent: `False`
Production apply executed: `False`
Mutates DB: `False`
Remote source: `ssh_subprocess`
Remote readback command: `docs/reports/leo-working-state-20260709/telegram-visible-direct-claim-remote-readback-command-current.sh`
Remote readback command SHA256: `741b9ee14548122cc5e15009f3bbbbfddd4389a1452099265f80f367cbe467ec`

## Packet Checks

- `packet_does_not_execute_production_apply`: `True`
- `packet_does_not_mutate_db`: `True`
- `packet_has_no_authorization_recorded`: `True`
- `packet_message_count_exact`: `True`
- `packet_not_sent`: `True`
- `packet_prompt_ids_exact`: `True`
- `packet_ready_to_request_authorization`: `True`
- `packet_targets_leo_group`: `True`

## Remote Checks

- `db_counts_read`: `False`
- `deploy_head_matches_last_deploy`: `False`
- `remote_packet_nonempty`: `False`
- `remote_packet_present`: `False`
- `service_active_running`: `False`
- `ssh_readback_ok`: `False`

## Deploy And Service

- Deploy head: ``
- Last deploy SHA: ``
- ActiveState: ``
- SubState: ``
- MainPID: ``
- NRestarts: ``
- ExecMainStartTimestamp: ``

## DB Counts Before Send

- `public.claims`: ``
- `public.sources`: ``
- `public.claim_evidence`: ``
- `public.claim_edges`: ``
- `kb_stage.kb_proposals`: ``

## Blocker Readback

- Current canary: Pre-send Telegram-visible direct-claim benchmark readiness for DC-01 through DC-06 in the Leo group, expecting packet verification plus VPS deploy/service/DB count readback before any authorized send.
- Exact gate: `ssh: connect to host 77.42.65.182 port 22: Operation not permitted`
- Clear CTA: Run `docs/reports/leo-working-state-20260709/telegram-visible-direct-claim-remote-readback-command-current.sh` from a full-access shell, then rerun `scripts/collect_telegram_visible_direct_claim_preflight.py --remote-json-base64 <payload>` with the base64 output it prints. Only after this report passes should the exact DC-01 through DC-06 Telegram group messages be sent under explicit action-time authorization.
- Next non-user action: Rerun this preflight with supplied VPS remote readback JSON, then run the Telegram-visible DC scorer and service/DB after-readbacks if the user explicitly authorizes the group send.

## Claim Ceiling

This is a read-only preflight for an explicitly authorized Telegram-visible DC benchmark. It does not send Telegram messages, does not run production apply, and does not prove Telegram-visible DC behavior until the six-message run is authorized, sent, captured, and scored.