Discussion about this post

User's avatar
The Grove Foundation, Inc.'s avatar

"Open weights running on three companies' servers is not sovereignty" — this framing extends one layer up. Most organizations building agentic workflows right now are doing it inside a single vendor's SDK. Open weights, open model, proprietary orchestration. The routing logic, the state management, the tool-call patterns all accumulate at the vendor's address. If the architecture of participation gets defined only at the model and infrastructure layers, the SDK layer above quietly recaptures everything won below, on a much shorter timescale than the data center layer would.

Your point about needing "an orchestrator not just for agents but also for models" is exactly the gap. That orchestrator needs to belong to nobody, the same way the addressing layer of the web had to belong to nobody. Until then, open weights run through a proprietary harness is the new AOL: connected, but not federated.

No posts

Ready for more?