3.9 KiB
3.9 KiB
Current Truth Index - Leo / Teleo - 2026-07-09
Use this file before making status claims. Prefer fresh VPS/GCP readbacks when cheap; this directory is the retained July 9 evidence snapshot committed to the Teleo infrastructure repo.
Definition And Outcomes
- Working Leo definition:
docs/reports/leo-working-state-20260709/working-leo-definition-20260709.md - Cory expected outcomes:
docs/reports/leo-working-state-20260709/cory-expected-working-leo-outcomes-20260709.md - Current state:
docs/reports/leo-working-state-20260709/working-leo-current-state-20260709.md - Execution plan:
docs/reports/leo-working-state-20260709/working-leo-execution-plan-current.md - Open-ended benchmark spec:
docs/reports/leo-working-state-20260709/working-leo-open-ended-benchmark-spec.json - Open-ended live Telegram canary:
docs/reports/leo-working-state-20260709/telegram-live-open-ended-cory-style-20260709.md - Open-ended live Telegram canary JSON:
docs/reports/leo-working-state-20260709/telegram-live-open-ended-cory-style-20260709.json - Fable onboarding prompt:
docs/reports/leo-working-state-20260709/fable-leo-teleo-onboarding.md - Operator surface map:
docs/reports/leo-working-state-20260709/operator-surface-map.md
Telegram And Live Leo Proof
- Live Telegram canary:
docs/reports/leo-working-state-20260709/telegram-live-canary-current.md - Live Telegram canary JSON:
docs/reports/leo-working-state-20260709/telegram-live-canary-current.json - Live Telegram DB-write canary:
docs/reports/leo-working-state-20260709/telegram-live-db-write-canary-20260709.md - Live Telegram DB-write canary JSON:
docs/reports/leo-working-state-20260709/telegram-live-db-write-canary-20260709.json - Handler canary:
docs/reports/leo-working-state-20260709/telegram-gateway-handler-canary-current.md - Handler canary JSON:
docs/reports/leo-working-state-20260709/telegram-gateway-handler-canary-current.json
KB DB Apply Proof
- Strict apply plan:
docs/reports/leo-working-state-20260709/kb-apply-canary-plan-current.md - Strict apply execute:
docs/reports/leo-working-state-20260709/kb-apply-canary-execute-current.md - Claim/source preview:
docs/reports/leo-working-state-20260709/claim-source-contract-preview-current.md - Mapped rich proposal plan:
docs/reports/leo-working-state-20260709/rich-proposal-creation-plan-mapped-current.md - Mapped production apply packet, not executed in production:
docs/reports/leo-working-state-20260709/production-apply-packet-current.md - Helmer 7 Powers proposal plan:
docs/reports/leo-working-state-20260709/helmer-7powers-creation-plan.json - Helmer 7 Powers apply packet, not executed in production:
docs/reports/leo-working-state-20260709/helmer-7powers-production-apply-packet-current.md - Helmer live rollback log:
docs/reports/leo-working-state-20260709/helmer-7powers-live-preflight-rollback-current.log - Helmer clone commit/delete rollback log:
docs/reports/leo-working-state-20260709/helmer-7powers-clone-commit-delete-rollback-current.log
GCP
- Current GCP blocker:
docs/reports/leo-working-state-20260709/gcp-db-parity-current-blocker-20260709.json
Images
- Skill-pack map:
docs/reports/leo-working-state-20260709/leo-db-state-13-skill-pack.svg - Helmer packet proof:
docs/reports/leo-working-state-20260709/leo-db-state-14-helmer-packet.svg - Open-ended Cory-style canary map:
docs/reports/leo-working-state-20260709/leo-db-state-15-open-ended-canary.svg
Current Claim Ceiling
- VPS Leo Telegram memory, KB audit, and staged-write canaries are live-proven.
- VPS Leo open-ended Cory-style triage is live-proven for a read-only vague incident prompt.
- A strict canonical
add_edgeapply canary is live-proven. - Rich approved proposal packets are clone/rehearsal-proven, not production-applied.
- The live VPS runtime behavior should not be changed while the DB apply path is stabilized.
- GCP parity remains blocked by account auth/access facts until a fresh readback proves otherwise.