Architecture

System-level diagrams and philosophy for the data pipelines, AI development pipeline, and cross-repo dependencies.

Architecture pages cover the parts of the stack that don’t belong to a single repo. They sit above the per-category sections and explain how things move — data, code, and decisions.

In this section

Data pipelines

The log and NetFlow ingest paths from the homelab edge to Splunk indexers. UniFi → HAProxy → Cribl Edge → Splunk.

AI development pipeline

The human → issue → AI agent → CI → review → ship flow. How Claude, Gemini, and Copilot fit together.

Principles

• One diagram per concern. Combining a deploy pipeline with a data pipeline shows nothing. Each diagram is allowed to be small.
• Diagrams over prose where structure matters. If a relationship is clearer as a graph, draw it.
• READMEs own install and usage. The docs site owns architecture, philosophy, and cross-repo context.

Where to go next

Infrastructure

OpenTofu modules and the Proxmox stack.

Configuration

Ansible playbooks for host and app config.

Nix Ecosystem

Reproducible dev environments.

Observability

OTEL → Cribl → Splunk.