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.
When a route resolves to a link item, the menu opens at the link's target.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When a route resolves to a link item, the menu opens at the link's target.
when resolved_kind_link the menu_router shall eventually satisfy link_target_followed
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Menu.qml openRoute lines 906-908.
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:34 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 27, 2026, 21:25 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewedboundaryedge_case
Worst case: a link silently lands somewhere other than its target - the misdirect cost is one wrong panel the user navigates away from, since routing grants no authority. boundary: the zero case is the targetless link - a link entry with an empty target skips the follow branch and opens at the link itself rather than dereferencing undefined. edge_case: the follow is single-hop by construction (id = entry.target, then open) so a chain a->b->c lands on the b row and needs a second follow, and a link whose target is an action bypasses the direct-run branch (that check ran on the original resolved entry) and opens a childless panel - both config-authored cosmetic edges, no hang and no route loop (one dereference, no iteration). 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: two map lookups (resolved entry, target field) with no iteration, so the same items and input always land on the same panel. totality: every resolved link ends defined - followed for a non-empty target, self-landing otherwise - and every other kind takes its own branch, with no input leaving openRoute without a landing id and an ok return.
- structuralnot applicable
Two property reads and an assignment; the target id is never evaluated, interpolated, or parsed - it only selects an existing map key downstream.
- domainnot applicable
Choosing which menu panel to render moves no authority; the traced slice has no network, crypto, privilege, or cross-process 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-68
Read openRoute. After resolveRoute, a resolved link entry makes the menu open at the link's target (an action leaf runs directly instead). resolved_kind_link models the kind==='link' arm; link_target_followed is the open-at-target behavior. 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 resolved_kind_link the menu_router shall eventually satisfy link_target_followed
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| # | link_target_followed | resolved_kind_link | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | resolved_kind_link | |
| 2 | F | T | F | link_target_followed | — |
| 3 | T | T | T | link_target_followed |
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 (1)
- Menu.qmlshell/plugins/menu/Menu.qml
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.