Runnable code and reference material behind the posts on vExpose.blog — the wiring behind the strategy: reference architectures, real code, real numbers.
The premise of the blog is simple: state the call a technology leader has to make, then prove it in code, architecture, and benchmarks. This repo is the "prove it" half — every folder maps to a post and holds the code you can actually run.
| Folder | Post | What's inside |
|---|---|---|
agentic-itsm/ |
A Reference Architecture for Agentic ITSM | The deterministic policy gate, a scoped ServiceNow adapter, and least-privilege IaC |
storage-benchmarking/ |
The Benchmark Trap | An honest fio job for enterprise storage |
rag/ |
A Reference Architecture for Enterprise RAG | Grounded retrieval: hybrid search, reranking, a citation guard, and a faithfulness eval |
servicenow-pagination/ |
The ServiceNow REST pagination gotcha | Why offset pagination silently drops records — and the sys_id cursor fix |
terraform/ |
The Terraform Gotcha That Destroys the Resource You Meant to Keep | The count trap, the for_each fix, and a no-downtime state migration |
kubernetes/ |
The Readiness Probe That Turned a Deploy Into an Outage | Shallow readiness + startupProbe + maxUnavailable: 0 vs the rollout death spiral |
pgvector/ |
Your pgvector Search Gets Slower as You Add Data | IVFFlat lists/probes tuning and a recall@k regression gate |
inference/ |
The Inference Bill Is a Memory-Bandwidth Problem | A bandwidth-bound token-cost calculator: decode speed from arithmetic |
ansible/ |
Your Ansible Playbook Says 'changed' Every Run. It's Lying. | Idempotency fixes and a CI gate that fails on a non-converging second run |
iac-guardrails/ |
Operating DNA, Not Templates | A paved-road module + OPA/Conftest policy that blocks non-compliant merges |
latency-benchmarking/ |
Coordinated Omission: Why Your p99 Latency Is Lying | A closed-loop stall demo: naive vs schedule-corrected percentiles |
AI fails in the operating model, not the model. The tool is not the transformation.
The code here is deliberately boring where it needs to be — the guardrail layers are plain, auditable code, not magic.
MIT — use it, adapt it, ship it.