DRABSNARG.
ARCHITECTURE / WORKFLOWS

Follow the signal.

A system is easier to understand when you can see the boundaries, dependencies, and paths between its parts.

These diagrams are deliberately simplified and sanitized. They are educational representations, not confidential network diagrams or proof of a deployed service.

Dante · plant migrationThe order of the remediation, without addressing or device names
  1. 01Audit: who is on which switch
  2. 02Dedicated subnet + static addressing
  3. 03DDM domains + dedicated PTP leader
  4. 04Cross-building pilot group
  5. 05Full plant cutover
Master control · staying on airSimplified playout path during a facility move
  1. 01Crispin automation
  2. 02Cloud playout: Harmonic VOS360
  3. 03Media via Azure, live via SRT
  4. 04Monitoring room watching air
  5. 05Back to on-prem XOS
Jarvis · release gateHow a change becomes a running release
  1. 01Claude Code builds + tests
  2. 02Codex independent audit
  3. 03Unqualified READY only
  4. 04Tag + staged deploy
  5. 05Real-machine go-live checks

Maps are hypotheses until tested.

Each diagram is a starting point for questions about failure modes, ownership, observability, and recovery. Detailed measurements and implementation notes belong in the linked project records.

Explore projects · Read engineering notes