Method

01

Audience

Start with something familiar, follow the hidden machinery, and see what failure means for a person using it. The expandable operator notebook keeps the deeper mechanism, safe commands and diagnostic checks close at hand.

02

Curriculum

The rotation is broad on purpose. Neglected fundamentals cause expensive surprises while fashionable tools are busy renaming their configuration fields.

• Linux internals
• TCP/IP
• DNS
• BGP and routing
• Kubernetes
• Observability
• Incident response
• AWS and cloud infrastructure
• IAM
• TLS and PKI
• systemd
• eBPF
• Containers
• CI/CD
• Terraform and infrastructure as code
• Supply-chain security
• Vulnerability management
• SRE reliability math

03

Evidence

Stable mechanisms come from primary documentation. Current claims require direct release notes, standards, maintainers, or vendor advisories. Every public source stays in the edition ledger. Hypothetical examples state their assumptions and follow three to five causal steps. We explain what could prevent the outcome, without inventing dramatic timelines.

04

Pictures that teach

Each article has four large hand-drawn scenes and at least three smaller teaching cartoons. Stick characters, ink, pencil and spare cyan and amber carry the mechanism. Metaphors are labeled; consequential facts remain readable page text.

Validation: Every edition must pass the content schema, source rules, illustration checks, three-question review and publication gates.

05

Corrections

Corrections are appended to the dated edition with a new revision time. Older days are not silently rewritten. A cleaner mistake is still a mistake.

06

Automation

The existing daily task runs in America/Chicago. It writes a candidate, validates the merged archive, builds the exact source, and deploys only after every gate passes. A failed run leaves the previous public version in place.