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.
An exact id match wins over every alias.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
An exact id match wins over every alias. App rows are never routable, so an installed app's keywords cannot shadow a menu route (htop ships Keywords=system).
when route_input & exact_id_match the menu_router shall eventually satisfy route_is_exact_id
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
MenuModel.js resolveRoute lines 177-191.
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 27, 2026, 21:25 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewedboundaryedge_casemalformed_input
Worst case: an installed app keyword shadows a menu route (htop ships Keywords=system), so typing a menu id launches an unrelated app instead - closed structurally by skipping kind==app in the alias scan so app aliases can never enter route resolution, while exact ids are checked first against the item map apps never join. boundary: the zero cases are pinned - empty input and the reserved words go/menu route to root before any lookup. edge_case: two menu items sharing one id resolve to whichever entry the merged item map holds (collision semantics owned by the merge sibling), duplicate aliases resolve by itemOrder position (deterministic but config-order dependent), and the id normalizer (lowercase, underscore-to-dash) means ids outside that folded space match only verbatim; unknown strings fall through as literal input by design so misspellings still attempt their id. 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.
- propertyrevieweddeterminismtotality
determinism: resolution walks itemOrder in order after the single exact-id map hit, so the same items and input always route identically. totality: every input string resolves to exactly one target - exact id, first matching alias, root for reserved words, or verbatim passthrough - with no input leaving the router undefined.
- structuralnot applicable
A lowercased string compare over a bounded alias list with the same normalization applied to both sides; no eval, regex over user input, or pointer work.
- domainnot applicable
Routing picks which user-owned action to run; no new authority is granted by the choice, and the traced resolver carries no network, crypto, or privilege surface.
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-58
Read resolveRoute. The exact-id check runs before the alias scan, so an exact id always wins; the alias loop skips kind==='app' entries outright, so an installed app's keywords can never shadow a menu route (the htop Keywords=system case in the description). route_input & exact_id_match models the first arm. Formula conforms to the code.
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.
The tests that discharge each obligation need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. 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 route_input & exact_id_match the menu_router shall eventually satisfy route_is_exact_id
Witnesses· 3 scenarios total
- menu-test.sh:1exercises 3 condition scenarios
MC/DC truth table· 4 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| # | exact_id_match | route_input | route_is_exact_id | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | T | F | T | exact_id_match | |
| 2 | T | F | F | T | route_input | |
| 3 | T | T | F | F | exact_id_match | Exempted · defensive — an exact id hit returns the input itself at the first check; routing it elsewhere needs that return removed (reviewed: REVIEW-M8) |
| 4 | T | T | T | T | route_is_exact_id |
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 (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
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.