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.
enable offers disabled plugins; disable offers enabled canDisable plugins; clone offers first-party plugins no installed clone points back at; remove offers non-first-party plugins.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
enable offers disabled plugins; disable offers enabled canDisable plugins; clone offers first-party plugins no installed clone points back at; remove offers non-first-party plugins.
when picker_verb_given the plugin_picker shall eventually satisfy verb_filter_applied
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
bin/omarchy-menu-plugin lines 12-21; menu-plugin-test.sh pins each filter.
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 30, 2026, 07:33 UTC · Leonid Bugaev
Hazard review
- scenarioreviewedboundaryedge_caseerror_handling
Worst case: a jq filter bug turns remove into a destructive verb aimed at first-party plugins, which cannot be re-fetched after deletion. The filter is (.firstParty | not), so a plugin record whose firstParty marker is absent (structural-trust inversion: the inventory flag gates a destructive verb) falls on the removable side - mitigated by the fact that clones are legitimately non-first-party, the id is cut from the returned row not re-derived, and omarchy-plugin-remove re-checks what it is deleting; residual consequence needs a defective inventory generator. boundary: one filter per verb is the exact partition, allowlisted by the case. edge_case: a tab inside a plugin name shifts the cut -f2 id column (line protocol), and the action then misses the intended plugin - ids are slugs, so a collision with a different plugin is implausible. error_handling: a plugin-list failure kills under set -e before any listing; empty rows notify and exit 0 per the sibling QMWP contract. Catalog 1.11.0 re-review: input_domain not applicable, plugin state comes from the installed plugin list, not from a parsed text file. concurrency_scale not applicable, one run per user action that owns its own temp files and shares no state with a concurrent run.
- propertyrevieweddeterminismtotality
determinism: rows preserve the jq array order of the plugin-list JSON for a given inventory state; every verb yiedlds the same set across runs. totality: every (verb, plugin state) combination resolves to a defined row set - enabled, canDisable-and-enabled, firstParty-not-cloned, or non-firstParty - and every downstream ending (empty notify, dismissal, missing-id exit 1, dispatch) is pinned.
- structuralnot applicable
Bash with all dynamic values safe by construction: the id reaches jq-free dispatch as a single quoted argv (omarchy-plugin-$1 with a case-allowlisted verb), terminal launchers receive printf %q-quoted ids, and no payload is evald or word-split beyond the row tab protocol.
- domainnot applicable
Local plugin inventory plus the omarchy-menu-select IPC summon owned by the protocol siblings (Q6ZS/9ABD); no network egress, crypto, or privilege boundary in the filter-and-dispatch slice this requirement governs.
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-53
Read omarchy-menu-plugin. The verb case maps enable to disabled plugins, disable to enabled canDisable ones, clone to first-party plugins with no installed clone pointing back, and remove to non-first-party plugins; rows come from select($filter) unconditionally. The picker_verb_given condition models the verb-case branch; verb_filter_applied is the per-verb jq filter. 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 · 1 deferred
Browse the catalogueEvery cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."
The picker hands its rows to omarchy-menu-select and waits synchronously downstream of the unbounded done_file poll with no deadline and no peer-liveness probe: a menu that dies after summon hangs every omarchy-menu-plugin caller - the KI reproduced defect class reaching this caller. The bound belongs to the KI fix at the poll site, which bounds this caller transitively.
- nominalrequireddeferredWitnessing deferred — accepted while the tracking known issue stays open.
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 picker_verb_given the plugin_picker shall eventually satisfy verb_filter_applied
Witnesses· 2 scenarios total
- menu-plugin-test.sh:1exercises 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| # | picker_verb_given | verb_filter_applied | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | picker_verb_given | |
| 2 | T | F | F | picker_verb_given | — |
| 3 | T | T | T | verb_filter_applied |
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)
- omarchy-menu-pluginbin/omarchy-menu-plugin
Tests to re-run (1)
- menu-plugin-test.shtest/shell.d/menu-plugin-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.