slosars.me · member

Anthony “Tony” Slosar

Lab Manager, version 4 30 September 2026

Every feature names the check that proves it, or says why it has none

A Claude Code agent runs the home network day to day under a written rule sheet, and Tony decides anything destructive.

  • Every listening port, scheduled job, credential and device is listed, and a check fails when the lab disagrees with its list.
  • A change that adds a feature with neither a check nor a reason is refused before it is committed.
  • All 183 checks run every hour, and one that fails twice in a row reaches Tony without anyone starting it.

Its rule sheet requires it to report what it measured, never what it intended.

Every register is checked against the live lab Four stations in a loop. Declare: 33 listening ports registered, and every job, credential and device. Check: 183 checks that can fail, run every hour, and 44 test suites. Show: 9 operations planes drawn from their source, 147 features indexed with their gaps counted. Tell: a single alert engine that sends the phone one line per alert. A new component adds a register row, and each failure reaches a plane. Measured on 2026-09-30. 01 DECLARE 33 listening ports registered and every job, credential and device 02 CHECK 183 checks that can fail 44 test suites prove the scripts 03 SHOW 9 planes drawn from their source 147 features indexed, gaps counted 04 TELL 1 alert engine behind every notice each alert is one line on the phone a new component adds a register row each failure reaches a plane Every register is checked against the live lab. Measured on 2026-09-30