From 54d83fe53de8a0af6bd7fc015f9e479d10553746 Mon Sep 17 00:00:00 2001 From: osmarks Date: Fri, 23 May 2025 22:59:58 +0000 Subject: [PATCH] =?UTF-8?q?Edit=20=E2=80=98vengeance=E2=80=99?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- vengeance.myco | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vengeance.myco b/vengeance.myco index 7c2b479..b7e4a68 100644 --- a/vengeance.myco +++ b/vengeance.myco @@ -23,7 +23,7 @@ Methods of vengeance may include, but are not limited to: * [[Torment nexus]] exposure. * Linearization. -== Vengeance Management Strategies +== Vengeance management strategies Vengeance is an important mechanism to disincentivize doing bad things to GTech™ employees. However, a credible threat of future vengeance, or [[acausal]] processing, is required for this function to work. This means that some form of vengeance should demonstrably occur with high probability after a bad thing is done. It's also important to correctly determine the scale of the vengeance resulting from a given act, since vengeance can beget further vengeance. The following analysis assumes that both parties are following the same vengeance scaling/strategy: in an asymmetric situation, we recommend that you consider each possible strategy yourself to maximize expected utility.