From 981cd4139b30319070b763f74d556256d01b3a37 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 31 Aug 2026 17:52:25 +0200 Subject: [PATCH] Reference the record rather than link across repositories A relative link out of this repository resolves nowhere on a forge. Every other reference here names the record in prose. --- examples/modules/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/modules/README.md b/examples/modules/README.md index 947718c..1c129bc 100644 --- a/examples/modules/README.md +++ b/examples/modules/README.md @@ -57,7 +57,7 @@ edge, and they are here as a **pair** because that is the only way to see the ha the private network. Neither manifest names an address, and that is what lets the same pair work on any mesh. -**`s3-bucket` names the protocol, not the product** ([ADR 0027](../../../hq/02-DECISIONS/)). A +**`s3-bucket` names the protocol, not the product** (novox/hq ADR 0027). A consumer's code is written against the S3 API, and swapping one store for another does not break it — so the coupling is to S3. A database is the other case: an application is written against PostgreSQL or against SQL Server, so those provisions name the engine.