I'm Joseph Tracy, an infrastructure engineer in Seattle with over two decades running enterprise systems end to end: scale-out NAS and SAN storage, Linux and Windows Server, virtualization, campus networking, and the identity and collaboration platforms sitting on top of all of it. Most of that time I have worked at the failure end, as the escalation point a hard problem routes to when the frontline is out of moves, which is a different education from building something once and handing it over.
Automation came out of that work rather than alongside it. Bringing hundreds of wireless access points onto a network, or large numbers of IP video cameras into one system, is the kind of job that stops being possible by hand somewhere around the third rack, and the scripts that made those deployments repeatable are the same instinct behind what I build now: the check that should have run before the job started, the snapshot that should have been taken before the config changed, the timing history that turns "it feels slow" into a measurement. Each one ships tested, documented, and with its source.
Everything here is built and tested on my own time, against public documentation and my own lab. This site is where that work happens in public.
The shared reliability plumbing extracted from my monitoring scripts: dependency preflight, locking with guaranteed cleanup, temporary directories that cannot leak, structured logging, and retry with backoff. Not a framework. A library with exactly the functions its two consumers earned.
A Python watcher, standard library only, that connects to a list of live TLS endpoints, verifies each certificate as this host's Python and OpenSSL would, and reports days to expiry against a warning threshold. A completed run prints a row for every endpoint, and an endpoint it cannot vouch for, including one it cannot reach, counts as a finding.
A Bash auditor that reads, without changing, the mounts visible in its current Linux mount namespace and compares them with a reviewed manifest: source, filesystem type, options that must be present, and options that must never appear. It reports every mismatch in one run, refuses a manifest it cannot trust, and prints a candidate manifest from a known-good host.
A pair of service-state read-only tools for a failed systemd service. One captures a private evidence bundle with a manifest and a per-command outcome record. The other reads that bundle and writes a review report that states what was observed and leaves the conclusion to a person.
Nine findings a cause line tends to absorb, how to list competing explanations before testing them, why the most persuasive evidence often rules nothing out, and the conclusion record a later reader can check, worked through one constructed certificate incident.
A title formula with ten rewrites, what each ticket field holds and what to keep out of it, one constructed incident written two ways, five situations that pressure a ticket's wording, and the questions a reviewer asks before the status says resolved.
Local timestamps with no offset fail in measurable ways: an hour that happens twice, an hour that never happens, a four hour outage that subtracts to three, and a sort that rearranges a timeline. Every output block comes from a script you can run, with the recording layers that show what to record or check to avoid, detect, or qualify each failure.
Who detects a failed automation platform, what it does when it cannot establish authority, which identities it runs under, and what happens to the work it missed.
Part two of two. What each postmortem claim costs in evidence, how to state a finding plainly once the review earns it, what to write instead of a finding about a person, and how to record prevention, action items, and residual risk so the document stays accurate after it leaves the room.