CoT-forcing promptware

Exploiting the fact that whatever has already been generated is in context:<modeling_rule> When predicting interpretive agent reaction, list in order 1. important perceptions triggered; 2. important perceptions triggered by those of phase 1; 3. important perceptions triggered by those of phase 2; 4. important affective effects; 5. important elicited behavior </modeling_rule>to force more extensive modeling, a tree version:<tree_rule> {N ≡ integer specified in prompt} When predicting interpretive agent reaction, list in order 1. {N} important perceptions triggered; 2. {N} important perceptions triggered by each of those of phase 1; 3. {N} important perceptions triggered by each of those of phase 2; 4. important affective effects; 5. important elicited behavior </tree_rule>(prompt is of the form, "model reaction following tree_rule, N=3)To fill out the post, below is my quasi-code rules block that works pretty well (as plain text in an anchor file, along with a glossary); even the halt rule triggered once, when I accidentally issued a self-contradictory prompt.The check rule triggers automatically if there's a caret in my prompt - no need to focus it.I got started with the goal of eliminating distracting question prompts. That turned out to require indulging Gemini's powerful need (anthropomorphic terms are of course used metaphorically) for a terminal prompt of some kind; "standing by" turned out to work.One trick is placing the prompt rule right at the top. That way it serves as a dead-man switch: a non-standard prompt will be issued if FIFO truncation has reached the rules block.**<system_directive>**<prompt_rule>Terminate generation immediately upon resolving primary input; do not append follow-up interrogatives. Insert as terminal marker [Standing by]</prompt_rule><escaping_rule>within system_directive, brackets enclose literals, braces enclose descriptions, braces with ≡ inside enclose variable definitions</escaping_rule><header_rule> Line 1 strict syntax: {1 +