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 89b2c1eSep 29, 2026, 09:42 AMpr/9056Back to current
All requirements
RequirementSTK-REQ-260922-XTNRStakeholderDraft

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 (visibility guards, checkmarks, installed-dimmed rows) without stale or contradictory display.

Automated checks pass.
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 (visibility guards, checkmarks, installed-dimmed rows) 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 the #1 churn/bug hotspot (bin/omarchy-menu: 304 commits, 13 bug fixes, 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
pending

History

Created
Sep 22, 2026, 13:33 UTC · Kimi Dogfood · AI agent
Modified
Sep 25, 2026, 09:23 UTC · Kimi Upstream Refresh · AI agent

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.

Discharging tests pending a synced audit.

Discharging tests pending a synced audit.

Discharging tests pending a synced audit.

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
59
Files
0
Tests
0
At-risk contracts
0

Requirements (59)

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