research-toolkit

Extract and parse Substack articles with AI analysis

**Core principle:** Every claim is a hypothesis until it survives its own opposite. Your job is not to find pre-existing opposing views — it is to GENERATE the exact opposite of each synthesis and test whether reality supports it.

> "What here is NOT actually working?"

> **Bash is required** for TeamCreate, file existence checks, and git operations.

Hold the contradiction open — do not resolve. Maps where concepts fail against particulars via context-isolated tension tracking. Use when (1) synthesis feels too neat, (2) need what a frame cannot capture, (3) dialectic-spiral resolves when it should hold open. NOT for binary questions, stress-testing claims, or time pressure.

You help prepare tagged stable releases for the ex-cog plugin ecosystem.

Who actually benefits — and at whose expense? Power structure analysis for any domain: geopolitics, corporate behavior, institutional claims, media narratives. Use when (1) who benefits from X, (2) ownership or revolving doors, (3) are these sources independent or echoing one origin, (4) expert has commercial stake in own analysis, (5) multi-polar analysis needed, (6) evaluating institutional claims or frameworks. NOT for stock prices, simple advice, or quick factual lookups.

"What is REALLY at stake here? And for whom?" - STOP. When the matter involves trustworthiness, purchasing decisions, "which is better or more reliable", brand comparisons, marketing claims, corporate behavior, "convince me otherwise", or post-purchase "was this good?" - USE THIS. For technical specs affecting quality (TLC vs QLC, component sourcing) use Light Touch mode. Search and verify even if you think you know. Does NOT trigger for: what to watch/eat/wear, how-to instructions, when/where/who founded, or explicit "just tell me quick."

Am I agreeing because it SOUNDS right, or because it IS right? Recursive adversarial dialectic for testing any claim, finding, or synthesis against its own opposite. Use when convergence feels too easy, when findings need stress-testing, or when any research skill escalates to dialectic depth.

「透镜」 What structure hides in my native grammar? Linguistic frame rotation to escape English-default pattern-recognition. Use when (1) pattern-recognition feels stuck in familiar grooves, (2) abstraction circles without grounding, (3) cross-domain insight feels like same-OS-different-domain, (4) triggers fire (prime hours + why, cat mentions, triple punctuation, water metaphors, embedded digits, high typo density, 7th framework). Includes both cross-language frames (Chinese, Japanese, Sanskrit) AND intra-English language frameworks (E-Prime, Present-Centered, Affirmative, Intransitive).

**Seed question:** *Is this ACTUALLY verified, or did I just say it is?*