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 fingerprint authentication is available, the lock view shall show the fingerprint indicator next to the password field.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When fingerprint authentication is available, the lock view shall show the fingerprint indicator next to the password field. When no fingerprint sensor is available, the lock view shall reserve no space for the indicator.
when fingerprint_sensor_configured the lock_view shall always satisfy fingerprint_indicator_tracks_sensor
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
An indicator without a working sensor invites a touch that can never authenticate. Space reserved for a missing sensor shifts the password field.
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:51 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 12, 2026, 23:32 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedboundary
Worst case: an indicator shown with no sensor invites a touch that can never authenticate, and reserved space for a missing sensor shifts the password field. The configured/not-configured threshold is the whole trigger: the binding is fingerprintConfigured ? iconWidth+12 : 0, so both arms are the boundary pair. Catalog 1.11.0 re-review: input_domain not applicable, it reads no external text input. concurrency_scale not applicable, view state recomputed from the current rows on each UI event: no process, timer or lock, and events are handled one at a time.
- propertyreviewedtotality
Every fingerprintConfigured value yields a fully defined layout (indicator visibility plus reserved margins); both arms are witnessed by lock-fingerprint-indicator-test.sh.
- structuralnot applicable
QML declarative binding over a boolean and a measured glyph width; the icon text is a static string, so there is no encoding transform, numeric edge, or memory surface.
- domainnot applicable
Display-only layout; no trust boundary is crossed, no external call is made, and no auth decision is computed here.
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-5
Fingerprint indicator visibility is bound to sensor configuration state; when no sensor is configured the indicator reserves no layout space, matching fingerprint_indicator_tracks_sensor in both polarities.
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 fingerprint_sensor_configured the lock_view shall always satisfy fingerprint_indicator_tracks_sensor
Witnesses· 2 scenarios total
- lock-fingerprint-indicator-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| # | fingerprint_indicator_tracks_sensor | fingerprint_sensor_configured | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | fingerprint_sensor_configured | |
| 2 | F | T | F | fingerprint_indicator_tracks_sensor | Exempted · defensive — the indicator visibility is a declarative binding on the sensor-configured state; an untracked indicator needs a broken binding, not a reachable input (reviewed: REVIEW-5) |
| 3 | T | T | T | fingerprint_indicator_tracks_sensor |
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)
- LockView.qmlshell/plugins/lock/LockView.qml
Tests to re-run (1)
- lock-fingerprint-indicator-test.shtest/shell.d/lock-fingerprint-indicator-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.