Runs the channel in real time
- Plays video and live sources at the correct moment.
- Executes daily playlists and fixed-time events.
- Renders graphics through TitleBox.
- Creates system and As-Run logs.
- Uses its own deterministic recovery features.
Simple project overview
ATHENSA remains the machine that actually plays the channel. Hermes becomes the careful operations layer above it—preparing schedules, checking files, watching what happened, and asking for help when a decision could affect the broadcast.
The basic idea
The project is not trying to replace ATHENSA. It is trying to reduce repetitive human work around ATHENSA without making the on-air path less reliable.
What we want to achieve
The ideal result is simple: prepare the channel early, catch mistakes before airtime, let ATHENSA play it, and know quickly when reality differs from the plan.
Where we have reached
We understand the copied software and the observed playlist format well enough to build and test safe tools. The remaining boundary is acceptance by a licensed, running ATHENSA system.
Manuals, modules, logs, recovery options, and automation surfaces were mapped.
The copied v7 programs and local help were inspected without running them.
The planner grid, program-name slots, real playlist grammar, candidate generation, validation, and safe staging are mapped.
A licensed ListBox/AirBox test must prove that the generated file is truly accepted.
What is proven—and what is not
Suggested next steps
The next phase should happen on a licensed but non-live test setup. One calm test is worth more than ten confident guesses.
Safety rule
Real-time timing stays inside ATHENSA. Hermes prepares work early, validates it, watches logs, and follows approved recovery procedures. Production deletion, untested restarts, and direct on-air schedule changes remain disabled until the test evidence says otherwise.
Production-readiness gate