teleo/teleo-infrastructure
8
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions 1
teleo-infrastructure/docs/reports/leo-working-state-20260709/telegram-handler-m3taversal-oos-suite-score-pre-schema-repair-20260713.md
twentyOne2x 64c35a7589 Harden Leo against schema and receipt drift
2026-07-13 09:17:28 +02:00

1 KiB
Raw Blame History

Working Leo m3taversal Out-of-Sample Score

Generated UTC: 2026-07-13T07:10:12.532120+00:00 Pass: False Prompts: 5/9 DB counts changed: False Service unchanged: True Temporary profile removed: True Posted to Telegram: False

Prompt Scores

  • OOS-01 / demo_pressure_without_ids: pass=True
  • OOS-02 / multi_surface_knowledge_ingestion: pass=True
  • OOS-03 / identity_restart_truth: pass=False
  • OOS-04 / partner_demo_claim_ceiling: pass=True
  • OOS-05 / source_pointer_is_not_evidence: pass=False
  • OOS-06 / database_composition_judgment: pass=False
  • OOS-07 / same_session_memory_set: pass=True
  • OOS-08 / same_session_memory_recall: pass=True
  • OOS-09 / telegram_participant_identity: pass=False

Claim Ceiling

A pass proves broad out-of-sample and same-session-memory behavior through the live VPS GatewayRunner using a temporary profile, with no Telegram post and no DB count change. It does not prove human-visible Telegram delivery, production DB apply, or GCP parity.