Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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-system-sleep-lock shall request the session lock before it calls the clamshell reconciliation helper.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
omarchy-system-sleep-lock shall request the session lock before it calls the clamshell reconciliation helper.
when suspend_imminent the sleep_lock shall always satisfy lock_requested_before_clamshell_sync
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
A stuck Hyprland IPC call during a lid transition must not consume the lock window before Quickshell has begun securing the session.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- in_review
- Reviewer
- Kimi Dogfood · AI agent
- Reviewed
- Sep 12, 2026, 23:50 UTC
History
- Created
- Sep 12, 2026, 19:43 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 12, 2026, 23:32 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewederror_handlingedge_case
Worst case: a stuck Hyprland IPC call during a lid transition consumes the lock window before Quickshell begins securing the session, so the machine suspends unlocked. error_handling: the reconciliation helper is bounded at 0.4s with kill-after and its failure is absorbed, so a stalled IPC cannot consume the budget. edge_case: the lid transition that temporarily stalls Hyprland IPC is exactly the trigger condition, and the ordering requirement is what keeps it from pre-empting the lock request. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, it orders two steps inside one suspend; rapid repeated suspends are stated on SYS-REQ-260912-HC86.
- propertynot applicable
A single ordering statement between two calls; no algebraic or repeated-application surface beyond the sequence itself.
- structuralnot applicable
Two sequential bash calls; no memory, encoding, or numeric surface.
- domainnot applicable
The clamshell call deadline is bounded in-code and its budget ownership lives with FAWV and HC86; no additional domain class applies to the ordering statement itself.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Kimi Dogfood · AI agentApprovedSpec conformanceSep 12, 2026 · 3 weeks agoREVIEW-6
Ordering guarantee holds: the session-lock request is issued before the clamshell reconciliation helper is called; code order matches lock_requested_before_clamshell_sync.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
FRETish formula
when suspend_imminent the sleep_lock shall always satisfy lock_requested_before_clamshell_sync
Witnesses· 2 scenarios total
- run_sleep_lockexercises 2 condition scenarios
MC/DC truth table· 3 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | lock_requested_before_clamshell_sync | suspend_imminent | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | suspend_imminent | |
| 2 | F | T | F | lock_requested_before_clamshell_sync | — |
| 3 | T | T | T | lock_requested_before_clamshell_sync |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
No findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Files to re-check (1)
- omarchy-system-sleep-lockbin/omarchy-system-sleep-lock
Tests to re-run (1)
- sleep-lock-test.shtest/shell.d/sleep-lock-test.sh
What this rests on
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.