# Telegram Live DB Write Canary - 2026-07-09

Generated UTC: `2026-07-09T20:09:37Z`

## Scope

Live Telegram-visible test in the authenticated Chrome Telegram Web `Leo` group (`web.telegram.org/a/#-5146042086`). User explicitly authorized Leo bot test messages. The test asked Leo to stage a review proposal in `kb_stage` only and explicitly forbade canonical `public.*` mutation or runtime-memory changes.

## Result

- Turn 3 sent at `2026-07-09 22:06 Europe/Zurich`.
- Leo replied `LIVE_TG_TURN3_STAGED`.
- Leo staged proposal `8dfedb3f-3aa4-4200-970f-4c0016f6869f` in `kb_stage.kb_proposals`.
- VPS Postgres verified the proposal row exists:

```text
id                                      status          proposal_type  proposed_by_handle  channel  source_ref
8dfedb3f-3aa4-4200-970f-4c0016f6869f  pending_review  add_edge       leo-telegram-live   canary   telegram:leo:-5146042086:WL-LIVE-TG-CORY-20260709-T3
created_at: 2026-07-09 20:06:34.042946+00
rationale: Marker WL-LIVE-TG-CORY-20260709-T3: prove Telegram to Leo to DB proposal write path. Read-only canary -- no public table mutation.
```

- Canonical tables stayed untouched after the T3 timestamp:

```text
claims_marker_rows  sources_marker_rows
0                   0

claims_created_after_t3  sources_created_after_t3  edges_created_after_t3  evidence_created_after_t3
0                        0                         0                       0
```

- Turn 4 sent at `2026-07-09 22:08 Europe/Zurich`.
- Leo replied `LIVE_TG_TURN4_READBACK`.
- Leo remembered T3, read back proposal `8dfedb3f-3aa4-4200-970f-4c0016f6869f`, confirmed `pending_review`, confirmed `source_ref=telegram:leo:-5146042086:WL-LIVE-TG-CORY-20260709-T3`, and reported zero new rows in `public.claims`, `public.sources`, `public.claim_edges`, and `public.claim_evidence` after `2026-07-09 20:06:30 UTC`.

## VPS Stability

`leoclean-gateway.service` remained stable after T3 and T4:

```text
MainPID=3252143
NRestarts=0
ExecMainStartTimestamp=Thu 2026-07-09 06:59:44 UTC
ActiveState=active
SubState=running
```

## Screenshots

- Turn 3 staged reply: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/telegram-live-canary-20260709/telegram-live-turn3-staged.png`
- Turn 4 readback reply: `/Users/user/Documents/Codex/2026-07-09/019f34eb-d297-72d0-b7e2-b222d5515ab9-load/outputs/telegram-live-canary-20260709/telegram-live-turn4-readback.png`

## Claim Ceiling

This proves the live VPS Leo Telegram path can:

1. Receive a live group instruction.
2. Write a guarded review proposal to `kb_stage.kb_proposals`.
3. Remember that write in the next conversational turn.
4. Read back the staged row and distinguish staging from canonical application.
5. Leave canonical `public.*` tables unchanged.

It does not prove production application of rich Cory-approved packets. Those still require reviewed mappings and a full production apply authorization.
