The archive, mapped
Every blog post and case study on the site with the principles and playbooks each piece argues for. Filter by any principle or playbook to see just the evidence behind it.
Matching the filter
7 items- Repo Design Patterns for AI-Assisted Dev: Control Loops, Hooks, and MemoryFeb 9, 2026 · 6 min
Treat the repository as a control system: versioned instructions, explicit workflows, fast hooks, durable context, and visible failure states.
- Loom: One Registry, Many AI Coding AssistantsFeb 9, 2026 · 7 min
How Loom generates and checks MCP configuration across nine client profiles from one canonical registry.
- Loom Mode: One Proxy, One Daemon, Faster MCPFeb 9, 2026 · 7 min
How Loom keeps MCP tooling predictable with one client entrypoint, daemon-owned process lifecycles, bounded output, and coarse-grained tools.
- Two-Lane Text GPU Allocation: Quality + Vision/Fast (Plus a Media Lane)Feb 9, 2026 · 11 min
A February 2026 GPU allocation experiment: separating text workloads, testing shared-group priorities, and keeping client routes stable as models moved.
How fi-fhir separates feed-specific variance from parsing, semantic events, durable delivery, and workflow policy—and where the pre-1.0 platform still has work to do.
- Standing Up a GPU-Ready Private AI Platform (Harvester + K3s + Flux + GitLab)Dec 29, 2025 · 5 min
Field notes from building and operating a small private GPU platform with Harvester, K3s, and a GitLab -> Flux delivery loop.
How FlexDeck combines Kubernetes, Flux, CI, observability, and model state without hiding freshness, access boundaries, or the limits of a homelab control surface.