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 derive the wait budget from the logind InhibitDelayMaxUSec property.
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 derive the wait budget from the logind InhibitDelayMaxUSec property. It shall reserve one fifth of the window but at least 1000 ms for logind. It shall fall back to 5000 ms when reading the property fails, and cap the result at 12000 ms. When the caller passes an argument that is not a positive integer within the cap, the script shall ignore it and use the derived budget.
when suspend_imminent the sleep_lock shall always satisfy budget_bounded & budget_fallback_on_invalid
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
The shipped drop-in raises the inhibitor window to 15 s, but only logind knows the active value. A hand-raised window must not strand a closed laptop in a bag.
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 23, 2026, 17:20 UTC · Kimi Dogfood · AI agent
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-7
Budget derivation matches: InhibitDelayMaxUSec is read, one fifth (>=1000 ms) is reserved for logind, and an invalid/unreadable property falls back to 5000 ms — budget_fallback_on_invalid. Tested with zero-window and not-a-number/99999999 scenarios.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
1 obligation · 1 discharged
Browse the catalogueBehavior at limits, thresholds, and edge-of-range values.
- nominalrequiredpresentCovered by 1 test
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 budget_bounded & budget_fallback_on_invalid
Witnesses· 3 scenarios total
- run_sleep_lockexercises 3 condition scenarios
MC/DC truth table· 5 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| # | budget_bounded | budget_fallback_on_invalid | suspend_imminent | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | suspend_imminent | |
| 2 | F | F | T | F | suspend_imminent | Exempted · defensive — the deadline is always assigned from the validated argument, the derived logind window, or the 5000 ms fallback; no path leaves it unset (reviewed: REVIEW-7) |
| 3 | F | T | T | F | budget_bounded | Exempted · defensive — the fallback IS the 5000 ms bound; taking the fallback and ending unbounded is structurally absent (reviewed: REVIEW-7) |
| 4 | T | F | T | F | budget_fallback_on_invalid | |
| 5 | T | T | T | T | budget_bounded |
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.