Poko Resources
How The Poko Function Loop Works
The Poko function loop moves Thinking to Development to Behaviour to Performance to Regulation to Recovery, then back to Thinking. The order matters because real-life function is cyclical, not a straight line.
The loop starts with Thinking
The first question is how the person's cognitive system is processing the world. What is taking attention? What has to be remembered? What is unclear? What decision load is active? Starting here keeps Poko practical because it begins with the operating problem before jumping to labels, advice or personality stories.
Development explains fit and pattern
Development comes next because thinking happens inside a particular system. Neurodevelopmental patterns, learning history, cognitive style, sensory fit and support needs all shape what the person can access. This layer stops support from assuming every person should function in the same environment, at the same pace, with the same kind of cue.
Behaviour shows what the system does
Behaviour is the repeated move under those conditions. It might be avoidance, rushing, overchecking, freezing, masking, restarting, people-pleasing or disappearing. Poko treats behaviour as information about the loop. What did the system do because of the thinking load and fit conditions it was under?
Performance tests the system under demand
Performance asks what happens when something has to work in real life. Can the person start, continue, decide, communicate, finish, recover and return when the week has pressure and stakes? This is where good intentions meet actual conditions. It is also where cost matters: not just whether the thing happened, but what it took.
Regulation and Recovery keep the loop usable
Regulation keeps action available while the system is under stress, emotion, arousal or overload. Recovery restores capacity so the next cycle can begin. Without regulation, demand pushes the system out of usable range. Without recovery, the next Thinking pass starts with less room. That is why the wheel returns to Thinking rather than ending at output.
How to use this
- Run one hard moment through the loop in order: Thinking, Development, Behaviour, Performance, Regulation, Recovery.
- Notice which layer you usually skip.
- Choose one support move at the layer where the loop actually tightened.