AI SPACE · SYSTEM DESIGN & DELIVERY
Thirty years designing network, VoIP and IMS systems; the last eight on AI/LLM and voice. These days I write the design document first, hand implementation to AI agents, then verify the result myself before it ships. I do not design and leave.
01 · Why design, now
Plenty of people can code well.
Few can design well.
With AI coding tools, writing code fast is no longer the problem. The problem is on either side of it: deciding what to build and in what structure, and checking that what got built runs the way the design says. That is where vibe-coded systems have broken every time I have seen one.
Add features one prompt at a time and in two or three weeks nobody can touch the code. Unless table design, module boundaries and state transitions are written down first, AI-written code does not stay maintainable.
Running and running correctly are different things. An AI writes tests that its own code passes. Edge values, failure recovery and permission flows need a person to decide the test items and a person to read the results.
What a client hands over is a feature list, not a system. Turning it into entities, flows and operating procedures is the design work, and that is where experience shows.
02 · Order of work
I kept the way I have designed systems for 30 years and changed only who writes the code. Once structure and data model are fixed in a design document, agents with separate roles implement from it. I hold the verification gate.
Needs become entities, states and flows.
A master agent dispatches work against the spec.
Not whether it runs, but whether it runs as designed.
Never code alone.
How the agents are split is design work too. Role split, where a human checks, and what goes to automated tests are decided again for each project. The same setup is not reused everywhere.
03 · Case studies
Client names are left out. Each case covers what the structural problem was and how it was solved.
04 · Services
Design document, code and test report are delivered as one set. Maintenance scope after handover is agreed separately at the quote stage.
Requirements note, design document, test report: each step is confirmed in writing before the next. Meetings only when they are actually needed.
Phase one is a narrow MVP; the rest goes into upgrade items. I do not quote everything up front.
Development vs. operations responsibility, the security level applied and the maintenance scope are written into the quote, so there is no argument later about who owned what.
Working with clients in Korea and abroad. Remote, asynchronous engagement by default; English in writing.
05 · Contact
Email me what you want to build, in whatever shape it is in. I will propose scope and structure first; the quote comes after.