Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Omarchy Instant: deploy a signed image instead of installing file by file
Reported by josephjacks · filed Aug 28, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
I wanted to know if Omarchy could be put onto a blank NVMe in under seven seconds.\n\nTrying to make the installer 270x faster is the wrong approach. An installer resolves packages, unpacks thousands of files, runs hooks and builds the machine one file at a time. Omarchy Instant does that work ahead of time and writes a finished signed image directly to disk.\n\nCurrent result:\n\n- 6.829779 seconds to deploy the test image to a fresh virtual NVMe\n- Secure Boot into the verified image\n- 10 of 10 tampered artifacts rejected\n- 10 separate builds produced identical output\n- 8 of 8 interrupted GPT writes left the expected disk state\n- unsigned UKI and corrupted base images did not boot\n\nThe full claim is not proven yet. The current image is a small test system containing the pinned Omarchy source. It is not yet the complete 9.5 GiB Omarchy and Hyprland desktop, and the timing came from a VM rather than physical PCIe 4 NVMe.\n\nSource and proof: https://github.com/josephjacks/omarchy-instant\n\nI wrote the spec and built this with Perplexity Computer. I want the Omarchy team to pick the machine and NVMe for the full test. I will run it at least ten times, cut power at the dangerous points and publish everything, including failures.\n\nJoseph Jacks
View raw text
I wanted to know if Omarchy could be put onto a blank NVMe in under seven seconds.\n\nTrying to make the installer 270x faster is the wrong approach. An installer resolves packages, unpacks thousands of files, runs hooks and builds the machine one file at a time. Omarchy Instant does that work ahead of time and writes a finished signed image directly to disk.\n\nCurrent result:\n\n- 6.829779 seconds to deploy the test image to a fresh virtual NVMe\n- Secure Boot into the verified image\n- 10 of 10 tampered artifacts rejected\n- 10 separate builds produced identical output\n- 8 of 8 interrupted GPT writes left the expected disk state\n- unsigned UKI and corrupted base images did not boot\n\nThe full claim is not proven yet. The current image is a small test system containing the pinned Omarchy source. It is not yet the complete 9.5 GiB Omarchy and Hyprland desktop, and the timing came from a VM rather than physical PCIe 4 NVMe.\n\nSource and proof: https://github.com/josephjacks/omarchy-instant\n\nI wrote the spec and built this with Perplexity Computer. I want the Omarchy team to pick the machine and NVMe for the full test. I will run it at least ten times, cut power at the dangerous points and publish everything, including failures.\n\nJoseph Jacks
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 09:48 UTC