diff --git a/docs/adr/ADR-001-request-binding.md b/docs/adr/ADR-001-request-binding.md
index 239410d..2480547 100644
--- a/docs/adr/ADR-001-request-binding.md
+++ b/docs/adr/ADR-001-request-binding.md
@@ -26,7 +26,7 @@ So the two most ordinary REST shapes — `GET /roles/{id}` and
 `HandlerFunc` and hand-write the decode, the validation call, the encoding and the
 status. This is a **correctness** problem, not only ergonomics: `HandlerFunc` is the
 single path by which a handler reaches production without `v.Struct(req)` ever
-running. Two failure modes followed, both observed in a consumer (`kch-core-svc`):
+running. Two failure modes followed, both observed in a downstream service:
 
 1. **Unvalidated bounds** — a list endpoint that forgets to clamp answers
    `?per_page=99999`; the validator that would refuse it is not in the code path.
@@ -73,8 +73,9 @@ validates the assembled struct once with the `valid.Validator` already in scope.
 There is no `header:` tag, in this version or a later one. Headers are middleware's
 concern (authentication, request identity, tenancy). A `header:` tag would make one
 specific mistake ergonomic — filling a tenant/actor identifier from a value the
-client fully controls — which `kch-core-svc`'s own ADR-007 forbids. Reducing that
-mistake to one word in a struct tag would make it likely rather than merely possible.
+client fully controls, exactly the boundary a service's own authorization rules
+exist to defend. Reducing that mistake to one word in a struct tag would make it
+likely rather than merely possible.
 
 ## Options considered