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 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
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-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)
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 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 | — |
| 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.
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
Nothing downstream depends on this yet
No downstream impact — "When the lock IPC handler receives a lock request and…" has no downstream edges.
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.