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.
Cursor movement lands on the next selectable row in the direction of travel, wrapping at the list ends.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
Cursor movement lands on the next selectable row in the direction of travel, wrapping at the list ends. Movement steps over disabled rows.
when cursor_moves the menu_navigation shall eventually satisfy disabled_rows_skipped
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Menu.qml nextSelectable lines 530-542 and select lines 706-717.
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: the cursor parks on a disabled row where Enter silently does nothing - a cursor trap that reads as a dead menu. Closed on both input paths: movement scans rowSelectable and Enter and pointer activation gate on it too, so a skipped row cannot be fired from any direction, and the all-disabled menu ends at -1 with the cursor hidden rather than parked (settleCursor keeps the index defined but cursorActive false). boundary: the declared class covers the exact edges the scan exists for - count 0 and 1, from below zero or past the end normalized by double modulo, and the wrap scan bounded at count iterations. edge_case: a non-unit direction normalizes to a ±1 step, and a menu that grows a selectable row immediately grows a cursor on the next settle.
- propertyreviewedtotalitydeterminism
totality: every (from, direction, disabled-set) combination returns a defined index or -1, with the all-disabled -1 as the named third outcome. determinism: the scan walks one fixed step from a normalized start, so the same rows and cursor state always land on the same target.
- structuralnot applicable
The bounded for-loop is itself the termination argument (at most count iterations, no while-true wrap), double-modulo normalizes any integer from, and no arithmetic beyond index stepping exists in the slice.
- domainnot applicable
Cursor placement is display state inside one shell window; no trust boundary, network, crypto, or privilege surface, and no cross-process wait exists in the traced functions.
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-70
Read rowSelectable/nextSelectable. Movement scans in the direction of travel, wrapping at list ends, and steps over rows whose disabled flag rowSelectable reports; -1 (all disabled) is 3JG5's condition. cursor_moves models the movement entry; disabled_rows_skipped is the scan-skips-disabled construction. 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.
1 obligation
Browse the catalogueDischarging tests pending a synced audit.
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 cursor_moves the menu_navigation shall eventually satisfy disabled_rows_skipped
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| # | cursor_moves | disabled_rows_skipped | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | cursor_moves | |
| 2 | T | F | F | cursor_moves | — |
| 3 | T | T | T | disabled_rows_skipped |
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 — "Cursor movement lands on the next selectable row in the…" 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.