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 suspend is imminent, the system shall request the session lock before it reconciles clamshell state.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When suspend is imminent, the system shall request the session lock before it reconciles clamshell state. The system shall bound the wait by a budget derived from the logind inhibitor window and capped at 12000 ms. The system shall report an unsecured suspend and fail when the budget expires before the session is secure.
when suspend_imminent the sleep_lock shall eventually satisfy lock_requested_first & (session_secure | unsecured_suspend_reported) & !(session_secure & unsecured_suspend_reported)
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
logind stops honouring the delay inhibitor after its window. A suspend that beats the lock leaves the session exposed, so the deadline must enforce itself.
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
Hazard review
- scenarioreviewedboundaryerror_handlingedge_caseconcurrency_scale
Parent-level partitions carried by satisfying children: boundary via FAWV (cap, reserve, validation thresholds), error_handling via H2YF (unsecured report and exit 1) and FAWV (busctl fallback), edge_case via FAWV (zero window, locale edge) and GGGS (lid-transition IPC stall). The suspend-mid-lock worst case is owned jointly: the budget bounds it and the report surfaces it. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale applied, suspends can follow each other quickly; each requests the lock within its own budget.
- propertynot applicable
Decomposition-level statement; totality of the bounded wait is recorded on child FAWV.
- structuralnot applicable
Decomposition-level statement; the locale-encoding surface is recorded on child FAWV where EPOCHREALTIME is parsed.
- domainnot applicable
Deadline declaration across the path is recorded on child FAWV (external_call_timeout_bounded); no additional domain class applies at this level.
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-17
Suspend path matches: the lock request precedes clamshell reconciliation, the wait budget derives from InhibitDelayMaxUSec with a one-fifth reserve (>=1000 ms, fallback 5000 ms) capped at 12000 ms, and budget expiry reports an unsecured suspend and exits 1.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
2 obligations
Browse the catalogueDischarging tests pending a synced audit.
Discharging tests pending a synced audit.
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 suspend_imminent the sleep_lock shall eventually satisfy lock_requested_first & (session_secure | unsecured_suspend_reported) & !(session_secure & unsecured_suspend_reported)
Witnesses· 3 scenarios total
- run_sleep_lockexercises 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| # | lock_requested_first | session_secure | suspend_imminent | unsecured_suspend_reported | Result | Proves | Covering test |
|---|---|---|---|---|---|---|---|
| 1 | F | F | F | F | T | suspend_imminent | |
| 2 | F | F | T | F | F | suspend_imminent | — |
| 3 | F | T | T | F | F | lock_requested_first | — |
| 4 | T | F | T | T | T | session_secure | |
| 5 | T | T | T | F | T | lock_requested_first | |
| 6 | T | T | T | T | F | session_secure | — |
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
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.