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.
A row matches only when every query term appears in its name text (label, leaf id, aliases) or as a whole word in its description.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
A row matches only when every query term appears in its name text (label, leaf id, aliases) or as a whole word in its description. Invisible and disabled rows never match.
when query_terms_given the menu_search shall eventually satisfy all_terms_matched & row_hidden_from_results
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
MenuModel.js matchesQuery lines 323-339; Menu.qml matchesQuery line 510-512 excludes disabled rows from search.
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
- scenarioreviewedmalformed_inputboundaryedge_case
Worst case: a search for a secret-flavored query surfaces rows the user cannot act on - invisible or disabled rows matching the terms and inviting selection of a gated action; the !visible early return is the trust partition and the null/root guards bound the entry shape. malformed_input: the query is free-typed text - normalization (lowercase, trim, whitespace split) absorbs odd casing and runs of spaces, and matching is literal indexOf, so regex metacharacters and punctuation are inert by construction, no interpretation to exploit. boundary: the all-terms AND semantics flip on a single missed term; empty terms from whitespace runs are skipped rather than failing every row; a one-character term is the narrowest legitimate match. edge_case: description matches are whole-word only (termInSearchWords) while name matches are substring - a term inside a description word does not match, and an empty description reduces the row to name text only; disabled-but-visible rows are excluded by the caller folding guard results into visible. Catalog 1.11.0 re-review: input_domain not applicable, the query is typed text matched as is; normalisation gaps are tracked as KI-MENU-SEARCH-TEXT-NORMALIZATION-MISSES. 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
The same query against the same model yields the same match set: normalization is a fixed transform, term order is preserved, and matching is stateless string search with no ranking randomness here (scoring is the SJ7P sibling) - a row cannot flicker in and of the result set across identical keystrokes.
- structuralnot applicable
toLowerCase and indexOf over config-sourced strings; no regex evaluation on user input (the only regex is the fixed whitespace splitter), so no backtracking surface, and no memory or encoding round-trip beyond case folding.
- domainnot applicable
In-process text matching over the loaded model; the query arrives through the menu's own text field and no file, IPC transport, network, crypto, or privilege surface participates.
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-47
Read matchesQuery. Every query term must appear in the name search text (label, leaf id, aliases) or as a whole word in the lowercased description, else the row is rejected; root, invisible, and disabled rows return false before any term check. The term loop maps to all_terms_matched and the early false returns map to row_hidden_from_results. 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 query_terms_given the menu_search shall eventually satisfy all_terms_matched & row_hidden_from_results
Witnesses· 4 scenarios total
- menu-test.sh:1exercises 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| # | all_terms_matched | query_terms_given | row_hidden_from_results | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | query_terms_given | |
| 2 | F | T | F | F | query_terms_given | — |
| 3 | F | T | T | F | all_terms_matched | |
| 4 | T | T | F | F | row_hidden_from_results | |
| 5 | T | T | T | T | all_terms_matched |
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.
2 open · 0 resolved
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.