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 filter query narrows to visible, selectable rows whose name or description matches every term, ranked by match quality.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
A filter query narrows to visible, selectable rows whose name or description matches every term, ranked by match quality.
when search_entered the menu_search shall eventually satisfy matching_rows_ranked
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Search is the power-user path; ranking decides which row Enter activates.
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
boundary: the empty/whitespace query degenerates to all visible rows (no term to AND), and a query of only non-matching terms yields zero rows - both partition edges are contract, not accident. edge_case: multi-term AND semantics (every term must hit name or description) with rank tiers (prefix beats substring beats field position), so a term matching only description still ranks below a name hit; visible-only and selectable-only filters run before matching, so hidden/disabled rows can never be searched into view. malformed_input: the query is never compiled to a RegExp - matching is indexOf over lowercased text, so metacharacters are inert data. 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
determinism: rank is a pure function of the row labels and the query - the same query over the same tree orders identically; ties keep tree order. totality: every row is classified (match/no-match) by the same predicate, so the partition is total. monotonicity is deliberately not carried: adding a term can only narrow (AND semantics), which is the contract.
- structuralnot applicable
indexOf/lowercase comparisons over config-authored labels: no regex engine, no encoding transform beyond locale-stable toLowerCase on the same host, no memory/pointer surface.
- domainreviewed
redos_resistant evaluated and suppressed with rationale: the matcher constructs no RegExp from the query and uses linear-time indexOf scans, so catastrophic backtracking is structurally impossible on this surface - the class precondition (regex evaluation on the input path) does not fire, which is stronger than tuning a bounded pattern set. No external call, IPC, or trust boundary: search narrows an in-memory tree built from the user own config and same-machine providers.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
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 search_entered the menu_search shall eventually satisfy matching_rows_ranked
Witnesses· 2 scenarios total
- countexercises 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| # | matching_rows_ranked | search_entered | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | search_entered | |
| 2 | F | T | F | matching_rows_ranked | — |
| 3 | T | T | T | matching_rows_ranked |
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.
No findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
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
Requirements (3)
Files to re-check (2)
- Menu.qmlshell/plugins/menu/Menu.qml
- MenuModel.jsshell/plugins/menu/MenuModel.js
Tests to re-run (3)
- menumodel-replay.test.mjstest/node/menumodel-replay.test.mjs
- report-reproducers.test.mjstest/node/report-reproducers.test.mjs
- menu-test.shtest/shell.d/menu-test.sh
What this rests on
Parent requirements (1)
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.