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 target user has no enrolled fingerprint or /usr/bin/fprintd-list is not executable, omarchy-apply-lock shall remove /etc/pam.d/omarchy-lock-fingerprint.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the target user has no enrolled fingerprint or /usr/bin/fprintd-list is not executable, omarchy-apply-lock shall remove /etc/pam.d/omarchy-lock-fingerprint. When an enrolled fingerprint exists, the helper shall install the PAM fingerprint stack.
when fingerprint_not_enrolled the apply_lock shall always satisfy fingerprint_pam_removed
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
A stale fingerprint PAM stack without an enrolled finger would offer an authentication path that can never succeed and can shadow the password path.
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 30, 2026, 06:51 UTC · Leonid Bugaev
Hazard review
- scenarioreviewederror_handlingboundaryedge_case
Worst case: a stale fingerprint PAM stack without an enrolled finger offers an authentication path that can never succeed and shadows the password path. error_handling: a missing or non-executable fprintd-list, or a failed probe, routes to the removal branch, the fail-safe direction. boundary: the enrolled/not-enrolled threshold is the grep on probe output feeding the if/else. edge_case: on a multi-user host the system-wide stack is keyed to one target user enrollment, so another user without enrolled fingers meets a failing fingerprint option; the password path stays intact and the lock service retries then falls back, so the residual is confusion and delay, not a lockout.
- propertynot applicable
Single-branch installer derived from probe state; rerunning the helper reproduces the same branch, and there is no other algebraic surface.
- structuralnot applicable
Branch plus rm -f / tee of a fixed heredoc; no memory, encoding, or format-string surface.
- domainreviewed
atomic_write evaluated and DEFERRED (see obligation_deferrals): the fingerprint stack is written by as_root tee in place, so an interrupted run can leave a torn /etc/pam.d/omarchy-lock-fingerprint; the same write-temp-rename gap is tracked on JW2J for the password stack. Tracked debt, not an accepted gap.
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-11
Else-branch matches: no enrolled fingerprint (or non-executable fprintd-list) removes /etc/pam.d/omarchy-lock-fingerprint; enrolled fingerprint installs/keeps it. fingerprint_pam_removed is the removal branch.
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.
1 obligation · 1 deferred
Browse the catalogueFilesystem writes that produce externally-visible state shall use the write-temp-rename pattern (or an equivalent atomic primitive); partial writes shall not be observable.
the fingerprint install branch writes /etc/pam.d/omarchy-lock-fingerprint via as_root tee in place; a torn write leaves a partial stack; same write-temp-rename gap as the password stack deferred on JW2J
- nominalrequireddeferredWitnessing deferred — accepted while the tracking known issue stays open.
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 fingerprint_not_enrolled the apply_lock shall always satisfy fingerprint_pam_removed
Witnesses· 2 scenarios total
- apply-lock-test.sh:1exercises 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| # | fingerprint_not_enrolled | fingerprint_pam_removed | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | fingerprint_not_enrolled | |
| 2 | T | F | F | fingerprint_not_enrolled | Exempted · defensive — the not-enrolled arm unconditionally removes the fingerprint PAM file; leaving it in place needs a broken build (reviewed: REVIEW-11) |
| 3 | T | T | T | fingerprint_pam_removed |
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 (1)
- omarchy-apply-lockbin/omarchy-apply-lock
Tests to re-run (1)
- apply-lock-test.shtest/shell.d/apply-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.