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.
While the session is locked and the idle blank timer expires, the lock service shall blank the displays only when no password authentication is in flight.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
While the session is locked and the idle blank timer expires, the lock service shall blank the displays only when no password authentication is in flight. The armed fingerprint PAM shall not hold the display lit. When wall-clock time shows the timer froze through a suspend, the service shall re-arm the timer instead of blanking.
when idle_timeout_expired the lock_service shall always satisfy (blank_displays | password_auth_in_flight | timer_rearmed_after_suspend)
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
A countdown frozen by suspend fires right after resume and would blank the freshly woken unlock screen under the user. The fingerprint PAM stays armed for the whole lock, so gating on the combined authenticating state would keep the panel lit until unlock.
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
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-3
Idle-blank decision matches the disjunction: displays blank only when no password authentication is in flight; the armed fingerprint PAM path does not hold the display, and after resume the timer is rearmed. All three response disjuncts are reachable in the code's timer handler.
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 idle_timeout_expired the lock_service shall always satisfy (blank_displays | password_auth_in_flight | timer_rearmed_after_suspend)
Witnesses· 4 scenarios total
- lock-blank-fingerprint-test.sh:1exercises 4 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| # | blank_displays | idle_timeout_expired | password_auth_in_flight | timer_rearmed_after_suspend | Result | Proves | Covering test |
|---|---|---|---|---|---|---|---|
| 1 | F | F | F | F | T | idle_timeout_expired | |
| 2 | F | T | F | F | F | blank_displays | — |
| 3 | F | T | F | T | T | timer_rearmed_after_suspend | |
| 4 | F | T | T | F | T | password_auth_in_flight | |
| 5 | T | T | F | F | T | blank_displays |
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)
- Service.qmlshell/plugins/lock/Service.qml
Tests to re-run (1)
- lock-blank-fingerprint-test.shtest/shell.d/lock-blank-fingerprint-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.