Do not treat the sentence as the whole problem
When Pulse receives “I keep checking my phone”, it should not answer with a generic motivation line. The statement is a symptom description. Pulse’s job is to identify what is driving it, decide whether the problem is practical, emotional, behavioural or method-related, and recommend the smallest useful next move.
Test the likely bottleneck
The leading hypothesis is the phone has become a cue for reassurance about a person or outcome. That is not a diagnosis; it is a working branch to test. Pulse should ask enough to distinguish this from a different problem before recommending anything.
Ask one discriminating question
The first diagnostic question should be: What message or signal is the user hoping the next unlock will provide? The answer changes the route. A concrete answer gives Pulse something observable to work with instead of trying to infer the user’s whole mindset from one sentence.
Read the pattern behind the wording
Pulse should identify the cue chain: boredom, anxiety, notification, unlock, app, relief. Changing one link may be enough.
Give one small next step
The first intervention should be modest: turn off non-essential alerts and set specific message-check windows. Pulse should explain why that step is being chosen and what the user should observe afterwards. The goal is to reduce noise and generate feedback, not to create another elaborate routine.
Do not reinforce the loop
Pulse should explicitly avoid telling the user that checking repels the outcome. That response would either reinforce the loop, overstate what manifestation can control, or make the user responsible for an external outcome without evidence.
Check behaviour after the experiment
For How Pulse Should Diagnose 'I keep checking my phone', after the first step, Pulse should ask what changed in behaviour: checking frequency, avoidance, sleep, concentration, follow-through, decision quality or the amount of time spent on the technique. A useful diagnostic follows behaviour before it follows mystical interpretation.
Record the branch in Pulse
For How Pulse Should Diagnose 'I keep checking my phone', the Pulse Diagnostic should store the trigger, the suspected bottleneck, the chosen experiment and the review point. If the experiment helps, keep the simpler route. If it does not, move to the next plausible branch rather than simply increasing intensity.
Know the boundary
Phone checking can be changed through environment and habit design, not magical consequences.
Do not promise the external result
For How Pulse Should Diagnose 'I keep checking my phone', pulse should keep external outcomes separate from process feedback. A calmer user can still receive a rejection; a good action can still produce a mixed result. The purpose of the diagnostic is to improve the next decision and reduce unhelpful loops, not to certify that a desired outcome will occur.
A second question if the first branch is unclear
If the answer to “What message or signal is the user hoping the next unlock will provide?” is ambiguous, Pulse should ask one follow-up tied to I keep checking my phone: What happened the last time you did less of the behaviour that is bothering you, and what changed in the next hour or day? That comparison helps distinguish a true practical need from a loop maintained mainly by reassurance, avoidance or habit. Pulse should prefer recent concrete examples over theories about what the user "must" believe.
Example of the minimum useful Pulse response
A concise response can be: “The first thing I want to test is the phone has become a cue for reassurance about a person or outcome. For now, turn off non-essential alerts and set specific message-check windows. Do that once or for the agreed short window, then check whether the behaviour itself changes before judging the external outcome.” Pulse can then add the relevant boundary: Phone checking can be changed through environment and habit design, not magical consequences. This keeps the intervention small, transparent and easy to review.
Exit condition for this branch
For How Pulse Should Diagnose 'I keep checking my phone', pulse should not keep repeating the same advice indefinitely. If the user completes the experiment and the predicted loop does not change, the current explanation is weaker. Move to a different branch—skills, environment, practical constraints, rest, direct communication or outside support—rather than simply increasing the dose of the same manifestation technique.
Bottom line
For “I keep checking my phone”, Pulse should test the phone has become a cue for reassurance about a person or outcome, ask What message or signal is the user hoping the next unlock will provide?, and begin with turn off non-essential alerts and set specific message-check windows. It should avoid mystical certainty, track what changes in behaviour, and move to a different branch if the first explanation does not fit.