teleo/teleo-infrastructure
8
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions 1

Pin Working Leo apply refusal to deployed SHA

Browse source
This commit is contained in:
twentyOne2x 2026-07-13 05:32:20 +02:00
parent cb49ce0e6a
commit 7908120319
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/reports/leo-working-state-20260709/working-leo-production-apply-authorization-verification-current.json
View file

@ -11,10 +11,10 @@
"telegram_visible_post_not_authorized": true "telegram_visible_post_not_authorized": true
}, },
"claim_ceiling": "This verifier only checks whether an authorization string is valid for the current deployed SHA. It does not run SQL, does not mutate production, and does not prove canonical rows were changed.", "claim_ceiling": "This verifier only checks whether an authorization string is valid for the current deployed SHA. It does not run SQL, does not mutate production, and does not prove canonical rows were changed.",
"deployed_sha": "bef10341e9cc31f41cb5fbd0a55119f1766e41fd", "deployed_sha": "a26892ab8195c404657d328b784c7886fef09e6f",
"expected_authorization_text": "I authorize production DB apply for the integrated Working Leo packet set on VPS using deployed commit bef10341e9cc31f41cb5fbd0a55119f1766e41fd in this order: mapped-rich-base, cross-surface-anchor, rio-strategy-context, governance-concept-schema, helmer-7powers. Run preflight immediately before each phase, run the authorized apply SQL, run every postflight, run the non-posting direct-claim regression and scorer, capture service and cleanup readbacks, validate the production receipt, and do not post Telegram-visible messages unless separately authorized.", "expected_authorization_text": "I authorize production DB apply for the integrated Working Leo packet set on VPS using deployed commit a26892ab8195c404657d328b784c7886fef09e6f in this order: mapped-rich-base, cross-surface-anchor, rio-strategy-context, governance-concept-schema, helmer-7powers. Run preflight immediately before each phase, run the authorized apply SQL, run every postflight, run the non-posting direct-claim regression and scorer, capture service and cleanup readbacks, validate the production receipt, and do not post Telegram-visible messages unless separately authorized.",
"fresh_deployed_sha_required": false, "fresh_deployed_sha_required": false,
"generated_at_utc": "2026-07-13T01:37:29.621659+00:00", "generated_at_utc": "2026-07-13T03:31:14.369906+00:00",
"mode": "authorization_verification_only", "mode": "authorization_verification_only",
"next_action_if_verified": [ "next_action_if_verified": [
"Re-run production preflight immediately before each packet phase.", "Re-run production preflight immediately before each packet phase.",

6
docs/reports/leo-working-state-20260709/working-leo-production-apply-authorization-verification-current.md
View file

@ -1,12 +1,12 @@
# Working Leo Production Apply Authorization Verification # Working Leo Production Apply Authorization Verification
Generated UTC: `2026-07-13T01:37:29.621659+00:00` Generated UTC: `2026-07-13T03:31:14.369906+00:00`
Mode: `authorization_verification_only` Mode: `authorization_verification_only`
Status: `missing_authorization_text` Status: `missing_authorization_text`
Safe to enter apply window: `False` Safe to enter apply window: `False`
Production apply executed: `False` Production apply executed: `False`
Production apply authorization present: `False` Production apply authorization present: `False`
Deployed SHA: `bef10341e9cc31f41cb5fbd0a55119f1766e41fd` Deployed SHA: `a26892ab8195c404657d328b784c7886fef09e6f`
Operator identity: `` Operator identity: ``
## Checks ## Checks
@ -22,7 +22,7 @@ Operator identity: ``
## Expected Authorization Text ## Expected Authorization Text
I authorize production DB apply for the integrated Working Leo packet set on VPS using deployed commit bef10341e9cc31f41cb5fbd0a55119f1766e41fd in this order: mapped-rich-base, cross-surface-anchor, rio-strategy-context, governance-concept-schema, helmer-7powers. Run preflight immediately before each phase, run the authorized apply SQL, run every postflight, run the non-posting direct-claim regression and scorer, capture service and cleanup readbacks, validate the production receipt, and do not post Telegram-visible messages unless separately authorized. I authorize production DB apply for the integrated Working Leo packet set on VPS using deployed commit a26892ab8195c404657d328b784c7886fef09e6f in this order: mapped-rich-base, cross-surface-anchor, rio-strategy-context, governance-concept-schema, helmer-7powers. Run preflight immediately before each phase, run the authorized apply SQL, run every postflight, run the non-posting direct-claim regression and scorer, capture service and cleanup readbacks, validate the production receipt, and do not post Telegram-visible messages unless separately authorized.
## Next Action If Verified ## Next Action If Verified