A design correction I think is important enough to make explicit: **FounderOS currently has mechanisms for planning work and for governing agent execution. But there must be a governed work-allocation decision between those two things.** Planned work is not automatically agent work. I had been treating these as neighboring problems: **work planning → governed agent execution** I now think that skips a necessary boundary: **work observation / planning → responsibility → authority → execution-modality selection → execution** The missing question is: > **Who or what should actually perform this work—and does it require an agent at all?** That decision should occur _before_ an agent is instantiated or delegated authority. A model or council may help classify the work, estimate difficulty, identify dependencies, critique a plan, or propose an executor. But those outputs are evidence, not authority. The system should separately determine: * what work actually exists, * whose organizational responsibility it falls under, * what authority would be required, * and only then the minimum necessary execution modality. A legitimate result may be deterministic software, a human action, a narrowly bounded agent, or a governed composition of them. So the architecture I am working toward is no longer: **plan work → give work to an agent → govern the agent** It is: **govern work → allocate work → then, only when justified, govern agent execution** I’m calling this allocation layer GWS. The distinction sounds small, but I think it changes the default assumption behind agentic systems: **the existence of work does not imply the existence of an agent.** I’d be interested in counterexamples or prior architectures that already make this boundary first-class.