Part of HSP Framework Core Protocol
HSP · FROM MODEL TO APPLICATION
A consistent route for working with HSP: observe what happens, map the system route, locate what limits another choice, choose an appropriate direction for change and verify what later becomes genuinely available.
The framework describes how the system works.
The Core Protocol describes how to work with it systematically.
From model to application
HSP describes how input, meaning, prediction, learned system logic, activation, resources, capacity and choice space contribute to behavior.
The HSP Core Protocol adds one practical question:
If this is the map of the system, how do you work with it step by step?
The protocol helps you observe a current route, locate the main constraint, choose an appropriate direction for change and then verify whether something different has genuinely become available.
It is therefore not a second framework and not a new change technique. It is the canonical procedure that brings existing HSP concepts and tools together.
The complaint does not choose the method
The same visible problem can emerge from very different system routes.
Procrastination, for example, may involve uncertainty, overload, anticipated judgment, missing skill or an operating rule that makes the task extremely costly.
HSP therefore does not start with the intervention.
First the route. Then the function and constraint. Then the direction for change. Only then the method, practical step or experiment.
A useful solution does not always need to be psychological either. Sometimes information is missing, a skill is needed, load needs to decrease or the environment itself needs to change.
Scope & safety
Not every problem calls for system investigation or a behavioral experiment.
Actual danger, medical or psychological problems, severe overload or a concrete practical problem may first require another form of action or professional support.
An important protocol question is therefore:
Is this currently a question for HSP observation — or does the situation require something else first?
HSP is a coaching and observation framework. It is not a diagnosis, medical approach or clinical treatment protocol.
The HSP Core Protocol
Where useful, this is followed by: REPEAT · ROLLBACK · INTEGRATE.
The stages form a consistent reasoning route, not a rigid script. Sometimes CONDITIONS already shows that sleep, information, skill or an external boundary needs attention first. Then that is the route.
Make the question observable
Start with a concrete situation or recurring output.
Not only: “I want to be more confident.” For example: “When someone criticizes me, I immediately defend myself even though I want to remain able to listen and respond.”
What actually happens now?
What would you like to also become genuinely available?
The desired difference is not behavior that must be forced. It gives the investigation a direction.
Observe before explaining
What came in? What did you notice physically or emotionally? What did you do? What happened afterwards?
Where possible, separate signal from interpretation. Tension is an internal signal. “This is going wrong” is already meaning or prediction.
What you feel is information. Not automatic truth and not an instruction.
From event to system route
Next, map only the relevant parts of the HSP route.
Not every element has to be known immediately. Unknown is better than filling in a convincing explanation without enough information.
Behavior often has a function
Do not only ask why the output is inconvenient. Ask why the system keeps selecting this route.
What does the current output reduce, prevent, protect, obtain or preserve?
Does the route make something more predictable?
Does the route try to prevent rejection or conflict?
Does the route restore grip or distance?
Does the route protect worth or position?
Does the route reduce input, pressure or effort?
Does the route preserve room or independence?
Do not try to remove a route before understanding which system problem it currently solves.
Locate the bottleneck
Now look at the conditions that determine which output is genuinely available. Not every constraint is a belief or emotional pattern.
Is relevant or reliable information missing?
Has another response not yet been sufficiently learned?
Are energy, attention or processing resources limited?
Does the actual situation make another route difficult or unsafe?
Does old system logic continue to dominate?
Does available knowledge disappear when pressure rises?
Several factors may interact. First locate the constraint that most strongly determines current choice space.
A condition for learning, not the learning itself
New information only helps when enough safety, capacity, agency and processing room remain available to do something with it.
When protective output occupies almost the entire choice space, pushing harder into experimentation is usually not the next step. Lower load, greater actual safety, restored capacity or a different environment may need to come first.
Readiness is not an update. It is the condition in which new feedback may become usable.
Direction before method
Now determine what genuinely needs to become different for more choice space to become possible.
This may involve better information, greater skill, more capacity, more latency, a clearer boundary, uncertainty tolerance, a better calibrated prediction, a less rigid rule or a different environment.
The complaint does not choose the method. The primary constraint points toward the direction for change.
The direction therefore describes what needs to become differently available. The next step only then decides how useful new information might be created.
Minimum sufficient intervention
Choose the least complex route that can genuinely address the primary bottleneck.
That may be practical action, better information, skill development, capacity recovery, a boundary, a conversation, coaching, another method or a small behavioral experiment.
Use the smallest intervention that sufficiently addresses the actual problem.
When experimentation is appropriate, the goal is not perfect performance. The goal is to create a meaningful difference from which the system can receive useful new information.
New experience ≠ automatic update
What did you do? What did the environment do? What consequences were observable?
Was the feedback integrated, discounted, treated as an exception or reinterpreted through the old prediction?
An experience can contain objectively new information while the system still does not use that information to change the old route.
Feedback is new input. Not an automatic update.
The test of change
The strongest question is not whether an exercise felt good or worked once.
Does sufficiently similar input later produce a different range of genuinely available output?
Look for example at activation, latency, operational choice space, available responses, effort required, recovery and the ability to process new feedback.
One different response mainly shows that the response was possible under those conditions.
From practice situation to operating range
Repeat where useful and vary context, person, time and manageable load. This shows whether the newer route is becoming more broadly available.
If the older route returns, investigate which condition changed and where the current operating range of the newer route ends.
What still matters? What is now independently available? And when output had impact: what responsibility or repair is required?
Rollback is not automatic evidence that nothing changed. It may reveal the level of load under which the newer route is not yet reliably available.
Five useful outputs
An HSP analysis does not need to explain everything about a person. One protocol cycle is useful when five things have become clearer:
Which system route is currently running?
What does that route solve or protect?
What most limits another route?
What needs to become differently available?
What would later count as evidence that something genuinely changed?
The aim is not the perfect explanation. The aim is to understand enough to identify the right next question, condition or direction for change.
The same logic, different depth
The core route remains the same in self-use and guided work.
For self-use, the protocol can stay simple: observe what happened, roughly map the route, locate the primary constraint and choose one appropriate next step.
A coach or other professional can work more deeply with hypotheses, safety, constraints, route selection, feedback processing and verification.
Neither approach requires every box in the model to be fully completed.
THE CORE
Observe the current route.
Understand what it solves.
Find what limits another route.
Choose the smallest appropriate direction for change.
Use feedback as new information.
And call it change only when something different later proves genuinely available.
The HSP Core Protocol organizes the existing HSP architecture into one repeatable procedure. The deeper explanations remain where they already belong: in the Framework, tools and existing articles.