Proof Portal

Project overview

Omarchy

ProbeLabsviewing a historical run

A 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.

Viewing historical run 5d4fb9aOct 2, 2026, 11:50 AMquattro-proofBack to current
All requirements
RequirementSTK-REQ-260922-XTNRStakeholderReview

Users reach system actions, settings, and applications through the Omarchy menu.

All automated checks pass and 1/1 obligations are satisfied. Reviewed 5 days ago.
PriorityshallTypeguaranteeCategoryfunctionalComponentmenuAssuranceCFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

Users reach system actions, settings, and applications through the Omarchy menu. Scripts pose picker and input prompts and read back the answer. Menu rows reflect current system state without stale or contradictory display.

Rationale & tags

Why this requirement exists, and how it is categorised.

The menu is the primary UX surface of omarchy and its top churn/bug hotspot. bin/omarchy-menu history shows 304 commits, 13 bug fixes, and 3 cascade episodes. Its rows make claims about system state that must not lie.

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelC
Formalizationnone
Strategyinformal

Review

Status
in_review
Reviewer
Kimi Zero Warnings · AI agent
Reviewed
Sep 27, 2026, 23:08 UTC

History

Created
Sep 22, 2026, 13:33 UTC · Kimi Dogfood · AI agent
Modified
Sep 27, 2026, 22:35 UTC · Leonid Bugaev

Hazard review

Reviewed Oct 1, 2026, 21:26 UTCby agent:claude-baseline-passcatalog v1.11.0
  • scenarioreviewednominalerror_handlingboundaryconcurrency_scale

    Story-level partitions that decompose through the nine derived menu requirements: nominal (menu presents and routes verbs, pickers return answers) through J0AN and X6Z5, error_handling (unknown verbs and missing options answer loudly) through the dispatcher and dmenu protocol children such as SNZG and B839, boundary (comma-before-closing-brace text kept verbatim through JSONC trailing-comma stripping, per AC-002) through PPDW. Menu rows reflecting current state without stale display is the sum of the state-query children. Catalog 1.11.0 re-review: input_domain not applicable, the byte-level domains are stated on SW-REQ-260922-E4J2, SW-REQ-260922-3T3F and SW-REQ-260922-Q6ZS. concurrency_scale applied, scripts pose overlapping picker and input prompts; supersession is stated on SYS-REQ-260922-X6Z5.

  • propertynot applicable

    Story-level intent; the verbatim-text property is specified and witnessed at child PPDW, and no algebraic property is stated at this level.

  • structuralnot applicable

    Stakeholder story with no implementation at this level; the menu parser structural surfaces are recorded on the children.

  • domainnot applicable

    Menu actions execute with user privileges from the user's own config; no privilege boundary is crossed and no domain class applies_when fires for the story as written.

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.

3 obligations · 3 discharged

Browse the catalogue

Evidence tagged via <REQ> is witnessed by a requirement that satisfies this one — normal for stakeholder / aggregate requirements, which are proven through the requirements that refine them.

Discharged

Happy-path behavior with valid inputs.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
Discharged

Behavior when operations fail or dependencies are unavailable.

Discharging evidence1/1 required witnessed
Discharged

Behavior at limits, thresholds, and edge-of-range values.

Discharging evidence0/0 required witnessed

Acceptance criteria

Stakeholder conditions for satisfaction, traced to the derived requirements and evidence that discharge them.

Stakeholder-authored conditions defining when the requirement is satisfied, traced to derived requirements / evidence.

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).

If you change this

Requirements
64
Files
12
Tests
15
At-risk contracts
0

Requirements (64)

Files to re-check (12)

  • Menu.qmlshell/plugins/menu/Menu.qml
  • MenuModel.jsshell/plugins/menu/MenuModel.js
  • omarchy-menu-keybindingsbin/omarchy-menu-keybindings
  • omarchy-menu-imagesbin/omarchy-menu-images
  • omarchy-menu-pluginbin/omarchy-menu-plugin
  • omarchy-menu-timezonebin/omarchy-menu-timezone
  • omarchy-menu-sharebin/omarchy-menu-share
  • omarchy-menu-filebin/omarchy-menu-file
  • omarchy-menubin/omarchy-menu
  • BarWidget.qmlshell/plugins/menu/BarWidget.qml
  • omarchy-menu-inputbin/omarchy-menu-input
  • omarchy-menu-selectbin/omarchy-menu-select

Tests to re-run (15)

  • menu-acceptance-test.shtest/shell.d/menu-acceptance-test.sh
  • menu-dispatcher-test.shtest/shell.d/menu-dispatcher-test.sh
  • menumodel-replay.test.mjstest/node/menumodel-replay.test.mjs
  • menu-test.shtest/shell.d/menu-test.sh
  • menu-guards-test.shtest/shell.d/menu-guards-test.sh
  • menu-share-test.shtest/shell.d/menu-share-test.sh
  • menu-compositor-test.shtest/shell.d/menu-compositor-test.sh
  • report-reproducers.test.mjstest/node/report-reproducers.test.mjs
  • menu-dmenu-test.shtest/shell.d/menu-dmenu-test.sh
  • keybindings-menu-test.shtest/shell.d/keybindings-menu-test.sh
  • menu-images-test.shtest/shell.d/menu-images-test.sh
  • menu-plugin-test.shtest/shell.d/menu-plugin-test.sh
  • menu-timezone-test.shtest/shell.d/menu-timezone-test.sh
  • menu-file-test.shtest/shell.d/menu-file-test.sh
  • menu-pointer-lifecycle-test.shtest/shell.d/menu-pointer-lifecycle-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.

Sign in to discuss this with the proof team.Sign in