diff --git a/docs/credential-lane-designs/nk-bind-executor-go-live.md b/docs/credential-lane-designs/nk-bind-executor-go-live.md
index a54842d..d02a30c 100644
--- a/docs/credential-lane-designs/nk-bind-executor-go-live.md
+++ b/docs/credential-lane-designs/nk-bind-executor-go-live.md
@@ -40,7 +40,7 @@ delivered to KeyCape by ESO, and read natively by the executor through CCR-2026-
 
 - **G1, before step 5 (mint).** The founder accepts case `nk-bind-executor-approval` (owner and
   founder), and net-kingdom commits
-  `security-case-types/oidc-service-client/examples/nk-bind-executor-approval.yaml` with
+  `security-cases/nk-bind-executor-approval.yaml` with
   `status: materialized` and `acceptance: {at, record, by: [{role: owner}, {role: founder}]}`. The
   broker refuses anything else (`case_not_materialized`, `case_source_validation_failed`); a synthetic
   copy with exactly that shape passed the broker's case check on 2026-11-04.
@@ -144,7 +144,7 @@ CCR-2026-0043), not the platform-admin envelope.
 cd /home/worsch/railiance-platform
 export BAO_ADDR=http://127.0.0.1:18200 VAULT_ADDR=http://127.0.0.1:18200
 unset BAO_TOKEN VAULT_TOKEN
-CASE=/home/worsch/net-kingdom/security-case-types/oidc-service-client/examples/nk-bind-executor-approval.yaml
+CASE=/home/worsch/net-kingdom/security-cases/nk-bind-executor-approval.yaml
 grep -q '^  status: materialized$' "$CASE" && echo case-materialized
 REF="nk-bind-executor-approval@sha256:$(sha256sum "$CASE" | cut -d' ' -f1)"
 bao login -no-print -method=oidc -path=netkingdom role=credential-broker-keycape-client-secret-generate