CI / lint-and-test (push) Waiting to run

Details

- Add broad Cory-style outcome scenarios to the open-ended benchmark so regular-use ambiguity is tested, not only exact ID canaries.

- Add a clone-proven cross-surface strategy anchor packet that updates the mapped rich proposal anchor only after Claim D exists.

- Retain VPS Docker DB, claim/body metadata, and cross-surface proof reports with ruff plus 37 focused tests passing.

`docs/reports/leo-working-state-20260709/cory-expected-working-leo-outcomes-20260709.md`

`docs/reports/leo-working-state-20260709/cross-surface-apply-authorized-commit.sql`

`docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-current.log`

`docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-failed-source-id-constraint.log`

`docs/reports/leo-working-state-20260709/cross-surface-delete-rollback.sql`

`docs/reports/leo-working-state-20260709/cross-surface-packet.json`

`docs/reports/leo-working-state-20260709/cross-surface-postflight.sql`

`docs/reports/leo-working-state-20260709/cross-surface-preflight.sql`

`docs/reports/leo-working-state-20260709/cross-surface-resolution-current.md`

`docs/reports/leo-working-state-20260709/current-truth-index.md`

`docs/reports/leo-working-state-20260709/leo-db-state-17-cory-outcome-benchmark.svg`

`docs/reports/leo-working-state-20260709/leo-db-state-18-db-vs-workspace.svg`

`docs/reports/leo-working-state-20260709/leo-db-state-19-claims-body-metadata.svg`

`docs/reports/leo-working-state-20260709/leo-db-state-20-cross-surface-anchor.svg`

`docs/reports/leo-working-state-20260709/working-leo-current-state-20260709.md`

`docs/reports/leo-working-state-20260709/working-leo-definition-20260709.md`

`docs/reports/leo-working-state-20260709/working-leo-execution-plan-current.md`

`docs/reports/leo-working-state-20260709/working-leo-open-ended-benchmark-spec.json`

`scripts/kb_cross_surface_resolution_packet.py`

`scripts/working_leo_open_ended_benchmark.py`

`tests/test_kb_cross_surface_resolution_packet.py`

`tests/test_working_leo_open_ended_benchmark.py`

2026-07-09 23:39:51 +02:00

6.3 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
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
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
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
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

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.
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.
Governance-gate, concept-map, and Rio strategy targets remain explicitly deferred because current schema has no safe direct write path for them.
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.

6.3 KiB Raw Blame History