ljg-structure
Identify motif-level structures within information, expand abstract relationships back into concrete, visible phenomena, and use wind tunnel testing to examine critical causalities and boundaries. USE WHEN user says '找结构', '母题是什么', '结构风洞', '背后的结构', '不要只做AB测试', or wants the generative mechanism beneath a problem. Only expand into cross-domain sources or multi-motif combinations when explicitly requested by the user. NOT FOR standard summaries, single analogies, fact retrieval, or execution tasks with an already clear, unique solution.
1How It Works & Mechanism
Strictly distinguish four concepts: theme is a name, motif is a dilemma, analogy is a clue, and structure is a causal machine.
一句话：主题是名字，母题是难题，类比是线索，结构是因果机器。
Workflow Routing directs to the single workflow FindStructure, which extracts motifs, structural relationships, and wind tunnel experiments from the information.
| **FindStructure** | 从信息中找母题、结构关系与风洞实验 | `Workflows/FindStructure.md` |
Step 0/1: Perform a sufficiency check and compress the input, retaining at least one observable anchor (someone's action, a system change, or a moment when a judgment fails).
保留至少一个可观察的锚点：某个人做了什么、系统出现了什么变化、判断在哪一刻失效。
Step 2 Find Motif: Strip names, industries, and specific materials from the original scenario, framing it into a concrete question using plain language following the template: 'Under {critical constraint}, how does the system handle the relationship or tension between {A} and {B}?'.
在 `{关键约束}` 下，系统如何处理 `{A}` 与 `{B}` 的关系或张力？
Motifs must pass two gates: cross-domain replacement (still holds when roles and materials are replaced) and reverse explanation to the original problem (still explains the bottleneck when put back into the original scenario).
**跨域替换**：换掉角色和材料，问题仍成立；
Step 3: Internal cross-domain search for similar mechanisms to calibrate structure, treating sources only as scaffolding and omitting them by default in the output.
来源只是脚手架：默认不输出来源目录；确有助于理解时，用一句话带一个最贴切的例子。
Step 4: Determine the relationship across multiple structures (series/parallel/nested/checks-and-balances/feedback) before drawing a minimal relationship diagram using only ASCII characters; Unicode arrows and box-drawing characters are forbidden.
连接线、箭头和方框只用 ASCII 字符，不用 `→`、`┌`、`─` 等 Unicode 图形字符。
Step 5: The wind tunnel is an internal evaluation step, not output as a visible section: establish baseline prediction -> modify one key condition -> find boundaries and reversal signals.
风洞是内部判别步骤，不作为可见章节输出。
Output constraints: Approximately 800-1500 Chinese characters, Level 1 headings strictly limited to Input / Motif / Structure / Conclusion, file in org format with Markdown forbidden.
一级标题严格只有：`输入`、`母题`、`结构`、`结论`。
Persisting to disk: Default writes to ~/Context/{timestamp}--结构-{theme}__structure.org; do not create a file when the user specifies 'analysis only', 'do not write to disk', or read-only mode.
若用户明确说「只分析」「不落盘」或 `read-only`，直接在对话中给出同等完整的分析，不创建文件。
2Core Capabilities
4Recommended Governance & Evidence
- scripts/: Executes local scripts or commands: date +%Y%m%dT%H%M%S and date "+%Y-%m-%d %a %H:%M" (fetching timestamps for filenames and #+identifier)
- 本地工作目录: File read/write and artifact output: ~/Context/{timestamp}--结构-{theme}__structure.org (org structural analysis notes, optional: skipped when user specifies analysis-only/read-only)
5Second-Pass Verification
- [ok] 四概念区分 — 『一句话：主题是名字，母题是难题，类比是线索，结构是因果机器。』原文在。
- [ok] 工作流路由 — Workflow Routing 表指向 Workflows/FindStructure.md，§1 清单确有该文件。
- [ok] 可观察锚点 — 『保留至少一个可观察的锚点…』原文在。
- [ok] 母题句式与两道闸 — 『在 `{关键约束}` 下，系统如何处理 `{A}` 与 `{B}` 的关系或张力？』与『跨域替换/解释回原题』原文在。
- [ok] 纯 ASCII 图约束 — 『连接线、箭头和方框只用 ASCII 字符，不用 `→`、`┌`、`─` 等 Unicode 图形字符。』原文在。
- [ok] 风洞不外显 — 『风洞是内部判别步骤，不作为可见章节输出。』原文在。
- [ok] 固定四标题与落盘 — 『一级标题严格只有：`输入`、`母题`、`结构`、`结论`。』与 read-only 不落盘条款原文在。
- [discrepancy] 风险扫描与内文差异 — 扫描栏『执行外部程序/写盘』报无命中，但正文含 date 命令与 org 写入；按§2 内文为准，scripts_executed/file_writes 非空。
6Verdict & Scenarios
aba796fec52f66c5…