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 menu Lock row invokes the lock component's CLI entry point omarchy-system-lock with no arguments.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
The menu Lock row invokes the lock component's CLI entry point omarchy-system-lock with no arguments. The callee engages the session lock and exits 0. This is the only menu-to-lock interaction; lock never calls menu.
when lock_row_activated the menu shall eventually satisfy system_lock_invoked
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
The default menu config carries a Lock row whose action is omarchy-system-lock (default/omarchy/omarchy-menu.jsonc:38). This row is the single menu-to-lock call path; the lock component never invokes menu.
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 Zero Warnings · AI agent
- Reviewed
- Sep 27, 2026, 21:05 UTC
History
- Created
- Sep 27, 2026, 20:58 UTC · Kimi Zero Warnings · AI agent
- Modified
- Sep 30, 2026, 21:16 UTC · Opencode Quattro · AI agent
Hazard review
- scenarioreviewednominalerror_handling
Worst case graded on the error_handling obligation above (silent lock failure behind an already-closed menu - medium). nominal: the row is a fixed zero-argument invocation, the callee engages the lock and exits 0, and the row is the single menu-to-lock path (lock never calls menu), so no recursion or re-entry loop can exist. error_handling: a callee refusal exits coded and the menu-side runner prints non-zero exits to its stderr - but the menu has already dismissed, which is exactly the visibility gap graded above; the contract deliberately scopes this req to the invocation wiring and leaves engagement/failure surfacing to the lock component. malformed_input does not fire: no user-shaped input reaches the row (action string is repo-shipped). Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, one exec per Lock row activation; overlapping lock requests are stated on SYS-REQ-260912-T0XP.
- propertyrevieweddeterminism
determinism: the wiring is static - one row, one fixed action string, zero arguments, so every activation dispatches identically; nothing about the invocation depends on state or ordering. Atomicity/idempotency are owned by the lock component (re-entrant lock requests are its contract, batch A review), not by the row wiring.
- structuralnot applicable
a JSONC action string referencing a fixed binary name: no memory, pointer, or encoding surface; the argument list is empty by contract, so no quoting or injection surface exists.
- domainreviewed
cross_structure_key_identity evaluated and suppressed with rationale: the action string omarchy-system-lock and the invoked binary name live in one repo-shipped artifact pair (default/omarchy/omarchy-menu.jsonc:38 plus bin/), line-cited in REVIEW-28 and pinned by the menu tests - there are no two independently-maintained structures to drift. external_call_timeout_bounded evaluated and suppressed with rationale: the row handoff is fire-and-forget by design (menu dismisses, lock engages asynchronously), the menu side performs no wait, and the lock component engagement deadlines are owned by the lock requirements (SYS-REQ-260912-T0XP family, batch A) - deferring here would duplicate debt one level above its owner. control-not-silently-disabled is met at this boundary by the same ownership split: the wiring cannot disable the control, and the callees fail-visible contract is theirs. tampering/replay classes do not fire: the call is an in-session fork, not a message.
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 Zero Warnings · AI agentApprovedSpec conformanceSep 27, 2026 · 5 days agoREVIEW-28
Read the full call path. default/omarchy/omarchy-menu.jsonc:38 binds the Lock row action to omarchy-system-lock verbatim. openRoute (Menu.qml:954) resolves the row, sees kind=action, and runs entry.action via runAction -> Util.execDetached (subprocess, no args). bin/omarchy-system-lock takes no arguments, invokes omarchy-shell lock lock, and exits 0 by construction. Formula lock_row_activated -> system_lock_invoked matches: activation of the Lock row is the only trigger and the subprocess exec is the only invocation channel.
Cited code (3)
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 delegated
Browse the cataloguethe Lock row activation closes the menu and forks omarchy-system-lock, which then fails silently (binary absent after a partial sync, or the lock component refuses without a notification surface): the menu is already dismissed so no error reaches the user, and the user walks away from a session they believe locked - impact high, likelihood near zero (the lock binary is a default-set runtime invariant), graded medium on impact times the one-way visibility loss; the callees own lock engagement and its failure surfacing (SYS-REQ-260912-T0XP family, reviewed in batch A)
The graded worst case in the hazard_review above is a real, reproduced failure mode: bin/omarchy-system-lock line 10 swallows a refused or absent lock engagement and exits 0 behind the already-dismissed Lock row, so the user believes the session locked; failure surfacing is owned by the lock component (SYS-REQ-260912-T0XP family, per the delegation above), and until that lands the debt is tracked on KI-260930-2FBE with a green tripwire.
Failure surfacing for the lock call is owned by the callee per the WC89 hazard review: the contract deliberately scopes this interface req to invocation wiring and leaves engagement/failure surfacing to the lock component (SYS-REQ-260912-T0XP family), which carries error_handling on its checklist; the menu-side runner only forwards the callee exit to stderr and the menu is already dismissed at that point
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 lock_row_activated the menu shall eventually satisfy system_lock_invoked
Witnesses· 2 scenarios total
- menu-test.sh:1exercises 2 condition scenarios
MC/DC truth table· 3 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_row_activated | system_lock_invoked | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | lock_row_activated | |
| 2 | T | F | F | lock_row_activated | — |
| 3 | T | T | T | system_lock_invoked |
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
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.