3.1 KiB
Proposal Apply Production Authorization Packet
Generated UTC: 2026-07-15T02:08:10.775963+00:00
Required tier: T6_authorized_production
Current tier: T3_live_readonly
Safe to enter apply window: False
Production apply authorized: False
Production apply executed: False
Exact Binding
- Proposal:
9b2b5fa4-0e0d-5db0-aa4d-6fd102889946(approve_claim) - Proposal payload SHA-256:
6fba5e8e105a28dfaf5733ff7c9f85a20d31d653add0bc4a0f81e4b08de803af - Apply payload SHA-256:
c89bc03ce7714f325293329a0bf95eaba0a56c596ef021d731b48dab0447c684 - Immutable approval SHA-256:
310b54030e26ed43d7226f2e803610586e80d21ff064c67e11ea21e93ef40bd9 - Destination:
teleo-pg/teleo - Destination system identifier:
7649789040005668902 - Apply engine SHA-256:
ca2c0a0c1031393c95a26102d57339654d2363f4c51cdf39aabb9071d0ca6c26 - Apply engine path:
scripts/apply_proposal.py - Apply SQL SHA-256:
1a7d65870e415ee8891b6dd84732a29bcee00412c10862d3d1db4b191a8ade38 - Clone rehearsal rollback SQL SHA-256:
ef2464a6802426509333861cf0768ca64184901ab7bd2030529e7356a35d9cb3 - Production rollback status:
not_generated - Production rollback SQL SHA-256:
None - Approval gate prerequisite SHA-256:
bdf8c5da05eed10665b05ad1e331e3c9c8d72464c59889a3cf8f34ab23822faa - Approval gate prerequisite path:
scripts/kb_apply_prereqs.sql - Binding SHA-256:
6f1984f3a69ad049d4bbcc408ed2542dc5f081806ec9baa9a35c8959e5dab62a
Production Preconditions
approval_gate_ready:Falsedestination_readback_observed_at_utc:2026-07-15T02:07:27.133665+00:00destination_readback_was_read_only:Trueexact_production_rollback_packet_ready:Falsematching_candidate_count:0production_apply_authorization_present:Falseproduction_apply_executed:Falsestrict_proposal_present_and_approved:False
Approval Gate Readback
apply_role_present:Trueapprove_function_present:Falseassert_function_present:Falsefinish_function_present:Falseimmutable_approval_table_present:Falsereview_role_present:False
Exact Action-Time Authorization Text
This text is not actionable until every production precondition above is true.
I authorize one production DB apply for proposal 9b2b5fa4-0e0d-5db0-aa4d-6fd102889946 with payload SHA-256 6fba5e8e105a28dfaf5733ff7c9f85a20d31d653add0bc4a0f81e4b08de803af to Docker container teleo-pg, database teleo, system identifier 7649789040005668902, binding SHA-256 6f1984f3a69ad049d4bbcc408ed2542dc5f081806ec9baa9a35c8959e5dab62a. I also authorize conditional production rollback SHA-256 <PRODUCTION_ROLLBACK_SQL_SHA256> only if the bound postflight fails and no downstream dependency exists. Do not send Telegram, mutate another proposal, expose Cloud SQL, or promote GCP. Operator <OPERATOR_IDENTITY>; received ; expires .
Current Gate
deploy and independently verify the immutable approval gate before selecting a production proposal
The production approval-gate deployment is explicitly outside this apply packet and requires separate authorization.
Claim Ceiling
T2 clone lifecycle plus T3 destination readback; no production apply authorization or execution