<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Adr on vanityURLs</title><link>https://vanityurls.link/en/tags/adr/</link><description>Recent content in Adr on vanityURLs</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Fri, 05 Jun 2026 11:50:57 -0400</lastBuildDate><atom:link href="https://vanityurls.link/en/tags/adr/index.xml" rel="self" type="application/rss+xml"/><item><title>Architecture decisions belong with the code</title><link>https://vanityurls.link/en/blog/architecture-decisions-in-the-code-repository/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://vanityurls.link/en/blog/architecture-decisions-in-the-code-repository/</guid><description>&lt;p&gt;A setup page should tell an operator what to do.&lt;/p&gt;
&lt;p&gt;It should not carry the full history of why the Worker, installer, schema, release automation, and runtime security rules have their current shape. That history still matters. It belongs beside the implementation.&lt;/p&gt;
&lt;p&gt;vanityURLs keeps product-level decisions as architecture decision records in the code repository. The public docs stay operational. The code repo keeps the rationale that future maintainers will need when the next change looks obvious but is not.&lt;/p&gt;</description></item></channel></rss>