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.
An entry with action is an action, with target a link, otherwise a menu.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
An entry with action is an action, with target a link, otherwise a menu. An undeclared parent derives from the dotted id (or root). Root's parent is empty.
when entry_shape_declared the menu_model shall eventually satisfy kind_and_parent_inferred
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
MenuModel.js normalizeItem lines 13-40.
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 27, 2026, 21:25 UTC · Kimi Zero Warnings · AI agent
Hazard review
- scenarioreviewedmalformed_inputboundaryedge_case
Worst case: an entry whose declared shape is ambiguous or hostile - action AND target both present, an id with leading/trailing/double dots, or a non-object raw - normalizes into a tree node that silently loses a declared behavior (link target dropped because kind precedence picks action) or derives a parent that matches no other node (empty-string parent from an id like .x), so the row never renders or renders at the wrong depth. malformed_input: raw||{}, the action-over-target precedence, and the dotted-id derivation are exactly the declared-shape handling this class names, and the shipped config is user-extensible so shapes beyond the happy path are reachable. boundary: id==root forcing empty parent versus derived root parent is the identity edge of the tree; the three-way kind precedence is the type boundary. edge_case: explicit parent overriding the derived one, and dotted ids of every arity, are the witnessed corners. Catalog 1.11.0 re-review: input_domain not applicable, entries reach it already parsed by SW-REQ-260922-E4J2. concurrency_scale not applicable, a pure function of its arguments, recomputed on each load or keystroke: no state across calls, no process, timer or lock.
- propertyreviewedtotality
Every (id, raw) pair yields a fully defined item object: raw defaults to {}, kind is always one of action/link/menu, parent is always a string (dotted derivation, root literal, or declared), label defaults to the id. No config shape can make normalizeItem return a partial node that downstream tree building trips over.
- structuralreviewednil_safety
The function's whole job is absorbing zero-value input: a null/undefined/non-object raw becomes {}, missing strings default at every field (icon, iconFont, label, title), and the undefined-parent check is the nil case the contract itself specifies - that is the nil_safety obligation, witnessed by config fixtures with missing fields.
- domainnot applicable
In-process config-object normalization; no file, IPC payload, network, crypto, or privilege surface - the JSONC reading and file watching are owned by the source-loading sibling requirements.
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-36
Read normalizeItem. kind is decided by the exact chain the description states: action present -> action, else target present -> link, else menu; an undeclared parent derives from the dotted id prefix, defaulting to root, and root's parent is forced empty. Both branch chains map one-to-one onto kind_and_parent_inferred under entry_shape_declared. 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.
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 entry_shape_declared the menu_model shall eventually satisfy kind_and_parent_inferred
Witnesses· 2 scenarios total
- menu-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| # | entry_shape_declared | kind_and_parent_inferred | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | entry_shape_declared | |
| 2 | T | F | F | entry_shape_declared | — |
| 3 | T | T | T | kind_and_parent_inferred |
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 (2)
- Menu.qmlshell/plugins/menu/Menu.qml
- MenuModel.jsshell/plugins/menu/MenuModel.js
Tests to re-run (2)
- menumodel-replay.test.mjstest/node/menumodel-replay.test.mjs
- menu-test.shtest/shell.d/menu-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.