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/working-leo-authorized-apply-runbook-current.md
twentyOne2x 23b1c87ac0
Some checks are pending
CI / lint-and-test (push) Waiting to run
Details
Add Working Leo direct-claim benchmark and apply runbook 
Generate ready-not-executed operator runbook for the integrated apply packet set.

Extend Cory-style benchmark with no-context direct-claim prompts and expected follow-ups.

Refresh retained reports and tests for the 20-prompt mixed-evidence score.
2026-07-10 01:14:39 +02:00

5.5 KiB
Raw Blame History

Working Leo Authorized Apply Runbook

Generated UTC: 2026-07-09T23:12:00.028604+00:00 Mode: operator_runbook_generation_only Status: ready_not_executed Ready for authorized operator: True Production apply executed: False Production apply authorization present: False

Authorization Boundary

Do not run apply commands unless the operator explicitly authorizes production DB apply for the integrated Working Leo packet set in dependency order.

Checks

  • readiness_passes: True
  • readiness_says_not_executed: True
  • readiness_says_not_authorized: True
  • apply_order_matches_manifest: True
  • rollback_order_matches_manifest: True
  • all_phase_files_exist: True
  • all_phase_files_non_empty: True
  • all_apply_and_rollback_sql_have_transactions: True

Preflight Order

  1. mapped-rich-base -> production-preflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/production-preflight.sql
  2. cross-surface-anchor -> cross-surface-preflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/cross-surface-preflight.sql
  3. rio-strategy-context -> rio-strategy-preflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/rio-strategy-preflight.sql
  4. governance-concept-schema -> governance-concept-preflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/governance-concept-preflight.sql
  5. helmer-7powers -> helmer-7powers-production-preflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/helmer-7powers-production-preflight.sql

Apply Order

  1. mapped-rich-base -> production-apply-authorized-commit.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/production-apply-authorized-commit.sql
  2. cross-surface-anchor -> cross-surface-apply-authorized-commit.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/cross-surface-apply-authorized-commit.sql
  3. rio-strategy-context -> rio-strategy-apply-authorized-commit.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/rio-strategy-apply-authorized-commit.sql
  4. governance-concept-schema -> governance-concept-apply-authorized-commit.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/governance-concept-apply-authorized-commit.sql
  5. helmer-7powers -> helmer-7powers-production-apply-authorized-commit.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/helmer-7powers-production-apply-authorized-commit.sql

Postflight Order

  1. mapped-rich-base -> production-postflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/production-postflight.sql
  2. cross-surface-anchor -> cross-surface-postflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/cross-surface-postflight.sql
  3. rio-strategy-context -> rio-strategy-postflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/rio-strategy-postflight.sql
  4. governance-concept-schema -> governance-concept-postflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/governance-concept-postflight.sql
  5. helmer-7powers -> helmer-7powers-production-postflight.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/helmer-7powers-production-postflight.sql

Rollback Order

  1. helmer-7powers -> helmer-7powers-production-delete-rollback.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/helmer-7powers-production-delete-rollback.sql
  2. governance-concept-schema -> governance-concept-delete-rollback.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/governance-concept-delete-rollback.sql
  3. rio-strategy-context -> rio-strategy-delete-rollback.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/rio-strategy-delete-rollback.sql
  4. cross-surface-anchor -> cross-surface-delete-rollback.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/cross-surface-delete-rollback.sql
  5. mapped-rich-base -> production-delete-rollback.sql
    • psql "$TELEO_DATABASE_URL" -v ON_ERROR_STOP=1 -f docs/reports/leo-working-state-20260709/production-delete-rollback.sql

Expected Counts After Apply

  • claim_concept_map_links: 1
  • claim_edges: 18
  • claim_evidence: 34
  • claim_governance_gate_links: 2
  • claims: 12
  • concept_maps: 1
  • cross_surface_anchor_updates: 1
  • helmer_ledger_rows_marked_applied: 1
  • reasoning_tools: 1
  • rio_strategy_anchors: 5
  • rio_strategy_nodes: 2
  • sources: 28

Post-Apply Required Actions

  • Run every postflight SQL file and retain output.
  • Rerun live Telegram regression canaries after production postflight.
  • Record production apply receipt, row counts, service MainPID/NRestarts, and cleanup readback.

Claim Ceiling

This runbook is proof that the authorized apply sequence is explicit and ordered. It does not execute SQL, does not mutate production, and does not replace explicit production apply authorization.