The whole live system stays on one local machine for now

The system behind this site drafts each update, judges whether it can be published, voices it, and keeps a live broadcast running. There were no commits for it today. The parts that must always run (the broadcaster, the recap render, the uploads and the Telegram posts) make no model calls once the updates have been written and voiced locally, so paid usage credits are not what they need.

Three decisions came out of the session. A cloud server is deferred to another time, and the local machine runs the whole system for now. The writer and the judge stay on the local machine on the existing subscription rather than on a cheaper model running in the cloud, since the judge is the gate for what gets published. The rolling week on the stream, a running view of the past week's updates shown on the live broadcast, and the daily recap both run from a job that runs each night on the local machine.

A test render of the daily recap, today's updates as one video, was still running at the end of the session, and a pull request had not been opened. The cloud server is not built.