How Weekly Reset Uses The Whole Poko Model

Performance is the anchor

Weekly Reset begins with the real week because the week is where support either works or does not. What has to happen? What is active? What is likely to move? What needs protecting? That makes it a Performance service: it is about function under demand, not abstract self-improvement.

Thinking: what is taking load?

The reset asks what is taking attention, memory, decision load or planning capacity. This matters because a week can look manageable on paper while the hidden thinking load is already too high. Naming that load makes the plan more honest.

Development and Behaviour: what pattern will show up?

The reset also asks what fit pattern matters and what default behaviour is likely to take over. Maybe ambiguity creates avoidance. Maybe pressure creates overcontrol. Maybe sensory load makes ordinary admin harder. Maybe the person can start but not return after interruption. This stops the plan from pretending the same strategy works for every system.

Regulation and Recovery: what keeps it usable?

Weekly Reset does not only ask what needs to be done. It asks what keeps the system inside usable range and what stops the plan borrowing from the future. That might mean fewer open loops, a smaller version, a boundary, a protected pause, a clearer handoff or a recovery point before the week gets loud.

One loop, one week, one usable plan

The point is not to analyse the whole life. It is to run one practical loop around the next seven days. What is hard to hold? What pattern matters? What default might take over? What must work? What keeps the system usable? What restores capacity for the next cycle? That is how the model becomes a plan.

How to use this

• Choose one upcoming week and ask what must work, not what would look impressive.
• Name the default that usually takes over when pressure rises.
• Protect one recovery or regulation condition before the week spends it.