The internet leaves your desk at nine and comes back at noon

A university blocks the exam container's network so students can't cheat. You block your own so you can't check the news.

Once: PUT /api/v1/containers/{id}/network with type: block. Then two hoody-curl schedules in a small second container, because a blocked container can't serve the request that blocks it: POST /network/start at 09:00 and POST /network/stop at 12:00, weekdays. Block mode is a service you start and stop; the policy stays saved in between.

Your writing desk still renders. The display and editor URLs come through the proxy, which block mode doesn't touch. Localhost works. The browser panel gets nothing. Between nine and noon the machine you write on has no outside.

The proctor and the student are the same person. The warden is a schedule in another container.

You can't open a tab you can't reach.