Windows exposes sleep prevention through power requests, and there are two relevant kinds. System-required tells Windows not to enter sleep. Display-required tells it to keep the panel powered. They are independent, and conflating them is why so many keep-awake tools leave a monitor on for jobs that do not need one.
StayGreen exposes this as a scope choice. The default takes both, which is right for presenting or reading. The system-only scope takes system-required alone, which is right for unattended work: the machine stays up, the display follows your normal timeout, and nothing is kept lit for nobody.
The acquisition order is deliberate and worth knowing if you care about correctness. System-required is taken before display-required and released after it, and if the display request fails to acquire, the system request is unwound rather than left dangling. There is no state in which the app believes it holds something it does not, or half-applies a hold and leaves it that way.
The timer does not tick. A timed session schedules a single wake at the deadline on a monotonic clock rather than polling a counter. When it fires, the hold is released and the state returns to off. That is one scheduled wake for the entire session, however long it is. The same design runs throughout: the per-app rule is driven by an event hook rather than a loop that asks what the foreground window is, and the power, lid, and session signals all arrive as notifications. This is the substantive efficiency claim, and it is a claim about architecture rather than a benchmark — there is no measurement harness in the app, and no CPU or memory figure here is being asserted as measured.
Bounds and precedence. Custom session lengths are whole minutes up to seven days, which is a deliberate ceiling rather than an unbounded field. An armed timed session outranks the per-app rules, so a rule that would otherwise release the hold cannot cut a job short. Hardware safety still applies on top of everything: if you unplug the machine and the battery rule is on, the session pauses, because an unattended job on battery is a different risk than one on wall power.
One honest limitation for unattended work. On hardware that uses Modern Standby, the system can take over on battery regardless of what any application requests. If the job matters, keep the machine on wall power. StayGreen probes for Modern Standby support and shows an advisory rather than letting you discover this at four in the morning.