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.

Local AI · trust boundaryConceptual target architecture — not a claim of deployed remote access
  1. 01Authenticated user
  2. 02Cloudflare Access + Tunnel
  3. 03Private chat interface
  4. 04Local inference service
  5. 05Open-weight model
Broadcast · signal pathIllustrative workflow, not a production network diagram
  1. 01Source / camera
  2. 02Transport: SDI or NDI
  3. 03Production / processing
  4. 04Encoder / delivery
  5. 05Monitoring + diagnostics
Jarvis · release lifecycleSimplified engineering workflow
  1. 01Source + changes
  2. 02Automated checks
  3. 03Versioned release
  4. 04Staged deployment
  5. 05Health verification

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