Cloud as worker, not owner
Use the strongest model when it earns the cost, but do not let the provider become the only policy engine, logbook or stop path.
Series 002 · local-first AI control
The cloud can do the work. It should not own the off switch.
I am not anti-cloud. I am anti single point of obedience. The serious pattern is local policy, cloud capability where useful, and a stop path that belongs to the operator.
Local witness before local hero
A small local model does not need to beat the frontier model. It needs to witness, sanity-check and keep the operator informed when the cloud route fails.
Memory is a governed tool
Good memory is selective, sourced and reversible. Stuffing everything into context is not memory; it is clutter with confidence.
Physical stop paths still matter
When software touches real systems, a human-owned boundary outside the model is not paranoia. It is engineering.
Human owner→Local policy→Cloud worker→Verifier→Approved action
That is the public-safe map. The private implementation details stay private. The point is the shape: the worker does not grade itself and the stop path is not inside the thing being stopped.