DevStation Engineering
Bilingual notes on how DevStation is designed, tested and operated. The goal is to document real decisions with enough context to be useful beyond the project.
Day 0: Why DevStation?
A personal origin story — from an AMD Geode running BrazilFW that bonded two home internet links, and a Pentium 4 game server, to a single self-contained CLI that describes a homelab once and rebuilds it on demand. Why DevStation is a CLI, what a station is, and how an agent can drive the whole thing over MCP.
Designed for extensibility: the technical decisions behind DevStation
Hexagonal, tactical DDD, CQRS, internal events and JSON-RPC contracts. Why a set that can sound like overengineering became the central bet — and what the evidence on AI and complex code has to say about it.
Testing through MCP: running the suite against a real homelab
The end-to-end suite drives a real Proxmox node over MCP — provision, install, uninstall, destroy — so an agent can run and explore the CLI like a QA. Notes on big refactors, the cross-OS Windows validation, and test discipline with AI.