01 · Start with the system
Understand the whole environment
We map users, goals, data, constraints, interfaces, permissions, and failure conditions before deciding what role a model should play.
02 · Make behavior observable
Build for evaluation
Actions, state, and decision boundaries should be visible enough for domain experts and engineers to test what the system is actually doing.
03 · Fit the environment
Choose technology in context
Model, memory, infrastructure, and deployment choices should reflect the project's hardware, privacy, performance, integration, and maintenance realities.