Proof Portal
Omarchy
ProbeLabs73 findings · 87 requirementsA 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.
A route string (exact id, declared alias, or normalized spelling) opens the item it denotes; unknown strings fall through as literal ids.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
A route string (exact id, declared alias, or normalized spelling) opens the item it denotes; unknown strings fall through as literal ids.
when route_given the menu_router shall eventually satisfy routed_to_intended_item
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Routes are user-facing (omarchy menu summon power); mis-resolution opens the wrong submenu or shadows menu items behind installed apps.
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:08 UTC · Leonid Bugaev
Hazard review
- scenarioreviewedboundaryedge_case
Worst case graded on the boundary obligation above (alias/exact-id shadowing across merged sources - low). boundary: the resolution partition is exact id first, then declared alias (lowercased, underscore-normalized), then normalized-spelling fallthrough, then the unknown string opened as a literal id - each arm is a child contract (exact/alias/normalized/literal), so the parent partition is covered arm by arm. edge_case: the unknown-string-as-literal-id fallthrough means a typo route opens a menu row named by the typo text instead of erroring - documented behavior, loud by row presence, and the fallback-to-root guarantee lives in the lookup child (B8N9 family). Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, a pure function of its arguments, recomputed on each load or keystroke: no state across calls, no process, timer or lock.
- propertyrevieweddeterminism
determinism: the same route string answers the same item on every resolution - the precedence order is fixed by itemOrder and alias matching is a pure string comparison; no algebraic/ordering surface on a route lookup. idempotency: resolving twice cannot change the tree.
- structuralnot applicable
string comparisons over config-authored ids: normalization is toLowerCase + underscore-to-dash, applied uniformly before comparison (so case/separator drift is closed by construction); no memory, pointer, or encoding surface. Depth-guarded walks (32 cap) protect the tree traversal behind routing.
- domainnot applicable
routing is in-process string resolution: no external call, no timeout surface, no IPC, no trust boundary (routes come from the user own keybinds/scripts on their own machine). Identity classes are met by construction: route keys, item ids, and alias tokens flow through one normalization before every comparison.
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 · 1 discharged
Browse the catalogueEvidence tagged via <REQ> is witnessed by a requirement that satisfies this one — normal for stakeholder / aggregate requirements, which are proven through the requirements that refine them.
Behavior at limits, thresholds, and edge-of-range values.
route precedence ambiguity: a user-declared alias that equals another item exact id (alias power on the item whose id is also power, or a slugified app claiming a menu id) flips which entry an alias route opens - resolution iterates itemOrder, so merged order (default-then-user, provider swaps) decides the winner; the exact-id-first partition and single-claim merge keep the wrong-target window at config-authoring time, graded low
- 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 route_given the menu_router shall eventually satisfy routed_to_intended_item
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| # | route_given | routed_to_intended_item | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | route_given | |
| 2 | T | F | F | route_given | Exempted · defensive — resolveRoute always returns the exact id, the alias target, or the literal input; an unintended destination needs all three returns broken (reviewed: REVIEW-M8) |
| 3 | T | T | T | routed_to_intended_item |
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 implementation linked
No source files are traced to this requirement yet.
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
Requirements (6)
- A route matching no id and no alias resolves to the literal…menu · SW
- Absent an exact id, a route equal to a declared alias…menu · SW
- When a route resolves to an action item with a non-empty…menu · SW
- An exact id match wins over every aliasmenu · SW
- When a route resolves to a link item, the menu opens at the…menu · SW
- A menu action may exactly match the bare-summon grammarmenu · SW
Files to re-check (2)
- Menu.qmlshell/plugins/menu/Menu.qml
- MenuModel.jsshell/plugins/menu/MenuModel.js
Tests to re-run (2)
- menumodel-replay.test.mjstest/node/menumodel-replay.test.mjs
- menu-test.shtest/shell.d/menu-test.sh
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.