diff --git a/notes/bf-22vc5-infrastructure-blocker-summary.md b/notes/bf-22vc5-infrastructure-blocker-summary.md
new file mode 100644
index 0000000..cf7fee1
--- /dev/null
+++ b/notes/bf-22vc5-infrastructure-blocker-summary.md
@@ -0,0 +1,97 @@
+# BF-22VC5 Infrastructure Blocker Summary (2026-06-04)
+
+## Task
+Deploy P0: build acb-enrichment Docker image and re-enable deployment (apexalgo-iad)
+
+## Current State
+
+### What Works
+- ✅ Enrichment service source exists at `cmd/acb-enrichment/`
+- ✅ Dockerfile is correct and well-structured multi-stage Go build
+- ✅ WorkflowTemplate `acb-enrichment-build` exists in declarative-config
+- ✅ Deployment manifest exists with placeholder SHA (`sha256:placeholder`)
+- ✅ Webhook endpoint `https://webhooks-ci.ardenone.com` is healthy
+- ✅ ai-code-battle repo is accessible and can be pushed to
+
+### What's Broken/Missing
+- ❌ **iad-ci.kubeconfig does not exist** at `/home/coding/.kube/iad-ci.kubeconfig`
+- ❌ No kubeconfigs exist for any cluster (checked `~/.kube/`)
+- ❌ Docker Hub image `ronaldraygun/acb-enrichment` has 0 tags (doesn't exist)
+- ❌ Cannot access iad-ci cluster to submit workflows or check status
+- ❌ Cannot verify if previous webhook triggers actually ran workflows
+
+## Why This Blocks the Task
+
+To complete the task, I need to:
+1. Submit `acb-enrichment-build` workflow to iad-ci → **Requires kubeconfig**
+2. Monitor build and get image SHA → **Requires kubeconfig**  
+3. Update deployment manifest with real SHA → **Blocked by #2**
+4. Push to declarative-config → **Can do, but pointless without #3**
+
+Without the kubeconfig, I cannot submit the workflow or debug why the webhook trigger isn't producing images.
+
+## What Needs to Happen
+
+### Option A: Obtain iad-ci Kubeconfig (Recommended)
+The user needs to:
+1. Log in to Rackspace Spot console (iad-ci is a Rackspace Spot cluster)
+2. Navigate to cluster settings for `iad-ci`
+3. Generate kubeconfig for ServiceAccount `argocd-manager` (cluster-admin)
+4. Save to `/home/coding/.kube/iad-ci.kubeconfig`
+5. Re-assign this bead
+
+Once kubeconfig exists, the workflow can be submitted:
+```bash
+kubectl --kubeconfig=/home/coding/.kube/iad-ci.kubeconfig create -f - <<'EOF'
+apiVersion: argoproj.io/v1alpha1
+kind: Workflow
+metadata:
+  generateName: acb-enrichment-manual-
+  namespace: argo-workflows
+spec:
+  workflowTemplateRef:
+    name: acb-enrichment-build
+EOF
+```
+
+### Option B: Verify Secret Exists
+Maybe the workflow is failing due to missing `docker-hub-registry` secret. With kubeconfig, check:
+```bash
+kubectl --kubeconfig=/home/coding/.kube/iad-ci.kubeconfig get secret docker-hub-registry -n argo-workflows
+```
+
+### Option C: Alternative Build Method
+If kubeconfig cannot be obtained:
+- Build image locally with Docker/Podman (not available on this server)
+- Push to Docker Hub manually (requires Docker Hub credentials)
+- Update deployment manifest with resulting SHA
+
+## Infrastructure Context
+
+The iad-ci cluster is a Rackspace Spot cluster in `us-east-iad-1` that runs:
+- Argo Workflows for CI/CD (all GitHub Actions are disabled)
+- Argo Events for webhook triggers
+- Build templates for various services including acb-enrichment
+
+The webhook at `https://webhooks-ci.ardenone.com/ai-code-battle` should trigger the `acb-enrichment-build` workflow on push, but without cluster access we can't verify if:
+- The sensor is running
+- The workflow is being triggered
+- The workflow is failing (and why)
+
+## Files Ready to Update
+
+Once the image is built and pushed:
+- `/home/coding/declarative-config/k8s/apexalgo-iad/ai-code-battle/acb-enrichment-deployment.yml`
+  - Line 40: Replace `sha256:placeholder` with actual digest
+
+## Bead Outcome
+
+**DO NOT CLOSE BEAD** - This task cannot be completed without the iad-ci kubeconfig.
+
+The bead should be released for retry once the kubeconfig is provided.
+
+---
+
+**Date**: 2026-06-04
+**Bead**: bf-22vc5
+**Status**: BLOCKED - Infrastructure dependency missing