diff --git a/docs/configuration-parity.md b/docs/configuration-parity.md
index b61f8bb..ce4a6f5 100644
--- a/docs/configuration-parity.md
+++ b/docs/configuration-parity.md
@@ -5,7 +5,20 @@ Authority:
 - upstream `cmd/jetstream/main.go` and `internal/jetstreamd/options.go` at
   `f29815c391fc2644f8a3dd36b899fb3697dd1ea6`
 - Stream `eb95c14310ef18c7ab9edbcff991a04a560a7d86`
-  (admitted artifact `sha256:43001041...`, `receipts/eb95c14.json`)
+  (admitted artifact `sha256:43001041...`, `receipts/eb95c14.json`) — this hash
+  resolves, but note experiment 6 deployed `29705cb`
+  (`receipts/29705cb.json`), so the basis is behind the artifact that ran. Same
+  gap recorded in `semantic-parity.md`.
+
+**Flag and environment names are derived, so they are not what needs auditing.**
+Since `ac09654`, a field on the options struct in `runtime/cli.zig` generates
+both spellings at comptime — `backfill_workers` becomes `--backfill-workers` and
+`JETSTREAM_BACKFILL_WORKERS` via `flagName` / `envName`. A canonical name
+therefore cannot silently drift from its environment variable, and a
+`--flag`/`JETSTREAM_*` mismatch is a comptime impossibility rather than an audit
+finding. What still needs a row is the part derivation cannot supply: the
+default value, the parse and validation rules, precedence, and whether the
+parsed value actually reaches the runtime mechanism named in the row.
 
 This document audits public configuration and command wiring. A **verified**
 configuration row proves only that the input is parsed/defaulted and reaches