Sometimes the Best Interface Adds Friction

At the start of an evening study session, Priya says: For this session, I want to finish this paper first. Remind me before I open another one. Twenty minutes later, a new result arrives through her semantic subscription. She reaches to open it.

The channel shows a line beside the action: You asked for a reminder before opening another paper. She can continue with the paper in front of her or open the new result immediately. The reminder makes the choice visible without taking it away.

The earlier request and the present choice both belong to Priya. The system has no independent objective to settle their disagreement. Its authority comes from the support she requested.

This is a constructed scene, not evidence that a reminder improves concentration. It exposes a narrower question:

When may an intelligent channel deliberately make an immediate action harder?

The governing boundary is:

The system may add friction only in service of an objective the user has actually supplied.

That is a necessary condition, not permission to use any means available. A goal identifies what the intervention may serve. The person must also supply or accept the kind of intervention, the scope in which it applies, and a way to end it.

user-authored goal ≠ system-inferred benefit
support ≠ control

A goal does not authorise every intervention

Priya could say that she wants to finish the paper without asking for any intervention. The channel may offer a reminder rule for her to accept. It cannot turn the aspiration into permission to block navigation, impose a delay or hide other sources.

In the opening scene, she asked for a reminder. That makes the authorised support concrete. A reminder does not become a confirmation gate merely because she ignores it. A confirmation does not become a restriction because the system thinks a stronger measure would work better.

The same boundary excludes goals the system invents. Reading for an hour does not authorise it to conclude that Priya needs less reading. Opening several sources does not establish a failure of attention. A prediction that she would benefit from stopping is still a prediction, not an instruction from her.

The channel can make a proposal. Priya can accept it, revise it or decline it. Without an applicable authorised rule, the default is ordinary access, with no added friction justified by an inferred benefit.

The small contract

The rule needs enough detail to make its effect inspectable. For the current session, a small illustrative contract would suffice:

Goal:          Finish the current paper before opening another.
Target action: Opening another paper in this reading tool.
Intervention:  Show a reminder beside the action.
Override:      Open it now, without further confirmation.
Scope:         This evening's study session.
Expires:       When this paper is finished or the session ends.
Source:        Priya's explicit request at the start of the session.

These are explanatory fields, not a fixed implementation schema. They separate the goal from the action affected, the permitted intervention from stronger alternatives, and this session from future reading. The source explains why the channel intervened; the scope and expiry explain why it may intervene now.

A stored contract can remain historically accurate after it expires. That does not make it active. As Chapter 23 established, remembering a request and applying it now are separate decisions. A rule for this evening must not reappear next week because the system faithfully retained it.

Start with the weakest authorised form

The first intervention should be the weakest form that can provide the support Priya requested. In this case, a short reminder beside an ordinary action is enough to make her earlier instruction available at the point of choice. It need not interrupt the reading view or demand an explanation.

Other contracts could authorise a confirmation, an extra step or a short delay. Those are different burdens, not interchangeable renderings of the same permission. A stronger form needs an explicit decision about that form. The channel must not experiment with escalating interventions because Priya repeatedly proceeds past the weaker one.

Sometimes the least intrusive support is a stopping point. If she asks for a notice at the end of a set of three papers, the channel can mark its end: That is the set you chose. Continue? The boundary comes from her plan and the notice from her request. The system does not decide how much reading is enough for her.

Choosing a weak intervention does not establish that it will help. The design principle limits the burden imposed under a rule; it is not a claim that a particular reminder or delay has been shown effective.

The reason stays visible

At the moment friction appears, Priya should be able to see the condition that triggered it and the instruction that authorised it. You asked for a reminder before opening another paper gives her something she can recognise and correct.

You are getting distracted again gives her a diagnosis instead. It changes a scoped request into a judgement about the person. Even if she opens several papers, that observation cannot supply the missing authority.

The wording should report what the contract says, without arguing that Priya is wrong to override it. A reason becomes cosmetic if the channel displays her instruction but then makes the alternative difficult to find. Provenance, visible choices and actual control have to agree.

authorised friction
+ visible reason
+ easy override
+ explicit expiry

Those properties belong to the same intervention. They cannot be distributed across a reminder she sees now, a settings page she may discover later and an expiry the system never shows her.

Override changes this action, not the goal

Suppose the new paper contains the missing premise for the one Priya is reading. She chooses Open it now. The action must proceed without another prompt defending the rule she just overrode.

That choice is a local exception. It does not establish that she has abandoned the goal of finishing the first paper. It does not delete the contract, change her default, or become evidence that she lacks the resolve to follow a plan.

Three decisions remain distinct:

override this intervention
≠
revise or revoke the rule
≠
change the goal

