Proof Portal
Omarchy
ProbeLabs74 findings · 94 requirementsA 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.
Before omarchy-apply-lock writes the PAM fingerprint stack, it shall install the fprintd resume hook (/usr/lib/systemd/system-sleep/fprintd-resume) and the fprintd stop-timeout drop-in, and reload systemd.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
Before omarchy-apply-lock writes the PAM fingerprint stack, it shall install the fprintd resume hook (/usr/lib/systemd/system-sleep/fprintd-resume) and the fprintd stop-timeout drop-in, and reload systemd. When either install fails, the helper shall stop before it writes the stack. When it removes the stack for an empty enrollment, it shall also remove the resume hook, and the drop-in when present.
when fingerprint_pam_installed the apply_lock shall always satisfy resume_recovery_installed
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Suspend can wedge the device claim of fprintd (libfprint/fprintd#173). Upstream #7158 restarts fprintd from a system-sleep hook after resume and caps its stop time with a drop-in. The helper installs both beside the PAM fingerprint stack. Setup and upgrades then cannot leave fingerprint authentication without its recovery. The empty-enrollment branch removes them again.
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
- Claude Code · AI agent
- Reviewed
- Oct 4, 2026, 19:06 UTC
History
- Created
- Oct 4, 2026, 19:00 UTC · Claude Code · AI agent
- Modified
- Oct 4, 2026, 19:16 UTC · Claude Code · AI agent
Hazard review
- scenarioreviewederror_handlingboundary
Worst case: fingerprint authentication is installed without the resume recovery, so the reader stays wedged after the first suspend and every fingerprint unlock fails. error_handling: install is run under set -e before the stack is written, so a missing hook or drop-in source stops the helper with no fingerprint stack (witnessed: "failed recovery installation cannot create fingerprint PAM", once per source). boundary: the removal branch removes the hook always and the drop-in only when present, reloading systemd only then, so a chroot install without systemd does not fail. input_domain not applicable: fixed source and destination paths. concurrency_scale not applicable: one helper run writes a fixed set of files. edge_case covered by the boundary rows.
- propertyreviewedidempotency
idempotency: install -D and systemctl daemon-reload give the same files when rerun.
- structuralnot applicable
install, rm and systemctl calls on fixed paths.
- domainreviewed
The hook runs as root from systemd-sleep on every resume and only enqueues a try-restart of fprintd.service; it reads no user input. The drop-in only sets TimeoutStopSec=3s. Both are installed root-owned with fixed modes (0755, 0644).
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.
- Claude Code · AI agentApprovedSpec conformanceOct 4, 2026 · 15 hours agoREVIEW-261004-YN8R
Read the install arm of the fingerprint step in bin/omarchy-apply-lock at upstream quattro 035ce29f. The helper runs under set -e. It installs the resume hook (0755) and the stop-timeout drop-in (0644) with install -D and runs systemctl daemon-reload before the tee that writes /etc/pam.d/omarchy-lock-fingerprint. A missing source makes install fail and stops the run before the tee. The removal arm removes the stack and the hook, and the drop-in only when present, reloading systemd only then. So a run that writes the stack has installed the recovery; the violation row needs the order reversed or set -e dropped and is dispositioned defensive. Witnesses in test/shell.d/apply-lock-test.sh: the hardened run installs the hook and the drop-in beside the stack; with either source missing the run fails and no stack exists. Requirement authored by agent:claude-code under the owner's delegation.
Cited code (5)
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 need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. 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 fingerprint_pam_installed the apply_lock shall always satisfy resume_recovery_installed
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_pam_installed | resume_recovery_installed | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | fingerprint_pam_installed | |
| 2 | T | F | F | fingerprint_pam_installed | Exempted · defensive — install of the resume hook and the drop-in and systemctl daemon-reload run under set -e before the tee that writes the stack, so a run that writes the stack installed both; a missing source stops the run first (witnessed below) (reviewed: REVIEW-261004-YN8R) |
| 3 | T | T | T | resume_recovery_installed |
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.