docs: set ubuntu docker deployment policy

AGENTS.md

@@ -31,6 +31,10 @@ Use Python 3.10+ and 4-space indentation. Keep modules, classes, functions, and
 
 Use `pytest`. Cover domain validation, SQLite/CSV data import-export behavior, DOE generation, and model or API behavior as those layers are added. Name tests after the unit under test, for example `tests/test_material.py` or `tests/test_store.py`. Prefer small, deterministic tests and use temporary files or in-memory SQLite for persistence tests.
 
+## Deployment Environment
+
+Production deployment and model training target the Ubuntu server. Prefer Docker as the deployment and training runtime so the scientific Python stack, CUDA-free CPU dependencies, and filesystem paths remain reproducible across machines. Use `uv.lock` as the dependency source of truth and avoid compiling native binaries unless a required dependency has no compatible wheel. Direct Ubuntu deployment with `uv sync` is acceptable only when a lightweight host environment is explicitly required.
+
 ## Commit & Pull Request Guidelines
 
 No Git history exists yet, so use concise, imperative Conventional Commits such as `feat: add material schema` or `docs: update architecture report`. Pull requests should describe the change and motivation, link related issues or project tasks, include verification commands and results, and add screenshots for visible report changes.