v11.1.3 download not yet authorized
Lights Out v11.1.3 passed full Reality Gate validation, but publishing it is a separate, owner-only decision that hasn't happened yet. No download link is shown until that authorization exists.
Lights Out · In proof
Local-first night control for Windows. Plan tonight's session on your PC, control it from bed with the Android Companion, and wake with First Light. Compatible smart lights, schedule automation, an experimental Wi-Fi Guard, and proof of every run.
Lights Out v11.1.3 is a Reality-Gate-verified, unsigned Windows portable build. The artifact has a SHA-256 hash and a Reality Gate proof bundle. It is not code-signed yet, so Windows may show warnings.
One screen decides how the night ends — and you can change your mind at any point.
Tonight turns a power action into a session. Pick how long is left, pick what the PC does when the time comes — shutdown, sleep, restart, hibernate, or log out — and either use a Night Mode or start from scratch.
The Android companion runs over your local network — pair it once, then steer Tonight from bed.
Start the session, change the duration, switch the PC action, pause, snooze, or cancel — without getting back out of bed. The companion shows live remaining time, reconnects across LAN changes, and keeps working while the desktop app hides in the tray.
The companion controls Tonight. It does not control smart lights, Wi-Fi Guard, or the proof ledger — those stay on the desktop in this build.
The night doesn't end when the PC goes to sleep — Lights Out schedules the morning too.
First Light is a real wake alarm. Set a time in the app, and Lights Out registers it with Windows Task Scheduler so the PC can wake from sleep on its own. When it wakes, the app runs a rising First Light sequence — a gradual, warm start instead of a cold alert.
Two supporting systems round out the routine: a Bedtime Reminder that nudges you before bed (on by default, 15 minutes before), and Autopilot Bedtime, which learns your pattern and offers to start the session — off by default until you turn it on.
A wake time in the app becomes a real scheduled wake event.
Task Scheduler wakes the machine from sleep or hibernate at the set time.
A gradual brightening sequence runs, followed by the morning briefing.
The Devices panel is a live summary of everything Lights Out can see and talk to.
Open Devices and you get the current state of the whole setup in one place: what this PC will do, whether the companion is connected, and which integrations are configured. Each card routes straight into the matching settings.
Smart Lights and Wi-Fi Guard live here as real, configured-or-planned cards: Smart Lights and Wi-Fi Guard each show their armed state — never a silent promise that they are active when they are not.
Dry Run mode shows here when armed.
Control Tonight from bed once paired.
Discovers nearby Lights Out peers on your network — not remote household control.
Hue or HTTP integration set up in Settings.
Experimental router, webhook, or adapter control.
Compatible lights can dim and warm as the bedtime session progresses — attached to the session, not on their own schedules.
Smart Lights join the session lifecycle. As the timer runs, configured lights can dim toward a warm color temperature where the fixture supports it, and switch off when the session ends — part of the same wind-down you started on the PC.
Independent per-light schedules — “Bedroom lights off at 11:00 PM, kitchen at 11:30” — are not part of this build. Light behavior is tied to the PC session tonight.
Dim and warm as the countdown progresses, when the fixture supports color temperature.
Lights off with the session's end, or follow the Night Mode you chose.
Nothing arms without a passing test connection. Configuration changes disarm it.
Philips Hue and generic HTTP webhooks are the exposed integrations in this build.
Wi-Fi Guard can put the network to bed with you — through supported router and webhook integrations.
Wi-Fi Guard restricts internet access as part of the bedtime flow — one more reason to actually log off. It supports TP-Link, ASUS, and Netgear routers, custom webhooks, and a local Wi-Fi-adapter fallback, and it restores access when the session ends or is cancelled.
TP-Link, ASUS, and Netgear paths are implemented and selected per router.
A custom HTTP(S) webhook can trigger your own network control.
Disabling the local Wi-Fi adapter works without any router at all.
Access is restored when the session ends, is cancelled, or a recurring schedule is no longer active.
Lights Out can start from more than a button — several real scheduling systems give the night a shape.
The Schedule screen is where the week gets predictable. It brings together everything that makes a routine stick:
One honest boundary: these systems are independently scheduled, not one saved whole-room timeline. “Kitchen lights dim at 11:00, Wi-Fi off at 11:30, PC sleeps at midnight” as a single plan is future direction — not current copy.
“Shut down at 10:40 PM” instead of “in 45 minutes.”
Multiple independent rules: at this time, on these days.
Live calendar events inform sessions and the morning briefing.
First Light, Autopilot Bedtime, Bedtime Reminder, and Content Blocker are each scheduled in their own settings.
Automated power actions shouldn't leave you guessing. The Proof screen records the session, and the receipt stays on your machine.
Every session produces a real record: what ran, which action, the outcome — including when you cancelled or changed course. Session history and a full ledger stay in the app, and Morning Proof surfaces the last run's results the next morning.
The system has the power; you keep the controls.
Everything that touches the machine is designed to be interruptible. Before anything runs you confirm it; while it runs you can always stop it.
Lights Out v11.1.3 passed a full Reality Gate Runroom validation on the exact candidate artifact below. This is proof of validation, not a public release — see "What this does not claim" further down.
Lights Out v11.1.3 (source commit c6736ec2, artifact SHA-256 CC3AB6A7...) passed a full Reality Gate Runroom validation: 20 of 20 steps, cryptographically signed receipt independently verified GREEN, real physical Samsung Galaxy S23 companion automation, 0 provider operations, 0 real power actions. This is a Reality-Gate-verified, unsigned Windows portable build -- it is not code-signed, and it is not a re-verification of the earlier, separately frozen v11.1.2 GitHub release ZIP (which remains blocked from anonymous GitHub access for unrelated account-level reasons). Public release awaits separate owner authorization.
cfb87394-5d3c-4763-aa66-b89500b858f7) passed all 20 of 20 validation steps against this exact artifact and source pairing.8b917a70-0a2d-4b57-82b2-113e9ea6fbad) is kept only as evidence of a validation-targeting issue that was found and fixed — it does not count as a passing result and is never cited as one.Before running any Lights Out download, confirm its hash matches exactly:
Expected artifact SHA-256:
Expected Reality Gate proof bundle SHA-256 (optional, for the proof bundle archive if it is published alongside the artifact):
If the hash doesn't match exactly, do not run the file — download again or contact the project.
This build is not Authenticode-signed. Windows may show a "Windows protected your PC" / unrecognized-publisher warning when you run it. No trusted-publisher claim is made, and no SmartScreen reputation is claimed. Please verify the SHA-256 hash above before running the download.
Honest about what is not ready yet.
Lights Out v11.1.3 passed full Reality Gate validation, but publishing it is a separate, owner-only decision that hasn't happened yet. No download link is shown until that authorization exists.
The earlier v11.1.2 release and frozen ZIP exist in the publisher's authenticated GitHub control plane, but an external account-level restriction currently makes the owner, repository, release, and asset return 404 to anonymous visitors. This is unrelated to, and unaffected by, the v11.1.3 Reality Gate proof above.
Desktop app runs on Windows 10 and Windows 11. The Android companion (Companion v11.1.1) lets you start, pause, snooze, cancel, and switch Night Modes from bed. No macOS or Linux build in this cycle.
Smart Lights setup covers Philips Hue and HTTP webhooks today. Wi-Fi Guard is experimental and depends on router or webhook support. Neither supports independent per-device schedules in this build.
Lights Out v11.1.3 is Reality-Gate-verified, but the download is not live yet — publication requires a separate, owner-authorized publish/deploy decision.
Once publication is authorized, this section will link to Lights-Out-Portable-v11.1.3-win-x64.zip and its Reality Gate proof bundle. Verify SHA-256 CC3AB6A78D08A6AE17092F0DC79A3EC5F916B7A6CEB27B16307698A62F94ADD3 before running the downloaded file, extract it into its own folder, and launch Lights Out.exe from the extracted folder — do not run it inside the ZIP. This Windows build is unsigned, so SmartScreen or an Unknown Publisher warning may appear.
Because the build isn't code-signed yet. Windows shows this warning for any unsigned executable, regardless of how it was tested. Verify the SHA-256 hash above before deciding whether to proceed.
No. It's an unsigned Windows portable build. Code signing is a separate, tracked piece of future work, not something this release claims.
It means this exact build passed a full, real, 20-step automated validation pipeline — including packaged-app checks and live physical-phone companion automation — and produced a cryptographically signed, independently verified proof receipt. It does not mean the file is digitally signed, and it has no effect on Windows SmartScreen.
No. This build is not a GitHub release. Distribution here is provider-neutral by design.
Run the Get-FileHash command in the Release status & evidence section above and compare the result to the published SHA-256. If they don't match exactly, don't run the file.
No. The Android Companion app remains at version 11.1.1 in this release; only the Windows desktop app moved to 11.1.3.