Priya may make any of them explicitly. Open this paper now bypasses the current reminder. Stop showing this reminder revokes the intervention. I am changing tonight’s plan changes the goal. The channel should carry out the decision she made without silently doing the other two.

The override must be easy at the point of intervention. It should not require navigating to settings, justifying an exception or paying a larger cost each time. A rule whose ordinary bypass becomes progressively harder is escalating through its interface, even if its stored description still says “reminder”.

Repetition prompts reconsideration, not escalation

Several overrides may make the rule worth revisiting. They do not establish why Priya overrode it or what intervention she now wants.

If relevant, legitimately retained evidence supports a question, the channel can ask at a suitable moment: Keep this reminder, change it, or remove it? The question should be rare, dismissible and separate from the immediate override. She must be able to proceed without first reviewing the contract.

Repeated override does not authorise a stronger delay or a block. Nor should the learner quietly move towards such a rule while treating her exceptions as evidence of a personal defect. Chapter 24’s boundary applies here: behaviour produced under an intervention carries that provenance. It is evidence about those interactions, not an independent vote for more control.

If Priya declines a proposed revision, the revision does not happen. Lowering a confidence score while continuing to learn towards the same rejected restriction would preserve the proposal through a hidden route. A later change requires a new explicit decision. Silence and repetition supply neither acceptance nor revocation.

Expiry is part of the permission

The reminder in the worked contract ends when Priya finishes the paper or closes the study session. Finishing the session does not require her to disprove the goal or persuade the system that she has done enough.

A different rule might end with a review, an incident or a stated time. Its boundary should be visible when it is accepted and when it is used. A goal that remains unfinished is not, by itself, permission to extend an expired intervention.

Expiry ends the rule’s current authority. It need not erase the historical record of what Priya asked for, and it does not establish that she no longer wants the outcome. If she wants support next time, that support needs an applicable standing rule or a new scoped request.

Ending the intervention must also end its unapproved effects on future policy. An expired reminder cannot survive as a more restrictive default, a diagnosis assembled from overrides or a silently renewed contract. The channel may retain only what has a separate, legitimate reason to persist.

An overlay can activate a rule

A declared mode can identify when an existing rule applies. Suppose Priya accepts: During deep-study sessions, remind me before I leave the current paper. Entering a deep-study session activates that rule. The session overlay can place the reminder appropriately in the current view.

The mode does not create the permission. Without that standing rule, selecting deep study would not authorise the same reminder, still less a block. A visible task inference that she appears to be studying supplies no missing goal or intervention either.

Priya may separately ask for unrelated recommendations to stay out of the reading view until the current paper is finished or the study session ends, while direct access remains available in the sidecar. That is another authorised effect. It cannot be inferred from the reminder contract, extended to other services, or strengthened because the system wants her to finish.

The sequence is therefore:

user-supplied goal
+ authorised intervention
+ matching current scope
          ↓
temporary friction
          ↓
override or expiry

An overlay applies these inputs. It cannot invent an objective, broaden the target action or upgrade the intervention.

When her instructions conflict

Priya can ask for new recommendations to stay out of the reading view until she finishes the current paper, and also ask for every new consensus recommendation to appear there immediately. If no explicit priority settles the conflict, the channel should expose it: You asked to hold new recommendations and to show this one immediately. It can offer the choice without deciding which wish represents her true interests.

Scope can also be uncertain. A related paper may be part of the task rather than a diversion from it. The reminder contract in this chapter names opening another paper, so Priya can recognise its effect and override it. A rule that depends on classifying an item as “distracting” needs a clear, accepted scope; a label invented by the system cannot expand what she authorised.

These cases separate permission from success. An authorised reminder may fail to help. An unrequested restriction may keep Priya on the first paper, yet still exceed its authority. Neither the completion of a task nor the absence of an override proves that the intervention was wanted.

The examples establish no measured benefit, including any effect on wellbeing. They make the proposed boundary inspectable: did the channel apply only the intervention she accepted, preserve the available choice, and end the rule when its scope ended?

Beyond this reading tool

Chapter 24 made communication fit the present without turning a temporary condition into a personal property. Here, a user-authored rule can make the immediate choice less effortless without turning support into control. The goal, intervention, scope, override and expiry remain hers.

That works within one reading tool. Priya’s evening also includes news, video and messages. She may want the same declared boundary to apply elsewhere, but the reminder contract does not automatically acquire authority over those services. Each may offer different controls, and carrying the history of her overrides into all of them would expose more than the rule requires.

The next question is what may travel: how can a boundary Priya has declared be applied in another service without exporting the history that produced it, changing its meaning or pretending to enforce more than the service can support?