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

Details

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

2026-07-09 22:56:48 +02:00

3.1 KiB

Raw Blame History

name	description
teleo-kb-db-change-workflow	Use for Teleo KB proposal normalization, approved-to-canonical DB change workflows, clone rehearsals, apply packets, rollback plans, and row-level proof without silently mutating production.

Teleo KB DB Change Workflow

Job

Turn approved KB proposal intent into a strict, reviewable, rehearsed, row-level DB change contract.

Trigger Phrases

"manipulate the knowledge base"
"approved proposal apply"
"canonical DB rows"
"kb_stage to public"
"claim/source contract"
"rollback rehearsal"
"production apply packet"

State Model

Use these states exactly:

proposed: draft or staged proposal text exists.
pending_review: proposal exists but is not approved.
approved: reviewer approved intent; canonical DB may still be unchanged.
applied: canonical row mutation happened and was read back.
not_applied: no canonical mutation exists.
packet_ready_not_executed: SQL packet and rehearsal proof exist, but production was not changed.

Current Table Contract

Core canonical tables used in July 9 work:

public.claims
public.sources
public.claim_edges
public.claim_evidence
public.reasoning_tools

Staging table:

kb_stage.kb_proposals

Required Workflow

Fetch proposal and status from live DB.
Normalize proposal payload into planned rows.
Preserve reviewer/caveat text as source/evidence/proposal body context.
Reject or block unsupported edge types, unknown targets, and schema gaps unless a reviewed mapping overlay exists.
Generate rollback-only SQL first.
Run live rollback rehearsal in a transaction.
Run disposable clone commit rehearsal.
Generate production packet only after clone proof passes.
Do not execute production commit unless explicitly authorized.
If production commit is authorized later, run preflight, commit, postflight, and service stability readback.

Current Important Proposals

00957f6c-9883-4015-95a4-6b09367efb0e: strict add_edge canary, applied.
8dfedb3f-3aa4-4200-970f-4c0016f6869f: live Telegram staged proposal, pending review at the retained snapshot.
14fa5ecc-ac7a-41c1-807d-a2e85b936617: approved rich proposal, mapped subset packet-ready, not production-applied.
ac036c9d-20a0-4ffe-881f-57d6b7bacf22: approved rich proposal, mapped subset packet-ready, not production-applied.
a64df080-8502-42e2-98f4-9bbdecb8da73: approved Helmer 7 Powers proposal, plan generated for reasoning tool plus claims/sources/edges; continue with rehearsal/packet proof.

Claim Ceiling

Clone proof is not production apply. A packet file is not a DB change. Production apply requires explicit authority and postflight row readback.

Validation

Run focused tests after planner/packet changes:

uv run --extra dev ruff check scripts/kb_rich_proposal_creation_plan.py scripts/kb_rich_proposal_apply_packet.py tests/test_kb_rich_proposal_creation_plan.py tests/test_kb_rich_proposal_apply_packet.py
uv run --extra dev pytest tests/test_kb_rich_proposal_creation_plan.py tests/test_kb_rich_proposal_apply_packet.py

3.1 KiB Raw Blame History