699a9e7917
Some checks are pending
CI / lint-and-test (push) Waiting to run
- Add reusable Teleo/Leo skills for VPS, GCP, Telegram, KB changes, provenance, and handoff onboarding. - Add guarded KB proposal tooling for approved rich proposals, apply packets, and rollback proof. - Add Cory-style open-ended benchmark prompts and tests alongside the precise regression canaries. `.agents/skills/leo-telegram-canary-ops/SKILL.md` `.agents/skills/teleo-gcp-parity-ops/SKILL.md` `.agents/skills/teleo-infra-provenance/SKILL.md` `.agents/skills/teleo-kb-db-change-workflow/SKILL.md` `.agents/skills/teleo-leo-onboarding/SKILL.md` `.agents/skills/teleo-proof-handoff/SKILL.md` `.agents/skills/teleo-vps-runtime-ops/SKILL.md` `.agents/skills/working-leo-cory-outcomes/SKILL.md` `docs/reports/leo-working-state-20260709/claim-source-contract-preview-current.md` `docs/reports/leo-working-state-20260709/cory-expected-working-leo-outcomes-20260709.md` `docs/reports/leo-working-state-20260709/current-truth-index.md` `docs/reports/leo-working-state-20260709/fable-leo-teleo-onboarding.md` `docs/reports/leo-working-state-20260709/gcp-db-parity-current-blocker-20260709.json` `docs/reports/leo-working-state-20260709/helmer-7powers-creation-plan.json` `docs/reports/leo-working-state-20260709/kb-apply-canary-execute-current.md` `docs/reports/leo-working-state-20260709/kb-apply-canary-plan-current.md` `docs/reports/leo-working-state-20260709/leo-db-state-13-skill-pack.svg` `docs/reports/leo-working-state-20260709/operator-surface-map.md` `docs/reports/leo-working-state-20260709/production-apply-packet-current.md` `docs/reports/leo-working-state-20260709/rich-proposal-creation-plan-mapped-current.md` `docs/reports/leo-working-state-20260709/skill-pack-manifest.json` `docs/reports/leo-working-state-20260709/skill-pack-readme.md` `docs/reports/leo-working-state-20260709/telegram-gateway-handler-canary-current.json` `docs/reports/leo-working-state-20260709/telegram-gateway-handler-canary-current.md` `docs/reports/leo-working-state-20260709/telegram-live-canary-current.json` `docs/reports/leo-working-state-20260709/telegram-live-canary-current.md` `docs/reports/leo-working-state-20260709/telegram-live-db-write-canary-20260709.json` `docs/reports/leo-working-state-20260709/telegram-live-db-write-canary-20260709.md` `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/approve_proposal.py` `scripts/kb_claim_source_contract_preview.py` `scripts/kb_rich_proposal_apply_packet.py` `scripts/kb_rich_proposal_creation_plan.py` `scripts/working_leo_open_ended_benchmark.py` `tests/test_approve_proposal.py` `tests/test_kb_claim_source_contract_preview.py` `tests/test_kb_rich_proposal_apply_packet.py` `tests/test_kb_rich_proposal_creation_plan.py` `tests/test_working_leo_open_ended_benchmark.py`
62 lines
1.8 KiB
Markdown
62 lines
1.8 KiB
Markdown
---
|
|
name: teleo-infra-provenance
|
|
description: Use when tracing Teleo repo/deploy/runtime provenance, preventing path confusion between GitHub, local checkouts, VPS mirrors, live service cwd, and generated report artifacts.
|
|
---
|
|
|
|
# Teleo Infrastructure Provenance
|
|
|
|
## Job
|
|
|
|
Prevent incorrect assumptions about where Leo/Teleo code, runtime state, DB state, and evidence live.
|
|
|
|
## Trigger Phrases
|
|
|
|
- "where is Leo running from"
|
|
- "VPS provenance"
|
|
- "teleo-infrastructure repo"
|
|
- "deploy source"
|
|
- "why /opt/teleo-eval"
|
|
- "what is canonical"
|
|
|
|
## Surfaces To Separate
|
|
|
|
- GitHub/canonical repo truth.
|
|
- Local Codex workspace checkout.
|
|
- VPS live deploy/source mirror.
|
|
- Hermes/leoclean runtime profile.
|
|
- Postgres canonical DB.
|
|
- `kb_stage` proposal ledger.
|
|
- Retained proof artifacts under local `outputs/`.
|
|
- Synced report artifacts under the VPS profile report directory.
|
|
|
|
## Current Known Path Map
|
|
|
|
- Repo-local evidence pack: `docs/reports/leo-working-state-20260709/`
|
|
- VPS deploy/source area: `/opt/teleo-eval/workspaces/deploy-infra`
|
|
- VPS profile reports: `/home/teleo/.hermes/profiles/leoclean/kb_stage/reports/`
|
|
- Live service: `leoclean-gateway.service`
|
|
|
|
## Required Readbacks
|
|
|
|
Before claiming provenance:
|
|
|
|
1. `git -C <path> status --short --branch`
|
|
2. `git -C <path> rev-parse HEAD`
|
|
3. service `WorkingDirectory` and `User`
|
|
4. file checksum if comparing script deployment
|
|
5. latest retained report artifact timestamp
|
|
|
|
## Common Failure
|
|
|
|
Do not say the repo/deploy split is the direct cause of a Leo outage unless evidence ties it to the active failure. The split can be a reproducibility/parity risk without being the immediate runtime cause.
|
|
|
|
## Output
|
|
|
|
Return:
|
|
|
|
- current repo HEADs,
|
|
- dirty state,
|
|
- live service cwd/user,
|
|
- which path owns code changes,
|
|
- which path owns runtime reports,
|
|
- exact stale/provenance risk if any.
|