See the rule before trusting it

A quiet-hours setting you can rehearse.

User problem. Quiet-hours rules are hard to trust because people cannot predict which notifications will be delayed, delivered, or treated as urgent until the rule is already live.

Proposed feature. Let users configure a quiet window and run a sample day through it before saving anything.

Assumed data flow

Rule simulation

Run a sample notification day

Nothing is saved or sent

Quiet window starts

Quiet window ends

Urgent policy

Ready — adjust the rule, then run.

Alternative directions

What should the feature optimize for?

Evidence boundary

What this concept knows—and does not

KnownUsers can compare visible rule outcomes in this self-contained simulation.

AssumedA preview would increase confidence before enabling quiet hours.

UnknownWhether real notification sources expose reliable urgency signals.

PlaceholderSample people, messages, times, and classification rules are illustrative.

Interactive system states

Tap each state to preview it

Each card is now an explicit control

State preview ready.Select Empty, Loading, Error, or Permission.

Structured review

Mark up the direction

Exports JSON only

Keep · timeline simulationThe concrete event-by-event explanation.

Keep · evidence boundaryThe known, assumed, unknown, and placeholder framing.

Change · rule controlsThe current start, end, and urgency configuration.

Change · visual hierarchyThe balance between setup and result detail.

Cut · summary alternativeRemove direction B from the next revision.

Free-form feedback

Open questions · one per line

Ready. Every action will report its result here.

Selectable JSON fallback · always available