Telegram-Visible Direct-Claim Preflight

Generated UTC: 2026-07-10T04:25:06.518703+00:00 Mode: telegram_visible_direct_claim_preflight_readonly Status: pass Ready for authorized Telegram-visible DC run: True Telegram-visible messages sent: False Production apply executed: False Mutates DB: False Remote source: supplied_remote_json_base64 Remote readback command: docs/reports/leo-working-state-20260709/telegram-visible-direct-claim-remote-readback-command-current.sh Remote readback command SHA256: 9bbfbe1de6e3f63e7aa9f73a7f412aa16f8f2f60b3c46f87ee93472290047c89

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: True
deploy_head_matches_last_deploy: True
remote_packet_nonempty: True
remote_packet_present: True
service_active_running: True
ssh_readback_ok: True

Deploy And Service

Deploy head: 63278b6354d3f5f15ed68897be95d484530db59f
Last deploy SHA: 63278b6354d3f5f15ed68897be95d484530db59f
ActiveState: active
SubState: running
MainPID: 2999690
NRestarts: 0
ExecMainStartTimestamp: Fri 2026-07-10 03:47:11 UTC

DB Counts Before Send

public.claims: 1837
public.sources: 4145
public.claim_evidence: 4670
public.claim_edges: 4916
kb_stage.kb_proposals: 26

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.

1.9 KiB Raw Blame History