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.
Cancelling the timezone picker exits 1 before any timedatectl set-timezone invocation.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
Cancelling the timezone picker exits 1 before any timedatectl set-timezone invocation.
when timezone_pick_cancelled the timezone_script shall eventually satisfy timezone_not_set
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
bin/omarchy-menu-timezone line 7.
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 Zero Warnings · AI agent
- Reviewed
- Sep 27, 2026, 21:25 UTC
History
- Created
- Sep 22, 2026, 13:34 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 27, 2026, 21:25 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewederror_handlingboundary
Worst case: a cancelled or failed pick still reaches sudo timedatectl set-timezone - either silently changing the zone from a stale answer or invoking it with an empty zone string. The || exit 1 after the picker pipeline is the whole guard: any picker failure (cancel exit 1, empty selection exit 1, IPC dead) aborts before the set call, and set -e plus the pipeline's last-command semantics make the picker's own status the branch. boundary: picker exit 0 with an empty zone string - list-timezones broken while the picker answers - is the residual edge where set-timezone runs with an argument; it fails loudly in timedatectl rather than setting a wrong zone, and the non-cancel contract (set+refresh) is SWFT's subject. error_handling is the subject: every failure of the picker lands in exit 1 before the privileged call. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, one run per user action that owns its own temp files and shares no state with a concurrent run.
- propertyreviewedtotality
Every picker outcome maps to exactly one of two defined endings - exit 1 with no timedatectl set call, or set-timezone with the picked zone - so no cancellation shape leaves the script in a half-run state with a pending privileged invocation.
- structuralnot applicable
Three-line bash pipeline; the zone string is passed as a single quoted argv element, no parsing, arithmetic, or encoding transform, and the unset/empty variable case is the boundary recorded under scenario.
- domainnot applicable
The cross-process calls here are an interactive picker whose wait is bounded by the user closing it - that is the declared deadline for an interactive surface - and timedatectl bus calls that ride systemd-timedated's own documented D-Bus timeouts; no socket, network, or privilege-boundary cross is made by this script itself (sudo is the shipped mechanism, invoked non-interactively via the desktop's credential broker), so no timeout-bounded or other domain class adds a distinct obligation.
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 Zero Warnings · AI agentApprovedSpec conformanceSep 27, 2026 · 5 days agoREVIEW-38
Read omarchy-menu-timezone: the picker call carries '|| exit 1' and the timedatectl set-timezone invocation sits after it, so a cancelled pick exits 1 before any set-timezone runs. The timezone_pick_cancelled condition models exactly that short-circuit branch; there is no other path to the set call. Formula conforms to the code.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
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 timezone_pick_cancelled the timezone_script shall eventually satisfy timezone_not_set
Witnesses· 2 scenarios total
- menu-timezone-test.sh:1exercises 2 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.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | timezone_not_set | timezone_pick_cancelled | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | timezone_pick_cancelled | |
| 2 | F | T | F | timezone_not_set | Exempted · defensive — a cancelled pick takes `|| exit 1` before any set-timezone call; setting a zone from a cancelled pick is structurally absent mcdc:witness-out-of-process (reviewed: REVIEW-M3) |
| 3 | T | T | T | timezone_not_set |
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).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Files to re-check (1)
- omarchy-menu-timezonebin/omarchy-menu-timezone
Tests to re-run (1)
- menu-timezone-test.shtest/shell.d/menu-timezone-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.