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.
When the idle blank timer expires during a locked session, 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.
When the idle blank timer expires during a locked session, 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
Hazard review
- scenarioreviewedconcurrentboundaryedge_caseconcurrency_scale
Worst case: the idle countdown blanks the display while a password check is in flight, hiding the field mid-authentication, or a suspend-frozen timer fires on resume and blanks the freshly woken unlock screen under the user. concurrent: the timer fire interleaves with in-flight authentication, so the gate reads authenticatingPassword only, deliberately excluding the long-lived fingerprint PAM. boundary: the interval+2000ms wall-clock threshold is the frozen-timer detector. edge_case: the post-suspend stale countdown re-arms instead of blanking. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale applied, it is driven by the idle blank timer racing an in-flight password authentication.
- propertynot applicable
Declarative timer policy over two boolean gates; no algebraic or ordering surface beyond the recorded interleaving.
- structuralnot applicable
QML timer plus boolean guards; no memory, encoding, or numeric surface.
- domainnot applicable
In-process QML timer policy; no external call or trust boundary.
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.
- Leonid BugaevApprovedSpec conformanceSep 29, 2026 · 3 days agoREVIEW-260929-AA9F
Re-recorded after the MC/DC annotation campaign shifted lines (idleBlankTimer 590->601). Read the idleBlankTimer handler: it blanks via runBlank only when lockRequested && !authenticatingPassword, so a password check in flight holds the display while the armed fingerprint PAM alone never does; a wall-clock gap (armedAt older than interval+2000, the suspend-frozen countdown) re-arms the timer instead of blanking. All three response disjuncts are reachable, matching the (blank_displays | password_auth_in_flight | timer_rearmed_after_suspend) shape.
Cited code (1) - 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)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
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 | Exempted · defensive — every expired idle timer ends in runBlank, an in-flight password hold, or a post-suspend re-arm; an expiry with none of the three needs a broken handler (reviewed: REVIEW-3) |
| 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.
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 (2)
- LockView.qmlshell/plugins/lock/LockView.qml
- 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.