Part of Human System Protocol™
HUMAN SYSTEM PROTOCOL™ — THE MODEL
Behavior does not arise in one step. HSP makes visible how input, prediction, learned system logic, activation, capacity and choice space influence which output becomes available.
This page is the canonical reference for the current HSP model, its core terminology and the boundaries of what HSP is and is not.
Canonical reference
This page describes the current Human System Protocol™ model: how input can move through predictive interpretation, learned system logic, activation, resource allocation and choice space into behavior / output and feedback.
Use this page as the reference for the meaning of the main HSP terms. Other articles may apply or simplify parts of the model, but this page defines the current model language.
Behavior is output, not identity. The question is not only what someone does, but which system route became available under these conditions.
Want to begin with recognizable human experience first? Start with your question →
From human experience to system dynamics
People usually do not arrive with system language. They say: “I keep overthinking”, “I feel stuck” or “I keep doing something different from what I want.”
The HSP Translation Layer translates these experiences into possible system dynamics: what was detected, what meaning and prediction emerged, which learned system logic became active, how activation and capacity changed, how much choice space remained and which output became available.
Not to excuse behavior or label people, but to make the route observable.
The current HSP model
HSP does not describe a fixed chain in which every step is always conscious or linear. The model makes visible which system layers together influence which output becomes available at a given moment.
Predictive interpretation contains three parts: detection → meaning → prediction. What does the system notice, what does that mean based on earlier experience, and what does it expect may happen next?
Operating rules remain useful HSP language. They sit within the broader idea of learned system logic: inner rules, thresholds, default routes and strategies that influence what feels safe, risky or necessary.
Activation changes system state. Resource allocation determines where attention, energy and processing capacity go. Together they influence how much capacity and choice space remains available.
Behavior / output is what becomes visible or noticeable. The output function asks what that output does in the system. When choice space is small, the function is often protective. With more choice space, output can also be conscious, relational, practical or value-based. Protection is therefore not a mandatory separate system layer.
Feedback is what happens after output. That feedback can confirm an existing route or, under sufficiently safe conditions, contribute to a system update.
What does the system notice, what does it mean, and what does it expect may happen?
Which rule, threshold, default route or strategy influences what becomes available?
How does system state change and how much urgency appears?
Where do attention, energy and processing capacity go?
How much access remains to pause, regulate, reflect and choose consciously?
What becomes visible, what function does it have, and what does the system learn afterwards?
Canonical terms
This short glossary defines how the core terms are used across this site. Articles may highlight only part of this language, but they do not change its meaning.
Internal or external signals and conditions that reach or influence the system: environment, words, body state, memories, thoughts, expectations and more.
The combination of detection, meaning and prediction: what the system notices, what it makes that mean and what it expects may happen next.
Learned rules, thresholds, default routes and strategies that influence what becomes available under particular conditions.
The shift in system state when something is predicted to be relevant, urgent, safe or threatening.
Where attention, energy and processing capacity go at that moment.
How much access remains to regulation, processing, perspective, pausing and conscious choice.
What the system produces and what becomes visible or noticeable: acting, speaking, avoiding, pleasing, shutting down, pausing or choosing consciously.
What the output does in the system. When choice space is small, that function is often protective, but output is not protective by definition.
What happens after output and what the system takes from it. Feedback can reinforce a route, weaken it or add new information.
A change in prediction or learned system logic that becomes possible through sufficient safety, capacity, new experience and feedback.
Getting stuck
Getting stuck often does not mean someone does not want to change. It means that under particular conditions an old prediction and learned route still become more available than a new one.
A system may return to control, avoidance, people pleasing, overthinking, perfectionism or shutdown because that output once regulated something, prevented something or created short-term relief.
The output may now be limiting, but it can remain available while the underlying prediction, learned system logic or feedback loop has not sufficiently updated.
A pattern becomes easier to understand when you ask not only what did I do?, but also what did my system predict, how much choice space was available, and what function did the output have?
Safe system update
HSP is not only about understanding behavior. Change becomes more possible when the system can process new experience and feedback under sufficiently safe conditions.
A system update cannot be reliably forced from high activation and very small choice space. Regulation, distance, support, recovery or more capacity may need to come first before experimentation becomes useful.
A different experience is not automatically an update. The system has to register the experience as relevant and safe enough for an existing prediction or learned route to be revised.
Under renewed load, an older route may become available again. That does not automatically mean earlier change has disappeared; it shows which route had the most access under those system conditions.
Practical rule: sufficient safety and capacity first, then experiment. Do not force an experiment to produce proof of change.
View system update readiness → View safe behavioral experiments →
Framework boundaries
HSP is a systems-based coaching framework for observing and understanding behavior, recurring patterns and change.
HSP does not try to place people into fixed categories. It does not first ask, “What type are you?” but, “Which system conditions are influencing what becomes available right now?”
HSP describes system dynamics, not identity. Understanding why behavior became available does not remove responsibility for its impact.
HSP can support coaching, but it does not replace medical or psychological care when that is needed and it does not claim to be clinically validated.
Observation
The HSP System Scan uses the terms on this page to explore which system dynamics may currently have the strongest influence.
The scan generates hypotheses, not diagnoses. It helps observe where prediction, learned system logic, activation, resource allocation, capacity, choice space or output function may need attention.
How strongly or quickly does system state shift?
How much access remains to pause, regulate, reflect and choose consciously?
Which output keeps returning and what does that output do in the current system route?
Use the scan as an observation tool and a starting point for inquiry, not as a label or conclusion about who someone is.
Reading route
This page is the canonical model reference. If you would rather learn HSP from recognition and in smaller steps, use the HSP in Plain Language reading route.
That route starts with human experience and then builds toward system logic, core principles, constraints and safe updates.