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.
Absent an exact id, a route equal to a declared alias resolves to the id of the item declaring the alias.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
Absent an exact id, a route equal to a declared alias resolves to the id of the item declaring the alias. Alias comparison lowercases and maps underscores to dashes.
when route_input & !exact_id_match & alias_match the menu_router shall eventually satisfy route_is_alias_target
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 181-189; normalization at line 178 and 186.
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_case
Worst case: two menu items declare the same alias and the route silently opens whichever comes first in itemOrder - a user summoning power lands on an unrelated item; the scan is order-driven and first-match-wins, which makes the outcome deterministic but the conflict itself is config-author error with a low cosmetic blast radius (a wrong menu opens, nothing executes). boundary: the exact-id beat over any alias is the precedence boundary shared with 74BZ, and excluding app rows from the alias scan is the deliberate trust boundary that keeps .desktop Keywords from shadowing real routes (htop ships Keywords=system). edge_case: underscore-to-dash normalization makes power_menu and power-menu one alias (collision collapses harmlessly), aliases on action and link kinds route through openRoute's kind handling, and an empty alias string can never match because raw is rooted before the scan. 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
Alias resolution is a pure function of the loaded model: normalization is a fixed string transform and the scan walks itemOrder in a fixed sequence returning the first declared match, so the same config always maps a route to the same target - including its first-match-wins arbitration of duplicate aliases.
- structuralnot applicable
toLowerCase/replace over declared alias strings compared for equality; no memory, pointer, numeric, or encoding round-trip surface - the normalization vocabulary is ASCII route names.
- domainnot applicable
In-process lookup over already-normalized config data; the IPC receipt of the route string lives with the lifecycle requirement (50RE) and nothing here touches files, network, crypto, or privilege.
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-45
Read resolveRoute. With no exact id hit, the alias scan compares the normalized input (lowercased, underscores mapped to dashes) against each non-app entry's normalized aliases and returns the declaring item's id on a hit. The condition route_input & !exact_id_match & alias_match models exactly this middle arm; app entries are deliberately skipped, matching the description's scope. 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 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 route_input & !exact_id_match & alias_match the menu_router shall eventually satisfy route_is_alias_target
Witnesses· 4 scenarios total
- countexercises 4 condition scenarios
MC/DC truth table· 5 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| # | alias_match | exact_id_match | route_input | route_is_alias_target | Result | Proves | Covering test |
|---|---|---|---|---|---|---|---|
| 1 | F | F | T | F | T | alias_match | |
| 2 | T | F | F | F | T | route_input | |
| 3 | T | F | T | F | F | alias_match | — |
| 4 | T | F | T | T | T | route_is_alias_target | |
| 5 | T | T | T | F | T | exact_id_match |
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 — "Absent an exact id, a route equal to a declared alias…" 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.