KAIM / Notes
A compact library of engineering decisions around AI systems, agents, MCP, production architecture and software delivery. Narrow enough to reuse; concrete enough to challenge.
Agents need release engineering, not just better prompts
A practical model for turning agentic coding from an impressive demo into a controlled delivery loop with context, evidence and human-owned releases.
Archive
05 notesUAT is not the end of development
What resolving 112 client-reported UAT issues taught me about treating acceptance as a production-design feedback loop, not a release gate.
Treat MCP as an operational contract
Why MCP integrations become more useful when you design them like production interfaces: narrow capabilities, explicit trust boundaries and observable tool calls.
Browser memory is a product feature
Large enterprise tables do not become fast because the component library is fast. The data contract, query shape and rendering strategy have to agree.
Deployment time is part of system design
A release process that requires repeated manual RDP work is not merely inconvenient. It changes how often and how safely the system can evolve.
Keep machine integration behind an application contract
MES software should model the state it needs from machines without letting PLC-specific details leak across the rest of the application.