Get updates

How it works

Intent in. Evidence out.

Every desktop-changing behaviour is intended to pass through one bounded pipeline. The system may fail to act when evidence is insufficient; it may not turn uncertainty into success merely to look reliable.

01 · Six stages, one contract

How does Orvial restore a workspace?

Gravity, Scenes, shortcuts, and any future interface use the same path. There is no faster route that skips safety or verification.

  1. 01

    Observe

    Read the current displays, applications, windows, and evidence.

  2. 02

    Resolve

    Adapt the logical Scene to the Environment that actually exists.

  3. 03

    Plan

    Calculate the smallest deterministic delta to the desired state.

  4. 04

    Safety

    Refuse unsafe or insufficiently supported actions before execution.

  5. 05

    Execute

    Apply only the actions in the bounded, attributable plan.

  6. 06

    Verify

    Re-observe the real result and report what is confirmed.

02 · Resolution, not replay

How does a Scene adapt to the desk in front of you?

Input

Logical Scene

The intended applications, windows, resources, relationships, and policies.

Context

Current Environment

The displays, roles, capabilities, and evidence available now.

Output

Resolved workspace

The desired state that can actually be satisfied on this desk.

03 · Unknown is not false

What does Orvial report when it cannot prove the result?

Seven outcomes stay distinguishable. Collapsing them into success or failure would throw away the part that makes restoration trustworthy.

Satisfied
The target already matched the desired state, so nothing moved.
Changed
A change was applied and fresh evidence confirms the result.
Fallback applied
The exact target could not be met, so a defined alternative was used and reported.
Unsupported
The platform does not permit the action here, such as leaving native fullscreen.
Unresolved
The desired state could not be safely resolved on this desk.
Unconfirmed
The action may have happened, but the available evidence cannot prove it.
Failed
The action was attempted and did not succeed.

Reliability is not polish. It is the product.

The category’s strongest complaint is not a missing animation. It is restoration that sometimes appears to work and sometimes does not.

Orvial measures desired resolved state against a newly observed final state. Recovery and reporting are driven by verification rather than optimistic command results.

Read the verification note

Follow the build

The hard parts, reported honestly.

Occasional notes on what the engine proves, and what macOS still resists.