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.
When omarchy-apply-lock runs with EUID 0, it shall replace the inherited PATH with /usr/share/omarchy/bin:/usr/local/bin:/usr/bin:/bin before it runs any optional command.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When omarchy-apply-lock runs with EUID 0, it shall replace the inherited PATH with /usr/share/omarchy/bin:/usr/local/bin:/usr/bin:/bin before it runs any optional command.
when running_as_root the apply_lock shall always satisfy trusted_path_only
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Install and upgrade callers can start this helper as root. An inherited PATH lets a user-writable directory supply root-executed commands.
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
- Sep 12, 2026, 23:32 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedaccess_deniedboundary
Worst case: root runs the helper with a hostile inherited PATH, so a user-writable directory supplies a shadow binary executed with full root privileges during install or upgrade. access_denied: the unconditional PATH export inside the EUID==0 guard is the permission posture; the hostile-PATH execution attempt is refused by construction before any optional command runs. boundary: the EUID 0-vs-non-0 threshold is the trigger itself; the non-root arm keeps user PATH but executes nothing privileged (as_root prefixes sudo, which re-derives secure_path). Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, it rewrites PATH inside one run before any optional command; concurrent apply-lock runs share only the PAM files, whose writes are stated on SYS-REQ-260912-JW2J.
- propertynot applicable
A single unconditional assignment; there is no multi-input behavior, ordering, or repeated-application surface to constrain.
- structuralnot applicable
One static PATH string export; no memory, encoding, or format-string surface.
- domainnot applicable
control_not_silently_disabled evaluated: the control has no silently-skippable precondition path. The guard keys on EUID, not on configuration that can be absent, and the non-root arm never executes privileged commands, so there is no fail-open shape for the class to close.
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-9
Root branch matches: with EUID 0 the script replaces PATH with /usr/share/omarchy/bin:/usr/local/bin:/usr/bin:/bin before any optional command runs, matching trusted_path_only; non-root leaves PATH untouched.
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.
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 running_as_root the apply_lock shall always satisfy trusted_path_only
Witnesses· 3 scenarios total
- apply-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| # | running_as_root | trusted_path_only | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | running_as_root | |
| 2 | T | F | F | running_as_root | |
| 3 | T | T | T | trusted_path_only |
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.
2 open · 0 resolved
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 — "When omarchy-apply-lock runs with EUID 0, it shall replace…" 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.