The Tight Loop
Field test for the Mech Suit Methodology. A combat-log parser, a Godot test game, and a hosted multiplayer network became a working 3D replay viewer in two slices over two days. With the receipts.
Practitioner notes on AI-assisted development, architecture, and integration. Each piece traces back to a specific working artifact: a commit, a load test, a working demo. Receipts over rhetoric.
Field test for the Mech Suit Methodology. A combat-log parser, a Godot test game, and a hosted multiplayer network became a working 3D replay viewer in two slices over two days. With the receipts.
From copy-paste to multi-agent orchestration. Six phases of an AI-paired development workflow, written from lived practice. The AI does not replace your judgment. It amplifies it.
Eight field notes from a real repository. The receipts behind the Mech Suit Methodology, with file-path captions and verbatim artifact quotes.
Four parallel AI-builder streams shipped clean in one night. The pattern that made it possible: context tiers, bootstrap protocol, collaboration loop, automation boundary, human-in-the-loop.
The complete multi-agent build-and-run stack. Cowork desktop for parallel build sessions, Microsoft Agent Framework for runtime agent orchestration, OpenTelemetry as the observability substrate that spans both layers.
A working multi-agent log-analysis pipeline. Three streams under attack, three discrete agents, one cross-stream layer that catches the false-positive trap a single-prompt scanner walks into. No install required.
The desire trace demo as it ran the first day it worked. One form, one trace, one local store. Published unfinished on purpose.
Three standalone sample pages that explain the demo narrative, guardrails, and local restart loop.