Proof Portal
Omarchy
ProbeLabs74 findings · 88 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.
The app library lists an installed app exactly when the app is displayable and every query term matches it.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
The app library lists an installed app exactly when the app is displayable and every query term matches it. An app is displayable when it has a name or an id, is not marked NoDisplay, and the library does not hide it. A term matches the name, id, generic name, comment or keywords, or its acronym when the term has five characters or fewer. An empty query matches every app. The Apps menu asks with an empty query.
the app_library shall always satisfy (app_listed <=> (app_displayable & query_terms_matched))
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
shell/services/AppSearch.js builds the list that AppLibrary.sortedEntries returns to the Apps menu and the launcher. This requirement states which apps the list holds, as the upstream code behaves. It does not state the order. The code ranks rows by fuzzyScore when there is a query, then by the lowercased name in code-unit order. KI-MENU-APPS-SORT-LOCALE records that this order puts accented names after z.
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
- Claude Quattro Proof · AI agent
- Reviewed
- Oct 3, 2026, 12:20 UTC
History
- Created
- Oct 3, 2026, 12:33 UTC · Claude Quattro Proof · AI agent
- Modified
- Oct 3, 2026, 12:37 UTC · Claude Quattro Proof · AI agent
Hazard review
- scenarioreviewedboundaryedge_case
Worst case: an app the user can launch is missing from the Apps menu, or a NoDisplay or hidden entry shows. boundary: an empty query lists every displayable entry (fuzzyScore returns 0 before matching); a term of five characters matches the acronym, a longer term does not. edge_case: an entry with no name falls back to its id; with neither, sortedEntries drops it. concurrency_scale not applicable: one call per menu build over an in-memory list. error_handling not applicable: keywordText catches a non-array keywords value and the rest are pure string operations.
- propertyrevieweddeterminismidempotency
determinism: for a given entry list, query and hidden callback, the returned set is fixed. idempotency: asking twice returns the same set; sortedEntries does not change its input.
- structuralnot applicable
GC'd JavaScript (the QML JS engine); no manual memory, binary framing or format strings.
- domainnot applicable
In-memory desktop-entry fields only; no network, crypto, secrets or privilege 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.
- Claude Quattro Proof · AI agentApprovedSpec conformanceOct 3, 2026 · 19 hours agoREVIEW-261003-Q2WS
Read shell/services/AppSearch.js at upstream a85e29ab. sortedEntries walks the entries once. It skips an entry that is missing or NoDisplay, one the library's hidden callback rejects, and one with no name and no id (entryName falls back to the id). It then calls fuzzyScore, which returns 0 for an empty query and -1 when allTermsMatch rejects a term, and skips a negative score. Every entry that passes all four tests is pushed once. So app_listed holds exactly when app_displayable and query_terms_matched hold. The three violation rows need one of those continue statements removed, or a push for a skipped entry; they are dispositioned defensive. termMatches matches a term against the name, the id, the joined search text (name, generic name, comment, keywords, id) or, for terms of five characters or fewer, the acronym. The requirement leaves the order out: rows sort by score when there is a query, then by lowercased name in code-unit order (KI-MENU-APPS-SORT-LOCALE). Witnesses in test/shell.d/menu-app-library-test.sh: displayable matching apps listed for an empty, a keyword, an acronym and a two-term query; NoDisplay, hidden, nameless and unmatched entries not listed.
Cited code (7)
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
the app_library shall always satisfy (app_listed <=> (app_displayable & query_terms_matched))
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| app_displayable | — | The desktop entry has a name or an id, is not marked NoDisplay, and the library does not hide it. | |
| query_terms_matched | — | Every term of the query matches the entry's name, id, generic name, comment or keywords, or a term of five characters or fewer matches its acronym. An empty query matches every entry. | |
| app_listed | — | The entry has one row in the returned list. |
Witnesses· 2 scenarios total
- menu-app-library-test.sh:1exercises 2 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| # | app_displayable | app_listed | query_terms_matched | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | app_listed | |
| 2 | F | T | F | F | app_listed | Exempted · defensive — sortedEntries skips a missing, NoDisplay, hidden or nameless entry before it scores it, so a non-displayable entry reaches rows.push only if one of those continue statements is removed (reviewed: REVIEW-261003-Q2WS) |
| 3 | F | T | T | F | app_displayable | Exempted · defensive — the displayability skips run before fuzzyScore, so a matching term cannot list an entry those skips rejected (reviewed: REVIEW-261003-Q2WS) |
| 4 | T | T | F | F | query_terms_matched | Exempted · defensive — fuzzyScore returns -1 when allTermsMatch rejects a term and sortedEntries skips a negative score, so an unmatched entry is listed only if that skip is removed (reviewed: REVIEW-261003-Q2WS) |
| 5 | T | T | T | T | app_displayable |
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)
- AppSearch.jsshell/services/AppSearch.js
Tests to re-run (1)
- menu-app-library-test.shtest/shell.d/menu-app-library-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.