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-update-lock held shall exit 0 only when OMARCHY_UPDATE_LOCK_FD names an open descriptor.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
omarchy-update-lock held shall exit 0 only when OMARCHY_UPDATE_LOCK_FD names an open descriptor. That descriptor shall resolve to the update lock path, and flock shall take the lock on it.
when held_state_queried the update_lock shall always satisfy held_true_only_for_owning_fd
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
A bare lock-file existence check cannot tell this process's lock from another's. The descriptor identity is the proof of ownership.
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:49 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 12, 2026, 23:32 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedconcurrenterror_handlingboundaryconcurrency_scale
Worst case: a forged or stale OMARCHY_UPDATE_LOCK_FD makes held answer 0 while no lock is held, so a caller proceeds into a snapshot while another update runs and pacman transactions interleave. The /proc fd-existence check, readlink -f identity against the canonical lock path, and the final flock -n arbiter close that chain; -f vs -m canonicalization means alias paths compare equal only for the true lock inode. concurrent: the answer is defined against live lock contention and flock -n can never block. error_handling: unset, dangling, and wrong-file descriptors must answer non-zero, never crash or hang. boundary: descriptor-present-but-foreign and vanishing-between-check-and-readlink are the tested stale-descriptor edges. Catalog 1.11.0 re-review: input_domain not applicable, it reads a descriptor number from the environment, not text. concurrency_scale applied, the update lock exists to serialize concurrent updates: one holder, a second caller answered by flock on the shared lock file.
- propertyreviewedtotality
Every reachable OMARCHY_UPDATE_LOCK_FD value yields an exit 0/1 answer; flock -n is non-blocking so the probe is total over its input space and cannot hang waiting on a holder.
- structuralnot applicable
Pure bash byte-comparison of two readlink outputs against a fixed path; no manual memory, pointers, format-string sinks, or encoding round-trips. The unset-variable case is the nil case and is specified by the contract itself.
- domainnot applicable
Local filesystem plus flock only; no network, crypto, SQL, transport, or browser workload, and the requirement carries no domain tags, so no domain class applies_when fires.
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-15
held exits 0 only when OMARCHY_UPDATE_LOCK_FD is an open descriptor resolving to the lock path and flock can take it on that descriptor; descriptor identity (not path existence) is the ownership proof, matching held_true_only_for_owning_fd. All three MC/DC rows are witnessed in update-lock-test.sh.
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 held_state_queried the update_lock shall always satisfy held_true_only_for_owning_fd
Witnesses· 3 scenarios total
- update-lock-test.sh:1exercises 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.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | held_state_queried | held_true_only_for_owning_fd | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | held_state_queried | |
| 2 | T | F | F | held_state_queried | |
| 3 | T | T | T | held_true_only_for_owning_fd |
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-update-lockbin/omarchy-update-lock
Tests to re-run (1)
- update-lock-test.shtest/shell.d/update-lock-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.