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 select payload carries mode=select, prompt, options, selectionFile, and doneFile, plus integer width/maxHeight only when given; options come from arguments or, with none and non-terminal stdin, from stdin lines.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
The select payload carries mode=select, prompt, options, selectionFile, and doneFile, plus integer width/maxHeight only when given; options come from arguments or, with none and non-terminal stdin, from stdin lines.
when select_invoked the dmenu_protocol shall eventually satisfy payload_shape_correct
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
bin/omarchy-menu-select lines 29-87.
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
- pending
History
- Created
- Sep 22, 2026, 13:34 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 22, 2026, 13:34 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedconcurrent
KI-MENU-SELECT-POLL-DEADLOCK reviewed on audit/pr-9056-refresh: abandoned-request trigger (second summon strands first caller) is mitigated by SW-REQ-260925-XTGG (Menu.qml:32 finishRequest(null) before new open). Residual hazard UNCHANGED: peer death with no subsequent summon still leaves the done_file poll unbounded; reproducer re-run 2026-09-25 still reproduces (evidence refreshed, known_issue_reproduced). Bounded-wait spec gap remains open and KI stays active.
- domainnot applicable
Domain classes fire only on matching workload tags (HTTP/crypto/IPC frameworks); these menu dmenu-protocol requirements carry no domain tags and the component is a local QML plugin + bash scripts with no network/crypto surface.
- structuralnot applicable
Structural classes target C-family memory/format-string hazards (pointer arithmetic, manual ownership, sanitizer evidence). Implementation is QML/JS (GC'd) plus bash invoking printf with constant format strings; no manual memory or binary framing exists in this component.
- propertyreviewed
Reviewed: no property-catalog class binds beyond the scenario coverage. The select/dispatch protocol is single-shot per request (no idempotency/monotonicity dimension); answer atomicity is owned by the finishRequest reqs (C8HX/FGZQ); the residual unbounded-wait hazard is tracked by KI-MENU-SELECT-POLL-DEADLOCK, not a property class.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
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.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
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 select_invoked the dmenu_protocol shall eventually satisfy payload_shape_correct
Witnesses· 2 scenarios total
- menu-dmenu-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| # | payload_shape_correct | select_invoked | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | select_invoked | |
| 2 | F | T | F | payload_shape_correct | — |
| 3 | T | T | T | payload_shape_correct |
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
Nothing downstream depends on this yet
No downstream impact — "The select payload carries mode=select, prompt, options,…" has no downstream edges.
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.