> For the complete documentation index, see [llms.txt](https://sudoku.kazusa.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sudoku.kazusa.tech/exocet/11-exocet-with-domino-loop/03-conjugate-quadruple-node.md).
# 共轭四元节点（CQN）
前面的内容还是比较简单的，下面我们继续延续模式四数组的推论看看有没别的结论。
## 共轭四元节点的基本推理
通过前文我们可以得到的模式四数组，我们不难发现，因为四数组内部的某个数字不能出现两次及以上，所以我们可以强行构造弱链关系把他们串起来，于是我们可以构造一个抽象的链结构出来：
```
节点1(a) = PLQ其中两个格(a) - PLQ另外两个格(a) = 节点2(a)
```
如果头尾的两个节点确实都可以和这里的模式四数组的某个数字 $$a$$ 串起来，那么我们不难得到此链路。同时，链可以被简化为两个节点之间的强链：`节点1(a) = 节点2(a)`。
我们把这四个节点 `节点1(a)`、`PLQ其中两个格(a)`、`PLQ另外两个格(a)` 和 `节点2(a)` 称为一组**共轭四元节点**（Conjugate Quadruple Node，简称 CQN）。
> 这个术语表示的是一组四个节点，所以四个节点整体一个单位，用单数形式。
## 实际用例
如图所示。我们用一下链。这里我们构造出这样一条不连续环：
```
2r1c8=2r56c8-2r45c2=2r9c2-(2=6)r8c1-6r8c9=68r7c9|r9c7-5r9c7=5r79c8 => r1c8 <> 5
```
其中 `2r1c8=2r56c8-2r45c2=2r9c2` 强弱关系的得到，就是利用的共轭四元节点。后面的 `6r8c9=68r7c9|r9c7` 来自于 `b9` 里数字 6 和 8 的毛刺隐性数对。
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://sudoku.kazusa.tech/exocet/11-exocet-with-domino-loop/03-conjugate-quadruple-node.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.