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.
Drilling in pushes the previous menu on the navigation stack.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
Drilling in pushes the previous menu on the navigation stack. Backspace/Left pops it, or falls back to the parent menu when the stack is empty. Entering a menu clears the filter.
when submenu_entered the menu_navigation shall eventually satisfy back_retraces_path
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Menu.qml setActiveMenu lines 729-742 and goBack lines 744-757.
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: back navigation strands the user or lands somewhere wrong - a stack id or parent id whose menu vanished under a live config reload resolves through the unknown-id guard to root rather than an empty menu, and an empty-parent item falls to root explicitly. boundary: root as the terminal back target (goBack returns false without state change) and the empty-stack arm switching to parent fallback are the two partition edges of back behavior. edge_case: re-entering the current menu pushes nothing (id !== activeMenu gate) so Back cannot bounce in place, entering a menu clears the filter per the subject so a search-narrowed view cannot leak into a submenu, and repeated A-to-B-to-A drilling grows the stack one small string per level - bounded by user interaction and reset on every menu open (navStack cleared in openExistingMenu), graded low. All consequences are display-state only. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, view state recomputed from the current rows on each UI event: no process, timer or lock, and events are handled one at a time.
- propertyreviewedtotality
Every navigation state (any active menu, any stack depth, any parent chain, any config generation) yields a defined back destination - popped stack entry, declared parent, or root - and every drill-in yields a defined push-and-clear; no state leaves goBack without an answer or the filter uncleared.
- structuralnot applicable
Array concat/slice on a stack of id strings plus boolean flags; no memory, pointer, encoding, or numeric surface.
- domainnot applicable
Pure in-shell navigation state; no IPC, file, network, crypto, or privilege surface - the key events arrive through the menu's own focus handler and the config reload interplay is resolved by the unknown-id fallback recorded under scenario.
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-46
Read setActiveMenu and the navigation code around it. Drilling in pushes the previous menu onto navStack (pushHistory && id changed), Backspace/Left pops it with a fallback to the parent menu when the stack empties, and entering a menu clears the filter. The submenu_entered condition models the push branch; the pop/retrace path is the same stack. Formula conforms to the code.
Cited code (1)
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 submenu_entered the menu_navigation shall eventually satisfy back_retraces_path
Witnesses· 2 scenarios total
- pokeGuardsexercises 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| # | back_retraces_path | submenu_entered | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | submenu_entered | |
| 2 | F | T | F | back_retraces_path | Exempted · defensive — setActiveMenu pushes the previous menu on navStack on every drill-in and goBack pops it; a back that loses the path needs the push removed (reviewed: REVIEW-MC1) |
| 3 | T | T | T | back_retraces_path |
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 (1)
- menu-compositor-test.shtest/shell.d/menu-compositor-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.