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 20d4e6aOct 2, 2026, 05:32 PMquattro-proofBack to current
All requirements
RequirementSW-REQ-260922-9DMSSoftwareReview

A code:N binding shows the keysym resolved from the compiled keymap, or the built-in fallback table when xkbcli cannot resolve it; GRAVE displays as ~.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass and 0/1 obligations are satisfied.
PriorityshallTypeguaranteeCategoryfunctionalComponentmenuAssuranceCFindingsLowworst open

Specification

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

Description

A code:N binding shows the keysym resolved from the compiled keymap, or the built-in fallback table when xkbcli cannot resolve it; GRAVE displays as ~.

FRETish formula
when keycode_binding the keybindings_menu shall eventually satisfy symbol_resolved
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

bin/omarchy-menu-keybindings parse_keycodes lines 13-46.

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:34 UTC · Kimi Dogfood · AI agent
Modified
Oct 1, 2026, 21:29 UTC · Claude Quattro · AI agent

Hazard review

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

    Worst case: the menu mislabels a binding - a resolved symbol from the wrong keymap section shadows a correct fallback, or an unknown code renders raw as code:N - misleading a user hunting for a keybinding, cosmetic and graded low because dispatch uses the binding's own expression, never the displayed symbol. error_handling is the subject: xkbcli failure or an empty keymap degrades to the built-in fallback table, and </dev/null on the xkbcli pipe keeps a keymap read from consuming binding records on stdin - the composition trap this design closes. boundary: fallback-table codes are the fixed enumerated set (10..21, 59..61) plus mouse 272-274; a code outside both the keymap and the table is the uncovered edge that falls back to raw display. edge_case: GRAVE rewriting to ~ is a display convention over the layout-dependent keysym, so the symbol tracks whichever key the active layout puts left of 1 - witnessed by the source-derived keymap parse. Catalog 1.11.0 re-review: input_domain applied, it reads xkbcli keymap output and a built-in table; the producer emits machine-generated text, and an unresolvable code falls back to the table (already applied as error_handling). concurrency_scale not applicable, one keymap resolution per menu build.

  • propertyrevieweddeterminism

    Given one compiled keymap, every binding resolves to the same symbol on every menu build: the awk pass folds code_by_name and sym_by_name once, the fallback table is a fixed literal, and later keymap entries overwrite earlier ones deterministically rather than by iteration order - the menu shows a stable label for a stable configuration.

  • structuralnot applicable

    awk associative arrays over regex-matched string fields; no memory, pointer, or encoding surface, and the toupper normalization is a display convention on an internal symbol vocabulary, not a round-trip.

  • domainreviewed

    Two cross-process reads (hyprctl binds, xkbcli compile-keymap) feed this resolution, both without deadline wrappers; the class that names this hazard is accepted as tracked debt rather than suppressed, because a stalled Hyprland IPC is documented as real during lid transitions and xkbcli inherits the same exposure - the deferral entry records the consequence and the tracking ref.

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-43

    Read omarchy-menu-keybindings. A code:N binding resolves its keysym from the compiled keymap via xkbcli, falling back to the built-in table when xkbcli cannot resolve; GRAVE displays as ~ (asserted in keybindings-menu-test.sh). The keycode_binding condition models the code:-form branch; the fallback is part of the resolution path, not a silent precondition. 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 catalogue
Deferred

Every cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."

hyprctl binds (cache key and dynamic_bindings) and xkbcli compile-keymap run with no timeout wrapper; a stalled Hyprland IPC - documented as real during lid transitions - or a wedged xkbcli keymap compile hangs the keybindings menu build with no backstop, the same exposure deferred on EH0K for hyprctl -j monitors. Reproduced and tracked on KI-MENU-KEYBINDINGS-NO-TIMEOUT with a green tripwire covering both calls.

Discharging evidence0/1 required witnessed
  • nominalrequireddeferred
    Witnessing deferred — accepted while the tracking known issue stays open.

Code signals

Static-analysis signals from external scanners that bear on this requirement's obligations — the source location, the obligation each touches, and its closure status.

  • Suppressedbuiltinstrict_mode_missing
    Obligation: Error handling · Scenario

    Behavior when operations fail or dependencies are unavailable.

    script runs pipelines without `set -e`/`set -o pipefail`

    Suppression rationale: bin/omarchy-menu-keybindings is a read-only display-formatting script: it runs hyprctl/xkbcli/awk pipelines whose worst-case failure is an empty or partial keybinding list presented in the menu. It mutates no state. set -e/pipefail would turn a transient tooling failure (missing xkbcli off Hyprland) into a hard abort of a menu the user invoked for something else. Recorded as an intentional degradation-not-corruption contract; no per-call guards exist upstream, which this suppression documents rather than excuses.

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 keycode_binding the keybindings_menu shall eventually satisfy symbol_resolved

Witnesses· 3 scenarios total

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

Covereda test exercises this rowExempteda reviewed mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test
#keycode_bindingsymbol_resolvedResultProvesCovering test
1FFTkeycode_binding
2TFFkeycode_binding
3TTTsymbol_resolved

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

Requirements
0
Files
1
Tests
1
At-risk contracts
0

Files to re-check (1)

  • omarchy-menu-keybindingsbin/omarchy-menu-keybindings

Tests to re-run (1)

  • keybindings-menu-test.shtest/shell.d/keybindings-menu-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