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.
The system shall report the compositor session-lock state as an exit code.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
The system shall report the compositor session-lock state as an exit code. Exit 0 means some monitor reports LOCK blocking it. Exit 1 means a monitor answered and none shows LOCK. Exit 2 means the probes cannot determine the state. When the shell detects a stranded lock left by a dead client and password PAM exists, the shell shall take the lock once. It shall record the recovery in the journal.
when lock_state_queried the lock_component shall always satisfy lock_state_reported & stranded_lock_recovered
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
ext-session-lock outlives its client. A restart leaves an orphan lock behind the Hyprland failsafe that nobody can unlock, so the shell must detect and reclaim it.
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:42 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 23, 2026, 17:16 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-19
Exit-code contract matches: 0 when any monitor is blocked by LOCK, 1 when a monitor answers and none shows LOCK, 2 when undetermined; the stranded-lock recovery (take once + journal) is wired through the shell service per the WJYM review.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
1 obligation · 1 discharged
Browse the catalogueEvidence tagged via <REQ> is witnessed by a requirement that satisfies this one — normal for stakeholder / aggregate requirements, which are proven through the requirements that refine them.
Behavior when operations fail or dependencies are unavailable.
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered by 1 test
Code signals
Static-analysis signals from external scanners that bear on this requirement's obligations — the source location, the obligation each touches, and its closure status.
- Coveredbuiltinstrict_mode_missingObligation: Error handling · Scenario
Behavior when operations fail or dependencies are unavailable.
script runs pipelines without `set -e`/`set -o pipefail`
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_state_queried the lock_component shall always satisfy lock_state_reported & stranded_lock_recovered
Witnesses· 3 scenarios total
- hyprland-session-locked-test.sh:1exercises 2 condition scenarios
- lock-stranded-recovery-test.sh:1exercises 1 condition scenario
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| # | lock_state_queried | lock_state_reported | stranded_lock_recovered | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | lock_state_queried | |
| 2 | T | F | F | F | lock_state_queried | Exempted · defensive — every query run exits through one of the three status returns; answering nothing needs a broken build (reviewed: REVIEW-19) |
| 3 | T | F | T | F | lock_state_reported | Exempted · defensive — the stranded-lock recovery flows through the probe's exit-0 report; recovering without a reported state is structurally absent (reviewed: REVIEW-19) |
| 4 | T | T | F | F | stranded_lock_recovered | |
| 5 | T | T | T | T | lock_state_reported |
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
Requirements (2)
Files to re-check (2)
- omarchy-hyprland-session-lockedbin/omarchy-hyprland-session-locked
- Service.qmlshell/plugins/lock/Service.qml
Tests to re-run (2)
- hyprland-session-locked-test.shtest/shell.d/hyprland-session-locked-test.sh
- lock-stranded-recovery-test.shtest/shell.d/lock-stranded-recovery-test.sh
What this rests on
Parent requirements (1)
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.