UNHAPPY Scenario

In software language, an unhappy scenario is the route an operation takes when it leaves the expected path. The phrase places interruption inside a manageable plan: name the branch, provide recovery, return the user to continuity.

The poem composes this procedural vocabulary as found material. Upload, sending, reconnection, and reporting pass from one promised remedy to the next obstruction. The voice stays calm. Repetition makes that calmness increasingly charged, as the system continues to speak in the grammar of temporary inconvenience.

Repeated internet blackouts in Iran give this language its remembered ground. A failed connection reaches into intimate contact, access to information, work, and the possibility of reporting harm. The small vocabulary of system notices begins to carry a much larger condition: separation, suspended time, and accountability held beyond reach.

Two connected surfaces hold the interruption. The communication apparatus continues to offer procedures; the poem field receives what those procedures say. A surviving message, an active shell, its dark residues, and the accumulating lines register different durations of the same blocked passage. In the browser, the promise of return is allowed to spend itself completely.