Week 11: Risk Disclosure: Stop-Losses and the Black Swan Protocol

Setting a stop-loss before you need one, and what a black swan event does to a position that never set one

3 May 2027

A stop-loss is a condition, named in advance, under which a party exits a position regardless of how attached they’ve become by the time the condition triggers. Naming it in advance matters because dependency (week 4) actively degrades a party’s ability to name it in the moment — the balance sheet that makes leaving costly is the same one that makes leaving hard to evaluate clearly once the moment arrives. A stop-loss set before entanglement is a promise to a version of yourself who could still see clearly, made to a version who might not be able to later.

A black swan is different: not a threshold crossed, but an event outside the model’s assumptions entirely — the kind of thing no stop-loss was written to cover because nobody thought to write it. The Black Swan Protocol is not a prediction method; it’s a standing procedure (who you talk to, what you check, what you don’t decide alone) for the position to fall back on when the model runs out of coverage.

Outline#

• stop-losses as pre-commitments, and why they have to be set before, not during, entanglement
• the Black Swan Protocol: a fallback procedure for events the model didn’t anticipate, not a prediction method
• auditing your own case for an unset stop-loss
• reading for next week: pulling every variable together for the course retrospective