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 d52c386Oct 2, 2026, 12:13 AMpr/9056Back to current
All requirements
RequirementSW-REQ-260922-SNZGSoftwareReview

An unknown verb prints 'omarchy-menu: unknown verb' naming the verb to stderr and exits 2.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass.
PriorityshallTypeguaranteeCategoryfunctionalComponentmenuAssuranceCFindingsLowworst open

Specification

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

Description

An unknown verb prints 'omarchy-menu: unknown verb' naming the verb to stderr and exits 2.

FRETish formula
when verb_unknown the menu_dispatcher shall eventually satisfy diagnostic_printed & exit_two
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

bin/omarchy-menu lines 48-51; exit 2 keeps misuse distinct from runtime failure.

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
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

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

Reviewed Sep 30, 2026, 07:40 UTCby agent:opencode-hazard-ccatalog v1.10.1
  • scenarioreviewedboundaryerror_handlingedge_case

    Worst case: a caller scripts omarchy-menu <typo> in a chain and misreads exit 2 as success - the taxonomy is the mitigation: usage errors (missing args) exit 1, unknown verbs exit 2, so programmatic callers get two distinct failure classes, and the diagnostic names the offending verb plus the --help pointer on stderr where it cannot be mistaken for output. boundary: the case dispatch is total - every known verb, --help (exit 0), and the catch-all unknown arm - with no argv shape falling off the dispatcher. edge_case: the raw verb is echoed unquoted into the message, so terminal escape bytes in a hand-typed verb render raw in the user own terminal; the source is the user own command line (self-owned authority, same as any command echoing its arguments), and the bytes pass to stderr only, never to a parser.

  • propertyreviewedtotality

    Every argv resolves to exactly one dispatcher ending - a known verb dispatch, help text with exit 0, or the unknown diagnostic with exit 2 - with no input reaching an undefined fall-through or double exit.

  • structuralnot applicable

    A case allowlist, one stderr echo, and exit codes; the verb is never evald, dispatched through, or interpolated into a command - unknown input can only become message text.

  • domainnot applicable

    stderr text to the user own terminal from the user own argv; no trust boundary is crossed, and no network, crypto, privilege, or wait surface exists in the dispatcher arm.

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.

  1. Kimi Zero Warnings · AI agentApprovedSpec conformanceSep 27, 2026 · 5 days agoREVIEW-63

    Read omarchy-menu. The verb case falls through to an arm that prints 'omarchy-menu: unknown verb' naming the verb to stderr and exits 2. verb_unknown models the case default; diagnostic_printed and exit_two are that arm's two actions. 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.

Discharging tests pending a synced audit.

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 verb_unknown the menu_dispatcher shall eventually satisfy diagnostic_printed & exit_two

Witnesses· 2 scenarios total

  • menu-dispatcher-test.sh:1
    exercises 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.

Covereda test exercises this rowExempteda reviewed mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test
#diagnostic_printedexit_twoverb_unknownResultProvesCovering test
1FFFTverb_unknown
2FFTFverb_unknown—
3FTTFdiagnostic_printed—
4TFTFexit_two—
5TTTTdiagnostic_printed

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

If you change this

Nothing downstream depends on this yet

No downstream impact — "An unknown verb prints 'omarchy-menu" has no downstream edges.

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