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 stranded-lock probe exits 0, the service holds no lock, and password PAM exists, the lock service shall take the session lock once.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the stranded-lock probe exits 0, the service holds no lock, and password PAM exists, the lock service shall take the session lock once. It shall log a lock-stranded recovery event.
when stranded_lock_detected & password_pam_configured the lock_service shall eventually satisfy stranded_lock_recovered_once & recovery_logged
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. Without recovery, a shell restart leaves an orphan lock that only the Hyprland failsafe covers and nobody can unlock.
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 23, 2026, 17:20 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewederror_handlingconcurrentboundary
Worst case: a shell restart leaves an orphan ext-session-lock nobody can unlock, or the recovery itself flaps, taking the lock repeatedly. error_handling: an undetermined probe answer (exit 2) leaves the strand unresolved instead of acting, and recovery refuses without passwordPamConfigured, deferring to the J8SX fail-closed denial. concurrent: checkStrandedLock refuses to probe while locked or lockRequested, and the probe onExited verdict re-checks the same flags, closing the probe-in-flight versus lock-taken race. boundary: recovered-once is the strandedLock plus strandedLockResolved latch.
- propertyreviewedidempotency
recoverStrandedLock is idempotent per strand: the flag pair plus the probe running guard make every repeated trigger, whether the screens-changed re-arm, the retry timer, or the PAM reload, converge on at most one beginLock and one journal line.
- structuralnot applicable
QML flags plus one guarded beginLock call; no memory, encoding, or numeric surface.
- domainnot applicable
In-process recovery plus a local probe process; no external call, transport, or trust boundary.
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-1T34
Re-recorded after the MC/DC annotation campaign shifted lines (checkStrandedLock 101->105, recoverStrandedLock 114->118). checkStrandedLock runs the probe once until resolved and short-circuits when the shell holds or requested a lock; recoverStrandedLock takes the session lock exactly once - the strandedLock=false reset guards re-entry - and only when the probe found no own lock and password PAM is configured, logging lock-stranded: recovering via logEvent before beginLock. Matches stranded_lock_recovered_once & recovery_logged.
Cited code (2) - Kimi Dogfood · AI agentApprovedSpec conformanceSep 12, 2026 · 3 weeks agoREVIEW-13
Stranded-lock path matches: probe exit 0 + no own lock + password PAM configured takes the session lock exactly once and writes the lock-stranded recovery journal entry; the once-only guard prevents re-entry, matching stranded_lock_recovered_once & recovery_logged.
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 catalogueBehavior when operations fail or dependencies are unavailable.
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered by 1 test
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 stranded_lock_detected & password_pam_configured the lock_service shall eventually satisfy stranded_lock_recovered_once & recovery_logged
Witnesses· 3 scenarios total
- lock-stranded-recovery-test.sh:1exercises 3 condition scenarios
MC/DC truth table· 6 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| # | password_pam_configured | recovery_logged | stranded_lock_detected | stranded_lock_recovered_once | Result | Proves | Covering test |
|---|---|---|---|---|---|---|---|
| 1 | F | F | T | F | T | password_pam_configured | |
| 2 | T | F | F | F | T | stranded_lock_detected | |
| 3 | T | F | T | F | F | password_pam_configured | — |
| 4 | T | F | T | T | F | recovery_logged | — |
| 5 | T | T | T | F | F | stranded_lock_recovered_once | — |
| 6 | T | T | T | T | T | recovery_logged |
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
Files to re-check (1)
- Service.qmlshell/plugins/lock/Service.qml
Tests to re-run (1)
- lock-stranded-recovery-test.shtest/shell.d/lock-stranded-recovery-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.