Proof Portal
Omarchy
ProbeLabs73 findings · 87 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.
When the lock IPC handler receives a lock request and /etc/pam.d/omarchy-lock-password is missing, the lock service shall answer missing-pam.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the lock IPC handler receives a lock request and /etc/pam.d/omarchy-lock-password is missing, the lock service shall answer missing-pam. It shall not engage the session lock.
when lock_requested & !password_pam_configured the lock_service shall always satisfy lock_denied_missing_pam
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
A lock engaged without a password PAM stack can never authenticate. Refusing the lock is the only outcome that cannot strand the user.
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
- scenarioreviewedaccess_deniederror_handlingboundaryconcurrency_scale
Worst case: the lock engages without the password PAM stack, producing a session that can never authenticate and stranding the user at the lock screen. access_denied: the requirement is the denial itself, beginLock and the lock IPC verb both refuse to engage when the PAM config is absent. error_handling: a FileView load failure drives passwordPamConfigured false and into the refusal path. boundary: the present/absent threshold of /etc/pam.d/omarchy-lock-password is the trigger edge, re-evaluated live by watchChanges so a mid-session config removal flips the answer. Catalog 1.11.0 re-review: input_domain not applicable, it checks the presence of a PAM file and parses nothing. concurrency_scale applied, the lock IPC handler serves lock requests that can arrive back to back; each request while PAM is missing answers missing-pam and engages nothing.
- propertynot applicable
A refusal gate over one predicate; no algebraic, ordering, or repeated-application surface, and the once-only aspects of locking belong to WJYM.
- structuralnot applicable
QML boolean guard over a FileView state; no memory, encoding, or numeric surface.
- domainreviewedcontrol_not_silently_disabled
The lock control fails closed on its unmet precondition: a missing PAM stack is a reject path with a distinct missing-pam answer and a lock-denied journal event, never a skip path, and no alternate admission bypasses the check. lock-missing-pam-test.sh witnesses the denial.
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-5VB9
Re-recorded after the MC/DC annotation campaign shifted lines (beginLock 164->168, lockIpc lock 712->725; mcdc:ignore inserts above). Read beginLock() and the lockIpc lock() verb: beginLock refuses when passwordPamConfigured is false - it logs lock-denied: missing-pam and returns false without engaging the session lock; the IPC verb answers missing-pam on the same config check before beginLock can run, so with PAM configured the denial arm is not taken and the failed arm is structurally dead (mcdc:ignore:defensive). Matches lock_denied_missing_pam under lock_requested & !password_pam_configured.
Cited code (2) - Kimi Dogfood · AI agentApprovedSpec conformanceSep 12, 2026 · 3 weeks agoREVIEW-2
Lock IPC handler checks /etc/pam.d/omarchy-lock-password before engaging; on missing PAM it answers missing-pam and does not lock, matching lock_denied_missing_pam. When PAM is configured the denial branch is not taken — the antecedent !password_pam_configured gates exactly the code's config check.
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 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 lock_requested & !password_pam_configured the lock_service shall always satisfy lock_denied_missing_pam
Witnesses· 3 scenarios total
- lock-missing-pam-test.sh:1exercises 3 condition scenarios
MC/DC truth table· 4 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| # | lock_denied_missing_pam | lock_requested | password_pam_configured | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | lock_requested | |
| 2 | F | T | F | F | lock_denied_missing_pam | Exempted · defensive — the denial is the first statement of beginLock and returns before any engagement; a missing-PAM request that still locks needs a broken build (reviewed: REVIEW-2) |
| 3 | F | T | T | T | password_pam_configured | |
| 4 | T | T | F | T | lock_denied_missing_pam |
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)
- Service.qmlshell/plugins/lock/Service.qml
Tests to re-run (1)
- lock-missing-pam-test.shtest/shell.d/lock-missing-pam-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.