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 budget expires before the session reports secure, omarchy-system-sleep-lock shall print an unsecured-suspend diagnostic on stderr.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the budget expires before the session reports secure, omarchy-system-sleep-lock shall print an unsecured-suspend diagnostic on stderr. It shall then send a critical notification and exit 1. When the session reports secure within the budget, the script shall exit 0.
when budget_expired_without_secure the sleep_lock shall eventually satisfy unsecured_reported & exit_failure
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
logind suspends whether or not the wait succeeded. The notification on the unlock screen is the only way anyone finds out the session slept exposed.
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_handlingedge_case
Worst case: the machine suspends with the session exposed and nobody ever finds out, because the failure is silent. error_handling: budget expiry unconditionally prints the stderr diagnostic, sends the critical notification, and exits 1; that path is the requirement. edge_case: the notification service may be absent right after resume, so the send is declared best-effort while the stderr report and exit 1 still fire; a notification failure never downgrades the report to success. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, the outcome of one bounded wait inside one suspend; repeated suspends are stated on SYS-REQ-260912-HC86.
- propertynot applicable
Single-shot reporter; each expiry produces exactly one report and one exit, with no repeated-application or ordering surface.
- structuralnot applicable
printf uses a literal %s format with no user-controlled format string; no memory, pointer, or encoding surface.
- domainreviewederrors_propagated
The wait-loop failure is propagated as a typed outcome: nonzero exit plus stderr reason plus critical notification, never silently dropped. The absorbed notification failure is the declared best-effort policy the class names, with the stderr report as the authoritative channel.
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-8
Expiry path matches: when the budget expires before the session reports secure, the script prints the unsecured-suspend diagnostic on stderr, sends a critical notification, and exits 1; the secure path skips all three. Matches unsecured_reported & exit_failure.
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.
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 budget_expired_without_secure the sleep_lock shall eventually satisfy unsecured_reported & exit_failure
Witnesses· 2 scenarios total
- run_sleep_lockexercises 2 condition scenarios
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| # | budget_expired_without_secure | exit_failure | unsecured_reported | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | budget_expired_without_secure | |
| 2 | T | F | F | F | budget_expired_without_secure | — |
| 3 | T | F | T | F | exit_failure | — |
| 4 | T | T | F | F | unsecured_reported | — |
| 5 | T | T | T | T | exit_failure |
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)
- omarchy-system-sleep-lockbin/omarchy-system-sleep-lock
Tests to re-run (1)
- sleep-lock-test.shtest/shell.d/sleep-lock-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.