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.
While an Omarchy update runs, the system shall hold an exclusive update lock.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
While an Omarchy update runs, the system shall hold an exclusive update lock. A second update shall not enter its pre-update snapshot while the lock is held. The system shall answer whether the caller holds the update lock.
when update_run_requested the update_lock shall always satisfy update_lock_exclusive & held_state_reported
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Two concurrent updates can interleave snapshots and package transactions. The lock makes the second update fail before it can snapshot.
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 23, 2026, 17:16 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedconcurrenterror_handlingboundaryconcurrency_scale
Parent-level partitions carried by satisfying children: concurrent via FVHS (flock contention arbiter) and 0Y70 (live held answer against holders), error_handling via FVHS (refusal diagnostic, usage exit 2) and 0Y70 (stale or foreign descriptor answers non-zero), boundary via FVHS (zero-arg, missing lock dir) and 0Y70 (descriptor edges). The embedding suggester independently ranked concurrent top for this requirement, matching the rule pass. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale applied, its whole purpose is mutual exclusion of concurrent updates.
- propertynot applicable
Decomposition-level statement; totality of the probe and run partitions is recorded on children 0Y70 and FVHS respectively.
- structuralnot applicable
Decomposition-level statement over one bash helper; structural surfaces are recorded at the child level.
- domainnot applicable
Local flock surface only; no domain class applies_when fires for filesystem mutual exclusion.
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-20
Update-lock contract matches: run holds an exclusive flock on a dedicated fd exported to the child, a second run is refused with a diagnostic before the snapshot, and held answers ownership by descriptor identity.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
1 obligation
Browse the catalogueDischarging 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 update_run_requested the update_lock shall always satisfy update_lock_exclusive & held_state_reported
Witnesses· 2 scenarios total
- update-lock-test.sh:1exercises 2 condition scenarios
MC/DC truth table· 5 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_reported | update_lock_exclusive | update_run_requested | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | F | F | T | update_run_requested | |
| 2 | F | F | T | F | update_run_requested | — |
| 3 | F | T | T | F | held_state_reported | — |
| 4 | T | F | T | F | update_lock_exclusive | — |
| 5 | T | T | T | T | held_state_reported |
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
What this rests on
Parent requirements (1)
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.