git diff treats moved code as delete here, add there — 200 lines of churn for a simple refactor.runtime.py:223, you're counting hunks like a Victorian clerk.
The clean way to serve browser screens from a Python API is not to start from a frontend framework, a backend framework pattern, or a generic client registry. It is to start from the data shape that crosses the wire.
You know that moment when a repo has tidy folders called frontend, backend, contracts, and build... and then someone imports build from production code because the file was right there?
Yeah. The folder names were never the boundary.
| #!/usr/bin/env -S uv run --script | |
| # /// script | |
| # requires-python = ">=3.11" | |
| # dependencies = [ | |
| # "ollama>=0.1.0", | |
| # ] | |
| # /// | |
| """Probe an Ollama model and log what it supports using the local API. | |
| This script requires `uv` to be on the path. |
The clean way to build Open Data Contracts defined Python pipelines is not to start from a framework, a registry, or a mutable runtime context. It is to start from the actual computation.
The path to effortless systems begins before debugging.
You do not get 無為 from clever incident response. You get it by designing a system whose intended shape can still be recognised when it is under stress.
That means designing with invariants.
An invariant is not a test assertion and not a hopeful comment. It is a truth the system is built to preserve.