No dedicated repository. This case documents policy-gate patterns; supply-chain decisions that policy can enforce live in BlastGuard.
Policy as Code Guardrails
A CI turnstile that teaches: versioned policy packs evaluate before promote and return readable remediation — standards without tribal gatekeeping.
Evidence home
Pattern case — proof lives next door.
How it works
Pass the turnstile — or learn why.
Policy as Code Guardrails by Andrey Lesnikov — OPA-style packs in CI that block bad promotes and teach the fix.
-
01
Write policy as code
Rules live in versioned packs — reviewed like any other platform contract.
-
02
Evaluate in CI
The turnstile spins on every PR and image — early, automatic, consistent.
-
03
Deny with a lesson
Failures return remediation humans can act on — not a silent red X.
-
04
Allow and promote
Passing the gate continues delivery without waiting for a tribal approver to wake up.
Evidence
From problem to proof.
How the system is framed, operated, and proven — not a slide deck summary.
CI and admission still disagree: promote decisions rely on tribal review instead of machine-readable policy.
You need zero-trust service identity/mTLS fabric rather than delivery gates — see Zero Trust Service Mesh.
BlastGuard issues supply-chain decisions that policy can enforce. Secrets and Certificate Automation keeps identity material lifecycle-managed.
Developer experience, admission control, exception handling, auditability, and avoiding fragile gatekeeping.
Related
Nearby systems.
Zero Trust Service Mesh
Internal traffic is often trusted by default, making lateral movement and policy gaps hard to see
East-west mTLS by default
GitOps: Argo CD & Flux
Teams need a clear delivery model before GitOps becomes another layer of operational confusion
Delivery as explicit platform contracts
Secrets and Certificate Automation
Manual secret rotation and certificate handling create outage risk and hidden operational debt
Secrets + TLS with a real lifecycle