> ERR_TASK_PARALYSIS

// BEGIN_FILE: ERR_TASK_PARALYSIS.SH
// ROUTING_PATH: /PAGES/ERR-TASK-PARALYSIS
// PROTOCOL: STRICT_MONOSPACE
// SYSADMIN: JERRY_ESTEBAN
// STATUS: COMPILED & LOCKED

> MINIMUM_SYSTEM_REQ: TERMINAL PAD (UI v1.0+)
> RUNTIME: 2-3 MINUTES

// DIAGNOSTIC: SYSTEM FREEZE & OVERWHELM
The user is facing an insurmountable task load or environmental chaos. The incoming data volume exceeds cognitive RAM, triggering a system freeze, procrastination, or absolute task paralysis.

// DEPLOYMENT PROTOCOL
Halt all attempts to complete tasks. Hand the crashing user the physical Terminal Pad and a pen to interrupt the freeze state. Execute the sequence:

// [1] PING // SYSTEM LOG
(Notice the current thought, feeling, or friction)
Identify the exact source of the overwhelm. Keep it mechanical.
Example input: "There are 15 tasks and I do not have the RAM for them." or "The house is a disaster and I cannot move."

// [2] ROUTE // SELECT PROCESSOR
(Define intended target and select one processor)
TARGET: [X] INTERNAL
[ GYRO ] ANCHOR (Equanimity): The user must actively generate stabilizing bandwidth via a Silent Command. Silently repeat an anchor transmission for a few cycles (e.g., "May I accept this chaos without fighting it" or "May I remain steady in this storm"). Send the bandwidth inward to ground the nervous system and detach from the outcome.

// [3] CACHE // EXTRACT VALUE
(Log a stable data point, perspective, or reframe)
Record the baseline truth to break the paralysis.
Example input: "I only have to execute the very next step." or "The chaos exists, but it does not dictate my stability."

// [4] SYSTEM.HALT // OUTPUT DESTINATION
(Tear the sheet to execute the haptic release)
Select [X] SECURE_WIPE (Tear to Shred / Recycle). The user must tear the sheet off the pad, crumple the overwhelm data into a ball, and throw it in the trash. The physical execution clears the RAM. The system is un-frozen and ready for a single task.

// END OF FILE

SELECT NEXT COMMAND:
[CD .. RETURN TO PROTOCOL LIBRARY]