Decisions

Decision records capture the reasoning behind a real engineering choice, stated with the alternative that was rejected and the evidence that settled it. They are the counterpart to the notes: a note shows how something works, a decision record shows why it was built this way. Every record here refers to a choice this site (or its deployment) actually made and can be traced to a source.

A static file tree served directly by the edge, with no application tier drawn.

The site is served as a static tree, not by a dynamic application server

ADR — static artifacts over application servers, with a narrow, nameable boundary.

A pin marked on a version list for the theme and the generator.

Pin the vendored theme and the generator version

ADR — reproducible builds from a pinned generator and a vendored theme.

Two complete directory trees, the new one steps in as the served name.

Publish by exchanging complete directories, never file-by-file

ADR — atomic publication by renaming directories, never patching a live tree.