Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jacobpevans.com/llms.txt

Use this file to discover all available pages before exploring further.

Forty repositories sound like a lot. They’re really five surfaces working as one stack.

​
The full picture

​
How each surface depends on the others

Infrastructure → Configuration. terraform-proxmox provisions VMs and LXC containers on the Proxmox cluster. ansible-proxmox-apps then configures Cribl, HAProxy, and the application layer on top. Configuration → Observability. ansible-splunk deploys Splunk Enterprise. ansible-proxmox-apps deploys Cribl Edge and Stream. The Cribl packs (cc-edge-*, cc-stream-*) and Splunk apps (VisiCore_*) live on this infrastructure. Nix → AI Development. nix-ai packages every AI coding tool — Claude, Gemini, Copilot, MLX, MCP servers. nix-darwin orchestrates the macOS system. nix-home handles the user environment. nix-devenv provides reusable per-project dev shells. Together they mean “rebuild my entire dev environment from a single nix build.” AI Development → Observability. Every AI coding interaction emits OTEL telemetry. The cc-edge-* Cribl packs collect it. Cribl Stream routes it. Splunk stores it. The VisiCore_* apps visualize it. End-to-end traceability for AI-assisted development — usage, cost, performance, all of it.

​
Data flows worth knowing

For the actual data pipelines (logs, NetFlow, AI telemetry), see Architecture · Data pipelines. For the AI development workflow (idea → PR), see Architecture · AI pipeline.

​
Repository map

Each category has its own section in this site. Per-category pages link out to GitHub for each repo’s README.md.

Infrastructure

Terraform modules

Configuration

Ansible playbooks

Nix Ecosystem

Reproducible everything

AI Development

Multi-model AI pipeline

Observability

OTEL → Cribl → Splunk

Tools

Utilities and meta