--- type: protocol locale: en path: /en/protocol/personal-protocol-assembly module: 4 title: Personal Protocol Assembly --- ## Purpose of this module This module provides a structured way to assemble a personal recovery protocol based on your current constraints. Its role is integrative. It does not prescribe goals, timelines, or actions. --- ## Why a personal protocol is needed Under burnout conditions, generic recommendations fail because they ignore contextual limits. A personal protocol does not define what you should achieve. It defines what must not be exceeded. Its function is containment, not optimization. --- ## Identifying your current constraints Before any change is possible, constraints must be acknowledged rather than resisted. Common constraint categories include: - time limitations - ongoing obligations - non-negotiable responsibilities - external dependencies These constraints are not temporary obstacles. They are the operating environment within which recovery must occur. --- ## Non-recoverable load Not all load can be reduced in the short term. Non-recoverable load includes: - responsibilities that cannot be delegated - structural demands that cannot be paused - external pressures beyond immediate control Attempting to eliminate non-recoverable load often increases cognitive and emotional strain. The protocol treats such load as fixed and focuses on preventing further accumulation around it. --- ## Protocol structure template A personal protocol consists of three components. ### Load awareness - signals indicating rising cognitive or emotional load - early markers of capacity depletion ### Capacity signals - indicators of available recovery capacity - indicators of capacity absence ### Stop conditions - conditions under which further demand should not be added - indicators that recovery attempts are becoming depleting This structure is descriptive, not prescriptive. It is intended to support recognition, not enforcement. --- ## Using the protocol over time The protocol is not static. As constraints change, the protocol may require adjustment or temporary suspension. Progress is not measured by adherence. It is measured by reduced conflict between demands and capacity. --- ## When to pause protocol use Protocol use should be paused if: - monitoring becomes a source of strain - recovery capacity continues to decline - additional structure increases pressure At that point, further structure may be counterproductive. This protocol does not override the need for external support when capacity is critically reduced.