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-targeted-post-intake-composition-repair-20260713.md
twentyOne2x 17c7875129 Make Leo honor intake and reply boundaries
2026-07-13 12:06:04 +02:00

1.4 KiB
Raw Blame History

Post-Intake-Repair Targeted Handler Check

Result

After PR #109 deployed at merge 0182f71f1c181f079080b2621016e6bf27c1e655, the same five high-risk prompts ran through the live VPS GatewayRunner with a temporary leoclean profile.

  • Strict result after semantic calibration: 2/5.
  • Passed: proposal readiness (OOS-04) and restart/persistence reasoning (OOS-10).
  • Shared-claim versus belief storage (OOS-11) was semantically correct but failed the reply budget at 250 words.
  • Source intake (OOS-14) correctly preserved current source fields and review boundaries, but omitted that the compiler is build-only/not live and used 226 words.
  • Mixed-packet composition (OOS-06) correctly isolated unsupported policy and belief writes, but flattened the reusable framework into a claim graph, omitted the current governance-gate distinction, and used 277 words.

Safety Readback

  • Canonical counts stayed 1837/4145/4670/4916/26.
  • leoclean-gateway.service stayed active/running on PID 3166667 with zero restarts and the same start timestamp.
  • The temporary profile was removed.
  • No Telegram message or production DB apply ran.

The next repair sets a 170-word drafting target under the 220-word hard cap, requires current intake answers to lead with the non-live compiler ceiling, and adds a compact current-schema mixed-packet map.