[Gerrrt]

Three machines and a mounting kit were delivered on 2026-09-15: the Lenovo
ThinkServer TS150 that is smaug (#413), the HP ProDesk 600 G4 Micro that is
trinity (#404), the Intel DC S3520 240 GB that boots the NAS, and the 5.25"
bracket and double-sided tape that carry it in the optical bay.

docs/hardware.md is the estate's only inventory and it said all four were in
a delivery van. This corrects that, and nothing else.

What did not land

Still paid for and still moving, and recorded that way: the two Exos X20 18 TB
drives for smaug's mirror, the I226 card, the pfSense installer stick, the
CRS326, the A1437 cell for prometheus, and the two SM863a SSDs for Saruman.

So neither build is unblocked. #413 waits on the two Exos drives; the #404
rehearsal waits on the I226 card and the installer stick — and, as of this
commit, no longer on the box.

What this deliberately does not do

• No row enters the Rack or Compute tables. Each bullet names its own
  promotion trigger and none has fired. network.md and architecture.md are
  untouched for the same reason — and check_compute_table would have failed a
  premature row rather than merely tolerated it.
• No row moves on the buy table. Arriving is not buying, so it stays at two
  rows and README stays at "two items now, one later".
• No ADR is edited. ADR-0038 decides a record is superseded rather than
  rewritten, and an arrival amends no decision — including ADR-0038's own line
  saying the TS150 is in transit.
• No measurement is recorded. Every box is unopened. Each bullet gains a
  Checked on arrival, not assumed list instead, in the shape the CRS326 bullet
  already used: serials, CPU and RAM off POST rather than off a listing,
  smartctl -a on the boot disk before the install, and how many of the TS150's
  four bays came with a caddy. No serial or part number is invented here.

The one thing worth doing today

If trinity's 512 GB SSD is a 2.5" drive rather than M.2, its carrier and the
I226 card contend for the same slot. That was an unknown about a box in a van
and is now an unanswered question about a box in the room — and the card has not
shipped. Opening the ProDesk now is the difference between a return and a part
that fits nothing.

Two pre-existing errors fixed in passing

• roadmap.md's Plan and build the NAS on VLAN 40 #95 paragraph said the boot disk was bought "leaving only a
  bracket to carry it in the optical bay". The bracket was bought 2026-09-11,
  which the same section says fourteen lines in.
• The PBS bullet had the TS150 in transit.

Verification

make validate passes, make check-docs reports 10 assertions green, and all
six linters pass. The first local validate run tripped the known promtool
flake under a busy docker daemon and passed on the rerun.

Refs #413 #404

🤖 Generated with Claude Code

---

Second commit: the assertion count was stale (8bd33bf)

Unrelated to the delivery, found while verifying it, and kept here rather than
split because it is four lines of plumbing and a sentence.

README said "Six assertions" while check_docs.py registers ten, and
the enumeration beside it named four of them — ADR numbering, firewall posture,
guest claims and the buy list were all running and unmentioned. ADR-0026
recorded the count as seven when it was written, so it has been wrong at least
twice.

It drifted silently because check_counts() had no claim pattern for the noun
assertions — the exact failure that check's own comments say it exists to
prevent, about itself. So:

• The count is now asserted, not hand-maintained. main() writes
  len(checks) into the facts dict after building the registry;
  check_counts reads it. Adding an eleventh check updates the claim on the
  way in.
• Proven both ways: with the pattern added and README untouched, the run
  failed README.md:71 claims Six assertions; the repository has 10; with a
  temporary eleventh check registered, claims Ten assertions; the repository has 11.
• README is corrected to ten, enumerates all of them, and says it was
  wrong — a bullet advertising that this repo catches documentation drift is
  worth less if it quietly fixes its own.
• ADR-0026's "seven assertions" is left alone. ADRs are outside PROSE on
  purpose, being records of what was true when written.