Skip to content

The Atarus series

Foundations: the captures.

Every command output printed in Foundations is a captured run. This page lists each one with its run id and hashes, so anyone can check that a printed block is the run we recorded.

Front cover of Foundations I, The workbench and how computers talk.Front cover of Foundations II, Identity, access and where things run.Front cover of Foundations III, The tester's method and the report.

What a capture is

A real run, printed in full.

A capture is one command run on the bench edition the chapter names, in the order the chapter gives, with its complete output recorded by the harness. The book prints that output with a run id beneath it. Nothing in a printed output was typed by hand.

Before a block is printed, addresses and keys are replaced with fixed placeholders. The raw run stays on the capture host and is never published. When a correction changes an output, we run the capture again; we never edit an output by hand.

Run ids and hashes

How a block is named and checked.

Run id

r-20261031-ch01-03

The letter r, the date of the run, the chapter and the step within it. The id above is chapter 1, step 3, run on 31 Oct 2026.

Raw hash
SHA-256 of the output as the terminal produced it, before any placeholder went in. It proves the run existed without publishing it.
Printed hash
SHA-256 of the block exactly as the book prints it, header line included. This is the one to check a printed block against.
Each entry also records
The command, its exit code, the UTC time of the run, the bench edition, the host architecture and hypervisor, and the terminal width. No entry carries raw output.

The manifest

The public manifest for Foundations.

Published on this page as captures.json, generated from the same capture records the book build reads, so the two cannot drift.

Not yet published

The manifest publishes with the first volumes, and the table of runs appears here.

Seed scripts

The seed scripts, coming with the PDF.

A seed script builds one chapter's piece of Wrexby on the bench and takes it away again with --remove. Each is printed in full in Appendix B with its SHA-256. The downloads, with their checksums, are published here with the PDF.

  • ch02-seed.sh

    Chapter 2. The Wrexby price list incident: the shop folder and service, the shop and vendor accounts and their groups.

    Coming with the PDF

  • ch04-seed.sh

    Chapter 4. The warehouse backup problem: a week of orders files, the nightly backup script, its schedule and the warehouse account.

    Coming with the PDF

  • ch05-seed.sh

    Chapter 5. The order service as the network change left it, and one hosts line for orders.wrexby.lab.

    Coming with the PDF

  • ch06-seed.sh

    Chapter 6. Wrexby's internal name list and the agency's ticket, with the names added to the bench's hosts file.

    Coming with the PDF

Every seed script runs as root on your bench. Read it before you run it, as chapter 2 shows.