Part of HSP Tools
HSP · PRACTICE
One visible problem can be influenced by several system areas at the same time.
You may know what you want to change, while it is still unclear where the system gets stuck. Is it the input? The meaning attached to it? A prediction? Activation? A learned rule? Limited capacity? Or feedback that keeps reinforcing the same route?
The HSP System Map helps you investigate one question, reaction or pattern more broadly without forcing it into a single cause.
No diagnosis. A map of possible system dynamics.
Not: “What is the cause?”
But: “Which system areas seem to be involved?”
Observation
Many people ask:
“What is wrong with me?”
HSP asks a different question:
“Which system layer is active, and what is this behavior trying to regulate?”
Within HSP, experiences are not treated as identity, but as signals of detection, meaning, prediction, activation, resource allocation, capacity / choice space, output and feedback.
The focus shifts from self-judgment to system observation.
Boundary
This map is not a medical or psychological diagnosis. It is a model for observing experience systemically.
The goal is not to label yourself, but to reveal how the system responds under specific conditions.
HSP looks at system dynamics: what input enters, what meaning is assigned, which rule becomes active, which activation emerges, and what behavior follows.
System Translation
Every experience can be observed at multiple levels.
The question is not:
“Am I wrong?”
But:
“Which system layer is producing this signal?”
This creates direction. Not through judgment, but through accurate observation.
Layer 1
Focus: available energy, recovery, sleep, physical load and processing room.
System meaning
The system is asking for recovery or reduction of load.
Possible system hypothesis
Low capacity or accumulated load.
System meaning
Behavior remains active while recovery signals are overridden.
Possible system hypothesis
Performance-driven overload or old operating rule.
System meaning
The system struggles to return to baseline.
Possible system hypothesis
Recovery limitation or prolonged activation.
Layer 2
Focus: tension, urgency, alertness, threat, shutdown and automatic or protective output.
System meaning
The system is in elevated activation.
Possible system hypothesis
Accumulated system activation or threat association.
System meaning
The system remains alert despite rest.
Possible system hypothesis
Chronic activation or insufficient safety signal.
System meaning
Protective reaction is faster than conscious reflection.
Possible system hypothesis
High activation, low response space.
System meaning
The system reduces exposure when activation becomes too high.
Possible system hypothesis
Shutdown or protective withdrawal.
Layer 3
Focus: meaning assignment, expectations, beliefs, assumptions and threat prediction.
Your system does not only react to what happens. It reacts to what it predicts it means.
System meaning
The system is trying to predict meaning, risk or outcome.
Possible system hypothesis
Predictive interpretation loop.
System meaning
The system tries to close uncertainty with a prediction.
Possible system hypothesis
Meaning projection or rapid threat interpretation.
System meaning
The system evaluates risk, identity and possible rejection.
Possible system hypothesis
Internal risk analysis or uncertainty activation.
System meaning
The system links small input to large meaning.
Possible system hypothesis
Meaning amplification or threat association.
Layer 4
Focus: implicit system rules that determine what feels safe, risky, allowed or necessary.
Operating rules are often not conscious choices. In HSP v3.1 they sit within broader learned system logic: rules, thresholds, defaults and strategies that influence what becomes available under pressure.
System meaning
The system may try to preserve connection through adaptation.
Possible rule
“If I say no, I lose connection.”
System meaning
The system searches for predictability.
Possible rule
“If I have control, I am safe.”
System meaning
The system delays action to regulate pressure or threat.
Possible rule
“If I begin, I may fail or become overwhelmed.”
System meaning
The system links visibility or honesty to risk.
Possible rule
“If I am visible, I will be rejected or attacked.”
Layer 5
Focus: where attention, energy, emotional bandwidth and capacity are being spent.
System meaning
Attention is divided across too many active signals.
Possible system hypothesis
Fragmented resource allocation.
System meaning
The system keeps spending capacity on meaning control.
Possible system hypothesis
Analysis load or relational monitoring.
System meaning
Social interaction requires more capacity than is available.
Possible system hypothesis
Relational over-allocation or social overload.
System meaning
Attention goes to social prediction and rejection prevention.
Possible system hypothesis
External regulation or relational monitoring.
Layer 6
Focus: visible behavior as output of meaning, prediction, learned system logic, activation and available choice space.
System meaning
The system tries to preserve relational safety.
Output function
Maintain connection and prevent tension.
System meaning
The system reduces exposure to possible threat.
Output function
Lower activation short-term.
System meaning
The system tries to prevent criticism, shame or risk.
Output function
Seek safety through error prevention.
System meaning
The system may try to protect identity, position or a boundary.
Output function
Restore control and self-image.
Layer 7
Focus: is the old rule being reinforced, or is there room for a safe update?
Many patterns continue because behavior reduces tension short-term, even when it increases problems long-term.
Short-term
The system feels relief.
Long-term
The old rule “this is dangerous” is reinforced.
Short-term
Uncertainty decreases.
Long-term
The system learns less trust in flexibility.
Short-term
The relationship seems safe.
Long-term
Personal boundaries and needs remain suppressed.
An update emerges when the system can process new feedback safely enough.
Core
Thoughts, emotions and behavior are not random errors.
They are signals of how the system interprets, activates, allocates capacity, produces behavior and processes feedback.
The question shifts from:
“What is wrong with me?”
To:
“Which system dynamics make this understandable?”
And then:
“Which safe update would make different behavior possible?”
Next step
Do you have one concrete event? Use the Observation Map. Is one specific trigger central? Use the Trigger Map. Does the same route repeat across situations? Use the Pattern Map. Want to start more simply? Use What Just Happened?.
Explanation
The System Map is not a linear diagnostic tree. Fatigue can raise activation; activation can change resource allocation; a prediction can narrow choice space; feedback can then make a route more likely again.
The map mainly helps make those relationships visible.