diff --git a/docs/adr/ADR-006-kysely-contained-inside-db-adapter.md b/docs/adr/ADR-006-kysely-contained-inside-db-adapter.md
index 336327b..7c117e0 100644
--- a/docs/adr/ADR-006-kysely-contained-inside-db-adapter.md
+++ b/docs/adr/ADR-006-kysely-contained-inside-db-adapter.md
@@ -3,8 +3,9 @@
 - Status: Accepted
 - Date: 2026-08-31
 - Deciders: platform stream
-- References: ADR index (section 70), ADR-001, ADR-005, Architecture wiki
-  (sections 1, 4, 9), Engineering-Standards wiki (sections 24, 25, 57)
+- References: ADR index (docs/adr/README.md, section 70), ADR-001, ADR-005,
+  Architecture wiki (sections 1, 4, 9), Engineering-Standards wiki
+  (sections 24, 25, 57)
 
 ## Context
 
@@ -50,7 +51,7 @@ where the adapter lives — it is contained, not distributed, and the containmen
 is a package-level rule, not a type-level one.
 
 The decision text — **Kysely contained inside DB adapter** — matches the ADR
-index entry (ADR-006, section 70).
+index entry (ADR-006, section 70 of `docs/adr/README.md`).
 
 ## Alternatives
 
@@ -111,7 +112,8 @@ index entry (ADR-006, section 70).
 - Revisit this ADR when a non-adapter package demonstrably needs
   query-builder features that cannot be expressed through the adapter/port
   API, and there is evidence (per the architecture review gates, ADR index
-  section 68) that the boundary costs more than containment saves.
+  §68 of `docs/adr/README.md`) that the boundary costs more than containment
+  saves.
 - Revisit if the platform grows additional data stores or engines (shared with
   the ADR-005 revisit trigger): a second engine may need its own contained
   adapter, and the query-builder containment rule would extend per adapter.