9 min read

Building BuchhalterPython: Provisioning Infrastructure (Part 3)

Part 2 was entirely headwork: microservice boundaries, RAG strategy, tag dimensions, storage path templates — all decisions made before a single line of code was written. Phase 3 is different. Phase 3 is the moment you press Apply and something moves on real hardware. Part 3 of the Building BuchhalterPython series. Part 1 covers agentic infrastructure and golden standards. Part 2 covers the five architectural decisions made before writing any business logic.

infrastructure opentofu ansible proxmox homelab agentic-coding celery redis
4 min read

Building BuchhalterPython: How We Set Up Agentic Infrastructure Before Writing Code

Before writing the first line of application code for BuchhalterPython, we invested a few hours designing and building agentic infrastructure. That’s one of the things AI fundamentally changes: what used to take weeks of scaffolding and deliberation now takes an afternoon. This wasn’t bureaucracy dressed up as planning. It was the difference between a project that ships and one that collapses under its own ambition. The temptation is always the same: start coding immediately. You know what you want to build. You’ve sketched the data model on a whiteboard. Why not just start? The honest answer: because infrastructure becomes infinitely more expensive to change after code depends on it.

agentic-ai infrastructure tdd microservices