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.
A 2019 article on job shop scheduling with Google OR-Tools, written from inside a 24/7 manufacturing operation — republished verbatim with a 2026 coda. Same three constraints, same CP-SAT solver, different shop: the machines are now GPUs, the jobs are AI agents, and setup time (loading a model into VRAM) is the constraint that decides everything. Receipts included: 250 jobs, 3 model loads, zero missed deadlines.
A local MCP gateway for Claude Code on a Windows machine with an NVIDIA GPU: every tool call logged to a queryable ledger, a local model on tap for the grunt work, and a test gate at every step. ~90 minutes from nothing to receipts. Includes the traps that cost us real hours.
The enterprise architecture that actually gets used is smaller and humbler than a binder — a handful of document formats in tools you already know, plus the one command that makes them a habit. The formats that kept earning their place, and why the notes that help you remember turn out to help an agent operate the system cold.
A debugging methodology for when AI tells you it can't be done. Three patterns — persona-shifted critics, structured pushback, predictive self-critique — from one hard night of multi-card GPU debugging on consumer Windows. Four open-weights frontier labs running on the same box by morning.
I commissioned an adversarial AI review of my own code — instructed to find every defensible reason to dismiss it. It accused me of not writing the code. Why that was the most useful thing it could do — and why I published the review, unedited.
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.
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.
A spread-order bug surfaced in two seconds because the in-product trace overlay made the contract violation visible. The case for logs over tests when an agent builds in unfamiliar tech.
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.
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.
Eight field notes from a real repository. The receipts behind the Mech Suit Methodology, with file-path captions and verbatim artifact quotes.