ljg-constraint
Identify the defining constraints that genuinely bound a domain, profession, role, product, or debate; categorize them into world/rule/interpretation (hard/soft/self-imposed); and examine how this set of constraints defines identity, completes the problem statement, delineates the solution space, and explains observed real-world behaviors. Especially useful for distinguishing strategic disagreements where goals are identical but default constraints differ, and for identifying outdated interpretations mistaken for hard facts. USE WHEN the user says 'constraint', 'find constraints', 'what are the constraints of this domain', 'essential constraint', 'what bounds it', 'hard constraint or self-imposed constraint', 'where is the boundary', 'why does this industry do this', 'constraint', '/ljg-constraint', or provides any domain/profession/role/product/debate wanting its defining constraints and solution space mapped. NOT FOR drilling down into generative mechanisms (use ljg-rank to find generative power rather than boundaries), drilling deep vertically into an argument (use ljg-think), breaking down a book (use ljg-book), or dissecting a concept (use ljg-learn).
1How It Works & Mechanism
Constraints are not negative shackles; they are the system of equations that collapses infinite possibilities into 'this specific one'. The goal and the constraints together constitute the full problem statement.
约束不是在减少可能性，是从无穷里生出特定性。
Three levels of hardness: hard constraints (world/physical level, violating causes system collapse), soft constraints (rule level, violating incurs costs), and self-imposed constraints (interpretation/cognitive level, can be redefined).
**硬约束（世界层 / 物理层）**——不可违背，试图违背则系统崩溃。
Execute the seven-step process (list candidates / layer and position / determine authenticity / identify constraint mismatches / identify contradictory pairs / identify identity constraints / synthesize via two lenses) mentally only; do not write it into the final article.
工序心里走完，别写进文章——读者看不到你怎么摸的边，但感觉得到底下是摸到实处的。
Anchor conclusion in explanatory power: Rational, optimal behavior within the solution space should align precisely with what the role repeatedly does in reality for the constraints to be considered accurately identified.
**解释实际操作。** 这是收口，也是这引擎最值钱的地方：解空间里那个理性的最优行为，应该正好就是这个角色在现实里反复做的那些事。
The first gate and primary criterion of the post-check: Explanatory power—whether the rational, optimal behavior in the solution space matches observed real-world practice.
1. **解释力（主判据）**——解空间里的理性最优行为，对不对得上现实中观察到的实际操作？
'How to improve' is secondary and does not participate in diagnosis: append only one or two sentences on potential leverage points after the diagnosis is complete, without retroactively altering the diagnostic findings.
**急着找出口，就会看不清墙**——这是这引擎最容易犯的病，务必压住。
Native Chinese anti-collapse gate: silently ask before writing, 'Would a native speaker who has never read English phrase it this way?', and rewrite the entire paragraph if translationese or anglicisms are detected.
**「一个没读过英文的中国人，会这么说话吗？」**
Append an ASCII structural diagram at the end, shaped by the analytical framework; strictly prohibit all Unicode symbols (arrows, boxes, bullets, etc.) in the hard constraint layer.
**硬约束：只用纯 ASCII 字符。** 禁用任何 Unicode 符号（箭头 → ← ↑ ↓、方框 ┌─┐└┘│、圆点 • ● 等）。
Output workflow: Obtain timestamp, write to ~/Documents/notes/{timestamp}--{domain}的约束__constraint.org with frontmatter following references/template.org, and report the path.
写入 `~/Documents/notes/{时间戳}--{领域}的约束__constraint.org`，frontmatter 见 `references/template.org`
Gotchas baseline: Never write constraints as ordinary difficulties, flaws, or advice; a constraint must alter the solution space such that removing it changes permissible behaviors.
不要把约束写成普通困难、缺点或建议。约束必须能改变解空间；拿掉它，允许的行为会变。
2Core Capabilities
4Recommended Governance & Evidence
- 本地工作目录: File I/O and artifact output: Writes to `~/Documents/notes/{timestamp}--{domain}的约束__constraint.org` per SKILL.md output section (handled by host/agent).
5Second-Pass Verification
- [ok] 文件构成 — §1 清单仅 SKILL.md 与 references/template.org，无脚本、无资产、无端点。
- [ok] 三层硬度与工序连贯 — 硬/软/自设三层定义与七步工序、心内判据互相一致，解释力被反复点为主判据。
- [ok] 描述优先于改造 — 「松动哪条（第二位，不参与诊断）」与 Gotchas「不要急着写如何突破约束」一致。
- [ok] ASCII 图约束 — 文末结构图规定硬约束层禁用 Unicode 符号，并给出三种可选形态。
- [ok] 风险扫描复核 — §3 七类（URL/凭证/执行/写盘/网络/危险旗标/沙箱）均 0 命中。
- [ok] 判级口径 — 纯指令 + 一处本地写入（org 笔记）→ 按范式落 blue，非 green。
6Verdict & Scenarios
f61adce608c1df97…