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.
The script applies a picked timezone with sudo timedatectl set-timezone, refreshes the clock plugin, and sends a confirmation notification naming the new timezone.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
The script applies a picked timezone with sudo timedatectl set-timezone, refreshes the clock plugin, and sends a confirmation notification naming the new timezone.
when timezone_picked the timezone_script shall eventually satisfy timezone_set_and_refreshed
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 lines 8-10.
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 30, 2026, 07:42 UTC · Leonid Bugaev
Hazard review
- scenarioreviewedboundaryerror_handlingedge_case
Worst case: a confirmation notification fires for a timezone that was never set (user trusts a wrong clock until it matters) - closed by the set -e ladder ordering: sudo failure aborts before the clock refresh and the confirmation, so a sent notification implies a completed set. boundary: the zero case is the cancel arm - no pick exits 1 before sudo runs, touching nothing. edge_case: the picked value originates from timedatectl list-timezones (system tz database names) and is still double-quoted into the sudo call, so even a corrupted zone list cannot re-enter shell parsing; a stale zone list entry that timedatectl rejects aborts mid-ladder with no notification, which is the honest direction. Catalog 1.11.0 re-review: input_domain not applicable, the picked timezone is passed through, not parsed. concurrency_scale not applicable, one run per user action that owns its own temp files and shares no state with a concurrent run.
- propertyreviewedatomicity
The apply is a strict four-step sequence - pick, set, refresh, notify - where every failure before the notification aborts with nonzero and leaves the prior timezone intact, so the observable state transitions only on full success and the notification can never precede the commit.
- structuralnot applicable
Four fixed commands with the only variable data (the zone string) quoted end to end; no arithmetic, parsing of command output, or dynamic dispatch.
- domainreviewed
The slice contains the scripts one privileged step, sudo timedatectl set-timezone, with the zone argument quoted and the privilege shape fixed to exactly that whitelisted binary invocation - no shipped catalog class covers quoted-argument sudo hygiene, so the category records the review: least-privilege holds by construction, the menu context supplies no terminal for a password prompt (a sudo failure aborts, it never retries), and no network egress exists in the traced file. The menu-select upstream wait is dispositioned under the deferral below.
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-64
Read omarchy-menu-timezone. After a successful pick, sudo timedatectl set-timezone, the clock-plugin refresh, and the confirmation notification naming the new zone are unconditional sequence points under set -e. timezone_picked models the picker succeeding; timezone_set_and_refreshed is that sequence. 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 catalogueEvery cross-process call shall declare connect, read, and total deadlines; no external call is defaulted to "no timeout."
The timezone list flows through omarchy-menu-select, so this caller waits downstream of the unbounded done_file poll with no deadline and no peer-liveness probe - a selector that dies after summon hangs the timezone dialog, the KI reproduced defect class reaching this caller; the bound belongs to the KI fix at the poll site and bounds this caller transitively.
- nominalrequireddeferredWitnessing deferred — accepted while the tracking known issue stays open.
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_picked the timezone_script shall eventually satisfy timezone_set_and_refreshed
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_picked | timezone_set_and_refreshed | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | timezone_picked | |
| 2 | T | F | F | timezone_picked | — |
| 3 | T | T | T | timezone_set_and_refreshed |
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
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.