teleo-infrastructure/docs/reports/leo-working-state-20260709/working-leo-apply-readiness-current.md

Working Leo Apply Readiness

Generated UTC: 2026-07-09T22:57:32.369798+00:00 Mode: retained_artifact_readiness_verify Ready for separately authorized production apply packet: True Production apply executed: False Production apply authorization present: False

Checks

• manifest_status_not_executed: True
• apply_order_matches_manifest: True
• rollback_order_matches_manifest: True
• expected_counts_match: True
• all_packet_files_ok: True
• clone_apply_markers_ordered: True
• clone_rollback_markers_ordered: True
• clone_cleanup_db_dropped: True
• service_stable_after_rehearsal: True
• clone_report_says_production_not_modified: True

Packet Files

• production-apply-authorized-commit.sql: ok=True, bytes=38892, sha256=d7c9d06e77571b9751a94fdf49715c9997421f071dc840e65247ea1a0d5c8088
• production-delete-rollback.sql: ok=True, bytes=5803, sha256=297bd9e8b5246e6d9cb4883b15ad9e11e745b220508305f223985be38506bc36
• production-apply-packet.json: ok=True, bytes=7119, sha256=c78107cf0ccf48487f2c80f01623376416e22d2e333262813135b0585fa9336d
• cross-surface-apply-authorized-commit.sql: ok=True, bytes=1366, sha256=381c6dcf178a419cb588d3e57bb63a1f794a03e9d5ff4a9ff3c2d9735a1bdf3f
• cross-surface-delete-rollback.sql: ok=True, bytes=823, sha256=41d10138e6d668426f8601ea5f528d70335ed4d30aae23830a55c0f068f046a8
• cross-surface-packet.json: ok=True, bytes=2365, sha256=7fec3252a833f0e5f4eec8bd60bc2224332500175dfe8e55df5cfa29a747b9bd
• rio-strategy-apply-authorized-commit.sql: ok=True, bytes=6579, sha256=0a219df35db7ea3379c8b232449b5a6b8bd3a0164dd26ee393e55fa997b31463
• rio-strategy-delete-rollback.sql: ok=True, bytes=1185, sha256=f7c6896018ac785fe8214bb4dfbdbf936cb3f91d92dcf877aee80b682dae2d93
• rio-strategy-packet.json: ok=True, bytes=7031, sha256=71bb6a81a631e36d28131b35af9a759f7dd6054729a50c37e92cd8b703f8fa1b
• governance-concept-apply-authorized-commit.sql: ok=True, bytes=6822, sha256=63b1ea56180ddd2308d4a4ca0e2d229ba3fe6cce494d5339339a6f62f1962bba
• governance-concept-delete-rollback.sql: ok=True, bytes=1160, sha256=786e107134a7c502130af9d92f19109184ac936399ac90d62b3b8c07f3e90f65
• governance-concept-packet.json: ok=True, bytes=4044, sha256=081b2bb346349978f13797330966ca4d2d24b0817c66c29dff1064521a5b8924
• helmer-7powers-production-apply-authorized-commit.sql: ok=True, bytes=42770, sha256=9264baa4249432dcdc96510e67cc694bb5f2b2e485b63a3bfee959d31a89104d
• helmer-7powers-production-delete-rollback.sql: ok=True, bytes=5702, sha256=77579ea3efbb3f3a06666f645a2bc662a501c8a3e92d9b389fca044dfef06a2d
• helmer-7powers-production-apply-packet.json: ok=True, bytes=1322, sha256=0a7e419f98711ab11eb7b6e839008d7105e178ec40e864fb37f714bd4bf133e5

Evidence

• Clone log: docs/reports/leo-working-state-20260709/working-leo-integrated-clone-rehearsal-current.log
• Clone report: docs/reports/leo-working-state-20260709/working-leo-integrated-packet-current.md

Claim Ceiling

Ready means the retained packet set is complete, ordered, clone-proven, and cleanly rolled back. It does not authorize or prove production DB mutation.

Not Done

• Production apply still requires explicit operator authorization.
• Live Telegram regression must be rerun after any production apply.
• GCP parity remains separate from this VPS packet-readiness gate.