docs(adr): the ProDesk is the sensitive tier's host, rehearsed on first (#404) - #405
Merged
Conversation
…st (#404) ADR-0008 needed two machines: a mini PC for the sensitive tier and, under #92, a cold spare for the firewall. Only the spare was ever on the shopping sentence in README.md, and the tier's host lost its tracker the day #102 split into one issue per service. One ProDesk 600 G4 was bought on 2026-09-08 for the spare, in the belief it would host the tier too. ADR-0034 decides it does. It is rehearsed on first, as the firewall spare, then wiped and built as the tier host under #404, and it is the firewall's spare hardware in a disaster at the cost of the tier being down until a replacement arrives — a cost ADR-0023 already accepts. The cold spare is deferred with a stated reopen condition. Six cores and 32 GB also fit the tier's real workload better than the "N100-class" box the docs assumed. README's shopping sentence now names every outstanding purchase; the roadmap's #92, #110 and #102 entries, both runbooks that racked the spare powered off, and hardware.md follow. Refs #92, #102, #404. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ADR-0034 — Run the sensitive tier on the ProDesk, and make it the spare hardware.
ADR-0008 needed two machines and only the firewall spare was ever on the README's shopping sentence; the tier's host lost its tracker when #102 split. One ProDesk was bought on 2026-09-08 for both jobs. This ADR decides it does both, in order: rehearse the firewall restore on it first (the half of #92 that matters), then wipe it and build the tier under #404, and in a disaster it is the spare hardware at the cost of the tier being down until a replacement arrives — a cost ADR-0023 already accepts. The cold spare is deferred with a reopen condition, not bought twice.
Also in this PR
README.md: the top-items sentence names every outstanding purchase (a second drive, the NAS) and says why it used to omit the tier's host.docs/roadmap.md: the Buy a spare ProDesk and rehearse the firewall restore #92, Rack the shelf switch in U4 — buy it with the UPS pack #110 and ADR-0008: the sensitive-tier services and two new firewall rules are untracked #102 entries.restore-the-firewall.md: §3 says the spare is the tier host and step 0 is wiping it; Afterwards says order a replacement the same day; the rehearsal's last step hands the box to Build the sensitive-tier host on the ProDesk (ADR-0034) #404 instead of racking it off.fit-the-ups-battery.mdstep 2 item 4: nothing else racks on the shelf.docs/hardware.md: the box listed as in transit, entering the Compute table when Build the sensitive-tier host on the ProDesk (ADR-0034) #404 builds it.#401, which recorded the same box as the cold spare, is closed unmerged.
Checks:
make check-docs,scripts/lint.sh.Refs #92, #102, #404.
🤖 Generated with Claude Code