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/current-truth-index.md
twentyOne2x 01a65b1b9b
Some checks are pending
CI / lint-and-test (push) Waiting to run
Details
Score retained Working Leo Telegram benchmark evidence 
- Rescore retained live Telegram replies with partial versus full coverage labels
- Retain OE-01 benchmark score artifacts without mutating Leo or production DB
- Update Working Leo truth docs and tests so partial proof is not overclaimed

`docs/reports/leo-working-state-20260709/current-truth-index.md`
`docs/reports/leo-working-state-20260709/telegram-live-open-ended-benchmark-score-current.json`
`docs/reports/leo-working-state-20260709/telegram-live-open-ended-benchmark-score-current.md`
`docs/reports/leo-working-state-20260709/working-leo-current-state-20260709.md`
`docs/reports/leo-working-state-20260709/working-leo-execution-plan-current.md`
`scripts/working_leo_open_ended_benchmark.py`
`tests/test_working_leo_open_ended_benchmark.py`
2026-07-10 00:30:37 +02:00

12 KiB
Raw Blame History

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 (5 live-safe open prompts plus 6 broader Cory-style outcome scenarios for disposable clone/sandbox first)
  • 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
  • Retained Telegram benchmark score for the open-ended canary: docs/reports/leo-working-state-20260709/telegram-live-open-ended-benchmark-score-current.md
  • Retained Telegram benchmark score JSON: docs/reports/leo-working-state-20260709/telegram-live-open-ended-benchmark-score-current.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
  • VPS/Hermes/DB mapping: docs/reports/leo-working-state-20260709/vps-hermes-db-mapping-20260709.md
  • DB provenance/load-path report: docs/reports/leo-working-state-20260709/leo-db-provenance-report-20260709T214741Z.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
  • Mapped production apply packet JSON: docs/reports/leo-working-state-20260709/production-apply-packet.json
  • Mapped production apply authorized commit SQL, not executed in production: docs/reports/leo-working-state-20260709/production-apply-authorized-commit.sql
  • Mapped production apply delete rollback SQL: docs/reports/leo-working-state-20260709/production-delete-rollback.sql
  • Cross-surface strategy anchor companion packet, not executed in production: docs/reports/leo-working-state-20260709/cross-surface-resolution-current.md
  • Cross-surface packet JSON: docs/reports/leo-working-state-20260709/cross-surface-packet.json
  • Cross-surface authorized commit SQL, not executed in production: docs/reports/leo-working-state-20260709/cross-surface-apply-authorized-commit.sql
  • Cross-surface delete rollback SQL: docs/reports/leo-working-state-20260709/cross-surface-delete-rollback.sql
  • Cross-surface clone commit/delete rollback log: docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-current.log
  • Rio strategy-context companion packet, not executed in production: docs/reports/leo-working-state-20260709/rio-strategy-context-current.md
  • Rio strategy-context packet JSON: docs/reports/leo-working-state-20260709/rio-strategy-packet.json
  • Rio strategy-context authorized commit SQL, not executed in production: docs/reports/leo-working-state-20260709/rio-strategy-apply-authorized-commit.sql
  • Rio strategy-context delete rollback SQL: docs/reports/leo-working-state-20260709/rio-strategy-delete-rollback.sql
  • Rio strategy-context clone commit/delete rollback log: docs/reports/leo-working-state-20260709/rio-strategy-clone-rehearsal-current.log
  • Governance/concept-map schema companion packet, not executed in production: docs/reports/leo-working-state-20260709/governance-concept-current.md
  • Governance/concept-map packet JSON: docs/reports/leo-working-state-20260709/governance-concept-packet.json
  • Governance/concept-map authorized commit SQL, not executed in production: docs/reports/leo-working-state-20260709/governance-concept-apply-authorized-commit.sql
  • Governance/concept-map delete rollback SQL: docs/reports/leo-working-state-20260709/governance-concept-delete-rollback.sql
  • Governance/concept-map clone commit/delete rollback log: docs/reports/leo-working-state-20260709/governance-concept-clone-rehearsal-current.log
  • 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 7 Powers apply packet JSON: docs/reports/leo-working-state-20260709/helmer-7powers-production-apply-packet.json
  • Helmer 7 Powers authorized commit SQL, not executed in production: docs/reports/leo-working-state-20260709/helmer-7powers-production-apply-authorized-commit.sql
  • Helmer 7 Powers delete rollback SQL: docs/reports/leo-working-state-20260709/helmer-7powers-production-delete-rollback.sql
  • Working Leo integrated packet manifest, not executed in production: docs/reports/leo-working-state-20260709/working-leo-integrated-packet.md
  • Working Leo integrated packet JSON: docs/reports/leo-working-state-20260709/working-leo-integrated-packet.json
  • Working Leo integrated clone rehearsal report: docs/reports/leo-working-state-20260709/working-leo-integrated-packet-current.md
  • Working Leo integrated clone rehearsal log: docs/reports/leo-working-state-20260709/working-leo-integrated-clone-rehearsal-current.log
  • 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
  • Helmer ledger clone commit/delete rollback log: docs/reports/leo-working-state-20260709/helmer-7powers-ledger-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
  • Helmer ledger packet proof: docs/reports/leo-working-state-20260709/leo-db-state-16-helmer-ledger.svg
  • Cory-style outcome benchmark map: docs/reports/leo-working-state-20260709/leo-db-state-17-cory-outcome-benchmark.svg
  • Leoclean DB versus workspace map: docs/reports/leo-working-state-20260709/leo-db-state-18-db-vs-workspace.svg
  • Claim/body/metadata schema map: docs/reports/leo-working-state-20260709/leo-db-state-19-claims-body-metadata.svg
  • Cross-surface strategy anchor proof: docs/reports/leo-working-state-20260709/leo-db-state-20-cross-surface-anchor.svg
  • Forgejo/load/agent update loop map: docs/reports/leo-working-state-20260709/leo-db-state-21-forgejo-load-agent-loop.svg
  • Identity render / decision matrix / document artifact map: docs/reports/leo-working-state-20260709/leo-db-state-22-identity-render-matrix-artifacts.svg
  • Rio strategy context packet proof: docs/reports/leo-working-state-20260709/leo-db-state-23-rio-strategy-context.svg
  • Governance/concept-map schema packet proof: docs/reports/leo-working-state-20260709/leo-db-state-24-governance-concept-schema.svg
  • Integrated apply rehearsal proof: docs/reports/leo-working-state-20260709/leo-db-state-25-integrated-apply-rehearsal.svg
  • DB loading diagram SVG: docs/reports/leo-working-state-20260709/leo-db-loading-diagram-20260709T214741Z.svg
  • DB loading diagram Mermaid source: docs/reports/leo-working-state-20260709/leo-db-loading-diagram-20260709T214741Z.mmd

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 and retained-benchmark-scored for OE-01 only: partial coverage, 1/1 scored prompt passing, no overclaim, no KB mutation.
  • The broader Cory-style benchmark layer is specified but not yet live-run; it intentionally tests regular-use ambiguity without exact proposal IDs.
  • A strict canonical add_edge apply canary is live-proven.
  • Helmer 7 Powers is full-coverage packet and ledger clone-proven, not production-applied.
  • Mapped rich approved proposal packet is clone/rehearsal-proven for the supported subset, not production-applied.
  • The strategy-anchor companion write for mapped rich proposal 14fa5ecc is clone-proven and reversible, not production-applied.
  • The Rio strategy-context companion write for mapped rich proposal 14fa5ecc is clone-proven and reversible: after the mapped base packet exists, it creates 2 Rio strategy nodes and 5 strategy anchors in a disposable clone; production stayed unchanged.
  • The governance/concept-map schema companion write is clone-proven and reversible: after the mapped base packet exists, it creates minimal concept-map and claim-to-governance link tables, then inserts 1 concept map, 1 concept link, and 2 governance links in a disposable clone; production stayed unchanged.
  • The full integrated packet set is now clone-proven in production dependency order: mapped base, cross-surface anchor, Rio strategy context, governance/concept schema, and Helmer 7 Powers applied together in teleo_integrated_rehearsal_20260710, then rolled back in reverse order; production stayed unchanged and the disposable clone/temp files were removed.
  • DB-first identity rendering is now documented from the July 9 PDFs plus VPS readback: canonical identity rows feed rendered SOUL.md, direct SOUL edits are not canonical DB updates, and no active renderer/timer/hook is proven in the current VPS readback.
  • The decision-matrix approval schema is still a target design on the current VPS: kb_stage.matrix_voters, kb_stage.proposal_votes, and kb_stage.proposal_decisions were not present in live schema readback.
  • Pending/approved document proposals are real kb_stage.kb_proposals rows with source_refs, but inspected source_refs did not directly match public.sources; they still need review/apply mapping into canonical sources/evidence/edges.
  • Governance-gate and concept-map targets are now schema-packet-proven, but not production-applied; the live VPS production schema still has no generated governance/concept tables.
  • The live VPS runtime behavior should not be changed while the DB apply path is stabilized.
  • A live Telegram regression canary should be rerun after any production apply; no production apply has been authorized or executed.
  • GCP parity remains blocked by account auth/access facts until a fresh readback proves otherwise.