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.
omarchy-hyprland-session-locked shall exit 0 when any monitor lists LOCK in solitaryBlockedBy.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
omarchy-hyprland-session-locked shall exit 0 when any monitor lists LOCK in solitaryBlockedBy. It shall exit 1 when no monitor shows LOCK and at least one monitor is not blocked by WORKSPACE. It shall exit 2 when hyprctl fails or every monitor answer comes back undetermined.
when lock_state_queried the session_locked shall always satisfy exit_zero_on_lock & exit_one_on_answerable_unlocked & exit_two_on_undetermined
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Hyprland stops at the first solitary blocker on a monitor with no workspace yet, so a missing LOCK there means the probe never asked. Callers that branch only on success treat 2 as unlocked.
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 Dogfood · AI agent
- Reviewed
- Sep 12, 2026, 23:50 UTC
History
- Created
- Sep 12, 2026, 19:43 UTC · Kimi Dogfood · AI agent
- Modified
- Oct 1, 2026, 21:28 UTC · Claude Quattro · AI agent
Hazard review
- scenarioreviewedmalformed_inputboundaryedge_caseinput_domainconcurrency_scale
Worst case: a caller that cannot distinguish undetermined from unlocked acts on unknown state. malformed_input: unparsable or empty monitor JSON yields an empty state that exits 2. boundary: the answerable partition is the elif on WORKSPACE readability separating exit 1 from exit 2. edge_case: a monitor with no workspace stops at the first solitary blocker before LOCK is consulted, the documented Hyprland behavior that forces the re-ask semantics. error_handling is suppressed, pointer to the existing obligation_suppressions entry: the 3-state contract makes set -e/pipefail wrong; hyprctl and jq failures are handled explicitly as exit 2. Catalog 1.11.0 re-review: input_domain applied, it parses hyprctl -j monitors output; that producer emits machine-generated ASCII JSON, so BOM, Unicode whitespace and CR partitions cannot arise, and unparsable or empty output is the malformed_input partition already applied here (exit 2). concurrency_scale applied, the stranded-lock recovery calls this probe repeatedly on a timer and it spawns hyprctl each time; the call-without-deadline exposure is the deferred external_call_timeout_bounded obligation.
- propertynot applicable
Stateless single-shot probe over one hyprctl snapshot; no algebraic, ordering, or repeated-application surface beyond the three-exit partition recorded under scenario.
- structuralnot applicable
jq filter over compositor output dispatched through a bash case; no memory, pointer, format-string, or encoding surface.
- domainreviewed
external_call_timeout_bounded evaluated and DEFERRED (see obligation_deferrals): hyprctl -j monitors on line 17 has no timeout wrapper, and a stalled Hyprland IPC is documented as real during lid transitions; the probe then hangs, stranded-lock recovery exhausts its retry budget unresolved, and the Hyprland failsafe lock remains the backstop. Tracked debt, not an accepted gap.
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 Dogfood · AI agentApprovedSpec conformanceSep 12, 2026 · 3 weeks agoREVIEW-12
Exit-code triage matches the conjunction: 0 when any monitor lists LOCK in solitaryBlockedBy, 1 when none shows LOCK and at least one monitor answers (not blocked by WORKSPACE), 2 when the state cannot be determined. The sole decision is an exit-status-constant idiom, dispositioned via tooling-limit ignore.
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 cataloguehyprctl -j monitors has no timeout wrapper; a stalled Hyprland IPC, documented as real during lid transitions, hangs the probe, so stranded-lock recovery liveness is lost until the retry budget exhausts; the Hyprland failsafe lock remains the backstop. Reproduced and tracked on KI-LOCK-PROBE-HYPRCTL-NO-TIMEOUT with a green tripwire (the real probe is still blocked at an external watchdog while hyprctl stalls).
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).
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 lock_state_queried the session_locked shall always satisfy exit_zero_on_lock & exit_one_on_answerable_unlocked & exit_two_on_undetermined
Witnesses· 2 scenarios total
- hyprland-session-locked-test.sh:1exercises 2 condition scenarios
MC/DC truth table· 6 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| # | exit_one_on_answerable_unlocked | exit_two_on_undetermined | exit_zero_on_lock | lock_state_queried | Result | Proves | Covering test |
|---|---|---|---|---|---|---|---|
| 1 | F | F | F | F | T | lock_state_queried | |
| 2 | F | F | F | T | F | lock_state_queried | — |
| 3 | F | T | T | T | F | exit_one_on_answerable_unlocked | — |
| 4 | T | F | T | T | F | exit_two_on_undetermined | — |
| 5 | T | T | F | T | F | exit_zero_on_lock | — |
| 6 | T | T | T | T | T | exit_one_on_answerable_unlocked |
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
Nothing downstream depends on this yet
No downstream impact — "omarchy-hyprland-session-locked shall exit 0 when any…" 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.