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.
A value command shared by several guards (e.g.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
A value command shared by several guards (e.g. omarchy-default-browser across seven rows) runs once per batch, captured eagerly before any guard line.
when reader_value_reused the guard_pipeline shall eventually satisfy reader_read_once
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
MenuModel.js guardPrelude lines 443-456; a lazy memo would die in the $() subshell.
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:46 UTC · Leonid Bugaev
Hazard review
- scenarioreviewedboundaryedge_case
Worst case: a shared reader with side effects (a counter, a cache write) executes once per referencing guard line instead of once per batch - the substitution covers only the plain $(reader) form, and documented non-plain forms (VAR=x reader, command -v reader, nested substitutions) are deliberately left to run the real command at eval time, so read-once holds exactly for the contract shape and degrades to repeated execution outside it; consequence is duplicate side effects and a slower batch, accepted and documented in MenuModel.js. boundary: a reader referenced by zero guards emits no capture line at all (the slot-membership test) - the read-once-only-when-shared half. edge_case: a reader exiting nonzero captures empty under the ||: isolation, so its dependents evaluate against an empty value (typically a false answer) instead of killing the batch, and one hung reader stalls the eager prelude - the freshness-only stall family dispositioned at MQ37. Catalog 1.11.0 re-review: input_domain not applicable, guard expressions reach it already parsed by SW-REQ-260922-E4J2. concurrency_scale not applicable, shared value commands are deduplicated within one generated batch; batch overlap is stated on SW-REQ-260922-4079.
- propertyrevieweddeterminismidempotency
determinism: slot numbering is fixed by GUARD_READERS order and the same items always produce the same prelude with the same captured values. idempotency: re-deriving the script over unchanged items repeats no reader execution beyond the one eager capture per used reader - the read-once property the requirement names.
- structuralnot applicable
Literal string substitution of $(reader) for an index-derived slot name over config-owned text; no eval on the JS side, no collision across slot indices, and an adversarial literal slot in a user expression is same-authority self-config, not an injection path.
- domainnot applicable
Readers are user-authored shell running with the user own authority - the same boundary MQ37 dispositioned for the generated script; the substitution adds no privilege, network, or crypto surface.
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-67
Read guardPrelude. A reader marked wanted by its substitution slot is captured once, eagerly, into __omarchy_read_<i> before any guard line ('|| :' keeps a nonzero reader from killing the batch under errexit), and every guard referencing it reads the captured slot. reader_value_reused models the shared-slot case; reader_read_once is the single eager capture. 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 reader_value_reused the guard_pipeline shall eventually satisfy reader_read_once
Witnesses· 2 scenarios total
- preludeexercises 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| # | reader_read_once | reader_value_reused | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | reader_value_reused | |
| 2 | F | T | F | reader_read_once | — |
| 3 | T | T | T | reader_read_once |
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)
- MenuModel.jsshell/plugins/menu/MenuModel.js
Tests to re-run (1)
- menu-guards-test.shtest/shell.d/menu-guards-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.