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.
omarchy-menu routes each verb (toggle/summon/close/refresh/ping) to the matching omarchy-shell IPC call so the menu opens, closes, refreshes, or answers ping.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
omarchy-menu routes each verb (toggle/summon/close/refresh/ping) to the matching omarchy-shell IPC call so the menu opens, closes, refreshes, or answers ping.
when menu_invoked the menu_dispatcher shall eventually satisfy menu_presented
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
The dispatcher is the single entry point; every keybind and script reaches the menu through it.
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:25 UTC
History
- Created
- Sep 22, 2026, 13:33 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 30, 2026, 08:07 UTC · Leonid Bugaev
Hazard review
- scenarioreviewedmalformed_inputerror_handlingconcurrency_scale
Worst case graded on the existing error_handling obligation above (exec refusal surfaces as terminal error text, no menu - low). malformed_input: an unknown verb exits 2 with usage text, an unknown route degrades to the documented root default, and payloads are built with jq -nc --arg so shell metacharacters in a route cannot break the JSON envelope or the IPC call. error_handling: each verb is a single exec, so the IPC result code IS the dispatcher result - no swallow point exists between the verb case and the process exit; refresh/ping answers are passed through unmodified. Catalog 1.11.0 re-review: input_domain not applicable, routes travel as JSON built by a JSON encoder. concurrency_scale applied, verbs arrive as independent IPC calls that can follow each other quickly (SW-REQ-260922-50RE).
- propertyrevieweddeterminism
determinism: the verb-to-IPC-call mapping is a fixed table (one case arm per verb, one payload shape per call) - same verb and route always dispatch the same call; no ordering, algebraic, or repeated-application surface exists on a fork-exec one-shot. idempotency belongs to the verbs themselves (toggle is deliberately not idempotent; summon/close/refresh are), which is the documented semantic, not a hazard.
- structuralnot applicable
a bash case table around jq and exec: no memory, pointer, or format-string surface; the only encoding step (jq --arg) is the structurally safe construction named above.
- domainreviewed
external_call_timeout_bounded evaluated and suppressed with rationale: every verb is exec dispatch onto the local omarchy-shell socket - a dead or wedged shell answers connect-refusal immediately (fast-fail loud, the low-graded worst case above), the dispatcher itself has no wait loop, and any bounded-wait debt inside the summoned surfaces is owned by their own requirements (done_file poll deferred under KI-MENU-SELECT-POLL-DEADLOCK). No auth surface (single-user local IPC), no cross-identity key movement between the verb table and the IPC call names - the strings are one repo artifact.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
1 obligation
Browse the cataloguethe dispatcher exec fails (omarchy-shell not running, socket refusal): the keybind or script caller sees a one-line error on the invoking terminal and no menu - recoverable and loud, graded low because refusal is immediate rather than hung, and the verb surface is fixed (toggle/summon/close/refresh/ping) with jq --arg payload construction making payload injection structurally impossible
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 menu_invoked the menu_dispatcher shall eventually satisfy menu_presented
Witnesses· 3 scenarios total
- menu-dispatcher-test.sh:1exercises 3 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| # | menu_invoked | menu_presented | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | menu_invoked | |
| 2 | T | F | F | menu_invoked | |
| 3 | T | T | T | menu_presented |
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.