@kensnzk/koyu 0.15.0 → 0.17.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (188) hide show
  1. package/README.ja.md +14 -10
  2. package/README.md +16 -13
  3. package/dist/cli.js +162 -84
  4. package/dist/cli.js.map +1 -1
  5. package/dist/core/derive.d.ts +264 -0
  6. package/dist/core/derive.d.ts.map +1 -0
  7. package/dist/core/derive.js +576 -0
  8. package/dist/core/derive.js.map +1 -0
  9. package/dist/{check.d.ts → core/diagnose.d.ts} +15 -15
  10. package/dist/core/diagnose.d.ts.map +1 -0
  11. package/dist/{check.js → core/diagnose.js} +269 -223
  12. package/dist/core/diagnose.js.map +1 -0
  13. package/dist/{diff.d.ts → core/diff.d.ts} +3 -2
  14. package/dist/core/diff.d.ts.map +1 -0
  15. package/dist/{diff.js → core/diff.js} +89 -43
  16. package/dist/core/diff.js.map +1 -0
  17. package/dist/{fabric.d.ts → core/fabric.d.ts} +5 -3
  18. package/dist/core/fabric.d.ts.map +1 -0
  19. package/dist/{fabric.js → core/fabric.js} +12 -11
  20. package/dist/core/fabric.js.map +1 -0
  21. package/dist/{graph.d.ts → core/graph.d.ts} +2 -4
  22. package/dist/core/graph.d.ts.map +1 -0
  23. package/dist/{graph.js → core/graph.js} +53 -54
  24. package/dist/core/graph.js.map +1 -0
  25. package/dist/core/light.d.ts +24 -0
  26. package/dist/core/light.d.ts.map +1 -0
  27. package/dist/{light.js → core/light.js} +17 -12
  28. package/dist/core/light.js.map +1 -0
  29. package/dist/{model.d.ts → core/model.d.ts} +178 -18
  30. package/dist/core/model.d.ts.map +1 -0
  31. package/dist/{model.js → core/model.js} +307 -68
  32. package/dist/core/model.js.map +1 -0
  33. package/dist/core/parse.d.ts.map +1 -0
  34. package/dist/{parse.js → core/parse.js} +546 -133
  35. package/dist/core/parse.js.map +1 -0
  36. package/dist/{poly.d.ts → core/poly.d.ts} +3 -6
  37. package/dist/core/poly.d.ts.map +1 -0
  38. package/dist/{poly.js → core/poly.js} +8 -13
  39. package/dist/core/poly.js.map +1 -0
  40. package/dist/core/site.d.ts.map +1 -0
  41. package/dist/{site.js → core/site.js} +2 -2
  42. package/dist/core/site.js.map +1 -0
  43. package/dist/core/tolerance.d.ts +26 -0
  44. package/dist/core/tolerance.d.ts.map +1 -0
  45. package/dist/core/tolerance.js +48 -0
  46. package/dist/core/tolerance.js.map +1 -0
  47. package/dist/{vertical.d.ts → core/vertical.d.ts} +48 -12
  48. package/dist/core/vertical.d.ts.map +1 -0
  49. package/dist/{vertical.js → core/vertical.js} +53 -105
  50. package/dist/core/vertical.js.map +1 -0
  51. package/dist/core/vocabulary.d.ts +40 -0
  52. package/dist/core/vocabulary.d.ts.map +1 -0
  53. package/dist/core/vocabulary.js +176 -0
  54. package/dist/core/vocabulary.js.map +1 -0
  55. package/dist/{axo.d.ts → draw/axo.d.ts} +1 -1
  56. package/dist/draw/axo.d.ts.map +1 -0
  57. package/dist/{axo.js → draw/axo.js} +53 -81
  58. package/dist/draw/axo.js.map +1 -0
  59. package/dist/draw/index.d.ts +3 -0
  60. package/dist/draw/index.d.ts.map +1 -0
  61. package/dist/draw/index.js +11 -0
  62. package/dist/draw/index.js.map +1 -0
  63. package/dist/draw/plan.d.ts +10 -0
  64. package/dist/draw/plan.d.ts.map +1 -0
  65. package/dist/draw/plan.js +284 -0
  66. package/dist/draw/plan.js.map +1 -0
  67. package/dist/index.d.ts +16 -11
  68. package/dist/index.d.ts.map +1 -1
  69. package/dist/index.js +55 -12
  70. package/dist/index.js.map +1 -1
  71. package/dist/mcp.js +112 -50
  72. package/dist/mcp.js.map +1 -1
  73. package/dist/parse-file.d.ts +1 -1
  74. package/dist/parse-file.d.ts.map +1 -1
  75. package/dist/parse-file.js +19 -4
  76. package/dist/parse-file.js.map +1 -1
  77. package/dist/validate/access.d.ts +6 -0
  78. package/dist/validate/access.d.ts.map +1 -0
  79. package/dist/validate/access.js +248 -0
  80. package/dist/validate/access.js.map +1 -0
  81. package/dist/validate/envelope.d.ts +4 -0
  82. package/dist/validate/envelope.d.ts.map +1 -0
  83. package/dist/validate/envelope.js +55 -0
  84. package/dist/validate/envelope.js.map +1 -0
  85. package/dist/validate/index.d.ts +60 -0
  86. package/dist/validate/index.d.ts.map +1 -0
  87. package/dist/validate/index.js +77 -0
  88. package/dist/validate/index.js.map +1 -0
  89. package/dist/validate/light.d.ts +6 -0
  90. package/dist/validate/light.d.ts.map +1 -0
  91. package/dist/validate/light.js +28 -0
  92. package/dist/validate/light.js.map +1 -0
  93. package/dist/validate/runs.d.ts +16 -0
  94. package/dist/validate/runs.d.ts.map +1 -0
  95. package/dist/validate/runs.js +60 -0
  96. package/dist/validate/runs.js.map +1 -0
  97. package/dist/validate/site.d.ts +6 -0
  98. package/dist/validate/site.d.ts.map +1 -0
  99. package/dist/validate/site.js +63 -0
  100. package/dist/validate/site.js.map +1 -0
  101. package/editors/vscode/.vscodeignore +2 -0
  102. package/editors/vscode/README.md +28 -0
  103. package/editors/vscode/extension.js +150 -0
  104. package/editors/vscode/language-configuration.json +19 -0
  105. package/editors/vscode/package.json +57 -0
  106. package/editors/vscode/syntaxes/koyu.tmLanguage.json +226 -0
  107. package/examples/basement/main.muro +3 -3
  108. package/examples/complex/main.muro +1 -1
  109. package/examples/complex/podium.muro +1 -1
  110. package/examples/complex/site.muro +6 -6
  111. package/examples/house/L2.muro +1 -1
  112. package/examples/house/main.muro +2 -2
  113. package/examples/house/site.muro +4 -4
  114. package/examples/house.muro +7 -7
  115. package/examples/mansion.muro +3 -3
  116. package/examples/office.muro +4 -4
  117. package/examples/steps/01-one-room.muro +1 -1
  118. package/examples/steps/02-two-rooms.muro +1 -1
  119. package/examples/steps/03-door.muro +1 -1
  120. package/examples/steps/04-exterior.muro +2 -2
  121. package/examples/steps/05-two-storeys.muro +2 -2
  122. package/examples/steps/06-finished.muro +3 -3
  123. package/examples/tower/L2.muro +1 -1
  124. package/examples/tower/main.muro +1 -1
  125. package/examples/tower/site.muro +4 -4
  126. package/examples/twin/main.muro +2 -2
  127. package/examples/twin/podium.muro +4 -4
  128. package/examples/twin/site.muro +8 -8
  129. package/examples/two-rooms.canonical.json +6 -4
  130. package/examples/two-rooms.muro +3 -3
  131. package/package.json +18 -3
  132. package/src/cli.ts +173 -83
  133. package/src/core/derive.ts +869 -0
  134. package/src/{check.ts → core/diagnose.ts} +313 -235
  135. package/src/{diff.ts → core/diff.ts} +91 -43
  136. package/src/{fabric.ts → core/fabric.ts} +22 -12
  137. package/src/{graph.ts → core/graph.ts} +64 -63
  138. package/src/core/light.ts +69 -0
  139. package/src/{model.ts → core/model.ts} +361 -74
  140. package/src/{parse.ts → core/parse.ts} +618 -135
  141. package/src/{poly.ts → core/poly.ts} +8 -16
  142. package/src/{site.ts → core/site.ts} +2 -2
  143. package/src/core/tolerance.ts +55 -0
  144. package/src/{vertical.ts → core/vertical.ts} +73 -116
  145. package/src/core/vocabulary.ts +210 -0
  146. package/src/{axo.ts → draw/axo.ts} +51 -94
  147. package/src/draw/index.ts +11 -0
  148. package/src/draw/plan.ts +344 -0
  149. package/src/index.ts +201 -34
  150. package/src/mcp.ts +119 -50
  151. package/src/parse-file.ts +19 -5
  152. package/src/validate/access.ts +291 -0
  153. package/src/validate/envelope.ts +59 -0
  154. package/src/validate/index.ts +107 -0
  155. package/src/validate/light.ts +43 -0
  156. package/src/validate/runs.ts +87 -0
  157. package/src/validate/site.ts +84 -0
  158. package/dist/axo.d.ts.map +0 -1
  159. package/dist/axo.js.map +0 -1
  160. package/dist/check.d.ts.map +0 -1
  161. package/dist/check.js.map +0 -1
  162. package/dist/diff.d.ts.map +0 -1
  163. package/dist/diff.js.map +0 -1
  164. package/dist/fabric.d.ts.map +0 -1
  165. package/dist/fabric.js.map +0 -1
  166. package/dist/graph.d.ts.map +0 -1
  167. package/dist/graph.js.map +0 -1
  168. package/dist/light.d.ts +0 -15
  169. package/dist/light.d.ts.map +0 -1
  170. package/dist/light.js.map +0 -1
  171. package/dist/model.d.ts.map +0 -1
  172. package/dist/model.js.map +0 -1
  173. package/dist/parse.d.ts.map +0 -1
  174. package/dist/parse.js.map +0 -1
  175. package/dist/plan.d.ts +0 -10
  176. package/dist/plan.d.ts.map +0 -1
  177. package/dist/plan.js +0 -354
  178. package/dist/plan.js.map +0 -1
  179. package/dist/poly.d.ts.map +0 -1
  180. package/dist/poly.js.map +0 -1
  181. package/dist/site.d.ts.map +0 -1
  182. package/dist/site.js.map +0 -1
  183. package/dist/vertical.d.ts.map +0 -1
  184. package/dist/vertical.js.map +0 -1
  185. package/src/light.ts +0 -63
  186. package/src/plan.ts +0 -472
  187. /package/dist/{parse.d.ts → core/parse.d.ts} +0 -0
  188. /package/dist/{site.d.ts → core/site.d.ts} +0 -0
package/README.ja.md CHANGED
@@ -8,10 +8,12 @@
8
8
 
9
9
  ## ドキュメント
10
10
 
11
- 文書は二冊に分かれている。**[guide/](guide/README.md) が最初の扉**で、[spec/](spec/README.md) が規範である。
11
+ **[docs/](docs/index.md) が文書であり、これが正である。**167頁 ×2言語、目的から引ける形に並べてある。
12
12
 
13
- - **[guide/](guide/README.md)** — 学ぶ本。チュートリアル・六つの考え・how-to・診断コード事典・CLI/APIリファレンス。**koyu を初めて書くなら [guide/start.md](guide/start.md) から** (30〜45分で二階建て一棟と平面図まで届く)
14
- - **[spec/](spec/README.md)** — 規範リファレンス。文法・意味論・語彙の台帳・正準JSON・ツール契約を現在形で
13
+ - **[docs/start/](docs/start/index.md)** — チュートリアル。一室から二階建てまで30〜45分。**koyu を初めて書くならここから**
14
+ - **[docs/why/](docs/why/index.md)** — 解説。なぜ空間が一次要素か、なぜ壁は関係か、なぜ形は一意でなければならないか
15
+ - **[docs/howto/](docs/howto/index.md)** — 手順。目的から引くものと、症状から引くもの
16
+ - **[docs/reference/](docs/reference/index.md)** — 規範。[.muro の全構文](docs/reference/muro/index.md)・[診断65コード](docs/reference/diagnostics/index.md)・[判定15規則](docs/reference/validate/index.md)・[CLI](docs/reference/cli/index.md)・[MCP](docs/reference/mcp/index.md)・[API](docs/reference/api/index.md)・[導出される形](docs/reference/form/index.md)・[正準JSON](docs/reference/json/index.md)
15
17
  - **[docs/decisions/](docs/decisions/)** — ADR。なぜそう決めたか、何を棄却したか
16
18
  - **[AGENTS.md](AGENTS.md)** — このリポジトリで作業するLLMエージェントの入口
17
19
 
@@ -20,25 +22,25 @@
20
22
  ```muro
21
23
  grid X 0 3600
22
24
  grid Y 0 4000
23
- level L1 0
25
+ level L1 0 h:2400 slab:150
24
26
  space /L1/a room X1..X2 Y1..Y2
25
27
  ```
26
28
 
27
29
  `koyu plan` が平面図を出す。壁は一本も描かれていない — 空間はあるが、境界が一つも無いからである。
28
30
 
29
- ![一室の平面図](guide/img/start-01-one-room.svg)
31
+ ![一室の平面図](docs/img/start-01-one-room.svg)
30
32
 
31
33
  `space` をもう一行足す。他は何も変えない。
32
34
 
33
35
  ```muro
34
36
  grid X 0 3600 5400
35
37
  grid Y 0 4000
36
- level L1 0
38
+ level L1 0 h:2400 slab:150
37
39
  space /L1/a room X1..X2 Y1..Y2
38
40
  space /L1/b room X2..X3 Y1..Y2
39
41
  ```
40
42
 
41
- ![二室の平面図。中央に壁が一枚立っている](guide/img/start-02-two-rooms.svg)
43
+ ![二室の平面図。中央に壁が一枚立っている](docs/img/start-02-two-rooms.svg)
42
44
 
43
45
  **壁が一枚現れる。壁を描く操作はどこにも無い。** 壁は二つの空間の境界という関係であり、空間の割付から導出される。接する空間の組に宣言が無ければ、それは「未定義」ではなく「壁」を意味する。
44
46
 
@@ -82,11 +84,13 @@ npm run koyu -- site examples/tower/main.muro # ショーケース: polyg
82
84
 
83
85
  `koyu-mcp` は依存ゼロのMCPサーバー (stdio、ADR-0012)。LLMエージェントが建物を読み (`layers`)、編集し (`write_layer`)、`check` がビルドの門番になる — エラーは出所レイヤー:行つき。`doors` / `light` / `site` は同じ記述への異なる問い。延床4,786㎡のショーケース一棟が原本8,099トークン (実測 — IFC4は14倍、IFCXは25倍: [examples/comparison/](examples/comparison/README.md)) なので、一棟がコンテキストに余裕で載る。エージェントが正しく*編集*できるかは次の分水嶺 — 編集evalは計画段階でまだ実施していない ([docs/horizon.md](docs/horizon.md))。三軸の構想 (デジタルツイン・W3C BOTへのオントロジー整列・都市接続) も同文書。
84
86
 
85
- 登録は一行 (`claude mcp add koyu -- npx -p @kensnzk/koyu koyu-mcp`)。Claude Code・Claude Desktop・その他クライアントでの設定と標準ループは [guide/howto/agent-mcp.md](guide/howto/agent-mcp.md)。
87
+ 登録は一行 (`claude mcp add koyu -- npx -p @kensnzk/koyu koyu-mcp`)。Claude Code・Claude Desktop・その他クライアントでの設定と標準ループは [docs/howto/install-mcp.md](docs/howto/install-mcp.md)、ループの実例は [agent-loop.md](docs/howto/agent-loop.md)。
88
+
89
+ MCPサーバーとCLIは*確かめる*側。muroで仕事をするための知識はエージェントスキルとして別に配り、クライアントが手元で読み込むので呼び出しごとのコストがない — [koyu-design](skills/koyu-design/SKILL.md) が建物を書き、[koyu-validate](skills/koyu-validate/SKILL.md) が判定して直し、[koyu-revise](skills/koyu-revise/SKILL.md) が既存を壊さずに変える。処理系が答える問いごとに一本。導入方法 (Claude Code・Claude.ai・Claude Desktop) は [skills/README.md](skills/README.md)。
86
90
 
87
91
  ## 構成
88
92
 
89
- 現在の仕様は [spec/](spec/README.md) に体系化した — 言語リファレンス ([language.md](spec/language.md))・意味論 ([semantics.md](spec/semantics.md))・語彙の台帳 ([vocabulary.md](spec/vocabulary.md))・正準JSON・ツールリファレンス (CLI/MCP/API)。ADRは「なぜ」を、specは「いま何が真か」を持つ。記法の成立記録 (DSL/YAML/JSON書き比べ) は [spec/notation-v0.md](spec/notation-v0.md)、IFC4とのカバレッジ照合は [docs/ifc-coverage.md](docs/ifc-coverage.md)、設計判断の記録は [docs/decisions/](docs/decisions/)、行程は [docs/roadmap.md](docs/roadmap.md) (Linear: [koyu](https://linear.app/munipersonal/project/koyu-2789f588a03a/overview) と対応)、日々の記録は [docs/log/](docs/log/)。実装は src/ に約7,500行 (パーサ・グラフ・チェック・平面図生成・CLI・MCPサーバー)、テストは test/。IFCXの読解メモは [docs/ifcx-notes.md](docs/ifcx-notes.md)、同じ二室をIFC4・IFCXで書いた三方比較は [examples/comparison/](examples/comparison/README.md)。
93
+ 規範は [docs/reference/](docs/reference/index.md) に体系化してある — 記法・診断・判定・CLI・MCP・API・導出される形・正準JSON。**この木が正である。**ADR ([docs/decisions/](docs/decisions/)) は「なぜ」を持つが後から直さないので、現在の真ではなく履歴である。IFC4とのカバレッジ照合は [docs/ifc-coverage.md](docs/ifc-coverage.md)、行程は [docs/roadmap.md](docs/roadmap.md) (Linear: [koyu](https://linear.app/munipersonal/project/koyu-2789f588a03a/overview) と対応)、日々の記録は [docs/log/](docs/log/)。IFCXの読解メモは [docs/ifcx-notes.md](docs/ifcx-notes.md)、同じ二室をIFC4・IFCXで書いた三方比較は [examples/comparison/](examples/comparison/README.md)。実装は src/ に約7,500行 (パーサ・グラフ・チェック・平面図生成・CLI・MCPサーバー)、テストは test/。IFCXの読解メモは [docs/ifcx-notes.md](docs/ifcx-notes.md)、同じ二室をIFC4・IFCXで書いた三方比較は [examples/comparison/](examples/comparison/README.md)。
90
94
 
91
95
  ## 技術方針
92
96
 
@@ -102,4 +106,4 @@ TypeScriptで書き、実行時依存はゼロに保つ。BIM/IFC系のツール
102
106
 
103
107
  ## ライセンス
104
108
 
105
- コード (src/, test/, examples/ ほか) は [Apache License 2.0](LICENSE)。文書 (docs/, spec/, 原稿「[建築を書く](docs/writing-architecture.md)」) は [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.ja)。引用情報は [CITATION.cff](CITATION.cff)。
109
+ コード (src/, test/, examples/ ほか) は [Apache License 2.0](LICENSE)。文書 (docs/, 原稿「[建築を書く](docs/writing-architecture.md)」) は [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.ja)。引用情報は [CITATION.cff](CITATION.cff)。
package/README.md CHANGED
@@ -9,11 +9,12 @@ An exploration of text-native architectural description with **space as the prim
9
9
 
10
10
  ## Documentation
11
11
 
12
- The prose is split into two books, in Japanese. Start at the guide; consult the reference.
12
+ **[docs/](docs/index.md) is the documentation, and it is authoritative.** 167 pages in Japanese and English, laid out by what you came to do.
13
13
 
14
- - **[guide/](guide/README.md)** — the guide: a tutorial that goes from one room to a two-storey house in 30–45 minutes, the six concepts, how-to recipes, the diagnostic-code handbook, and the CLI and API references. **If you are learning koyu, start at [guide/start.md](guide/start.md).**
15
- - **[spec/](spec/README.md)** — the normative reference: grammar, semantics, the attribute ledger, canonical JSON, tool contracts. Present tense, no history.
16
- - **[docs/decisions/](docs/decisions/)** — the ADRs: why each decision was made and what was rejected.
14
+ - **[docs/start/](docs/start/index.md)** — the tutorial: one room to a two-storey house in 30–45 minutes. **If you are learning koyu, start here.**
15
+ - **[docs/why/](docs/why/index.md)** — the explanations: why space is primary, why a boundary is a relation, why the form must be unique.
16
+ - **[docs/howto/](docs/howto/index.md)** — recipes, by goal and by symptom.
17
+ - **[docs/reference/](docs/reference/index.md)** — the normative reference: [every `.muro` word](docs/reference/muro/index.md), [all 65 diagnostics](docs/reference/diagnostics/index.md), [the 15 verdicts](docs/reference/validate/index.md), [the CLI](docs/reference/cli/index.md), [the MCP server](docs/reference/mcp/index.md), [the API](docs/reference/api/index.md), [the derived form](docs/reference/form/index.md), [canonical JSON](docs/reference/json/index.md).
17
18
  - **[AGENTS.md](AGENTS.md)** — the entry point for LLM agents working in this repository.
18
19
 
19
20
  One room is written like this. Four lines, and it is a complete file.
@@ -21,25 +22,25 @@ One room is written like this. Four lines, and it is a complete file.
21
22
  ```muro
22
23
  grid X 0 3600
23
24
  grid Y 0 4000
24
- level L1 0
25
+ level L1 0 h:2400 slab:150
25
26
  space /L1/a room X1..X2 Y1..Y2
26
27
  ```
27
28
 
28
29
  `koyu plan` produces the floor plan. Not one wall is drawn — there is a space, but not one boundary.
29
30
 
30
- ![Plan of a single room](guide/img/start-01-one-room.svg)
31
+ ![Plan of a single room](docs/img/start-01-one-room.svg)
31
32
 
32
33
  Add one more `space` line. Change nothing else.
33
34
 
34
35
  ```muro
35
36
  grid X 0 3600 5400
36
37
  grid Y 0 4000
37
- level L1 0
38
+ level L1 0 h:2400 slab:150
38
39
  space /L1/a room X1..X2 Y1..Y2
39
40
  space /L1/b room X2..X3 Y1..Y2
40
41
  ```
41
42
 
42
- ![Plan of two rooms, with a wall standing between them](guide/img/start-02-two-rooms.svg)
43
+ ![Plan of two rooms, with a wall standing between them](docs/img/start-02-two-rooms.svg)
43
44
 
44
45
  **A wall appears. There is no operation anywhere that draws a wall.** A wall is the boundary relation between two spaces, derived from the layout of those spaces. Where a pair of touching spaces has no declaration, that means "wall" rather than "undefined".
45
46
 
@@ -59,9 +60,9 @@ A building can also be written as a set of files and composed — additive layer
59
60
 
60
61
  1. **Install.** Clone this repository and run `npm install`.
61
62
  2. **Write the four lines above** into `first.muro`, then run `npx tsx src/cli.ts check first.muro` and `npx tsx src/cli.ts plan first.muro -o out/first.svg`.
62
- 3. **Read a bundled example.** `npx tsx src/cli.ts check examples/two-rooms.muro` prints `✔ 整合 — 空間 3 / 境界 3`; `stats`, `graph`, and `doors` answer about the same file.
63
+ 3. **Read a bundled example.** `npx tsx src/cli.ts check examples/two-rooms.muro` prints `✔ Consistent — 3 spaces / 3 boundaries`; `stats`, `graph`, and `doors` answer about the same file.
63
64
 
64
- `grid` and `level` must be declared before anything that refers to them, and the type (`room`, the second positional word) is required; everything else — the `koyu` version line, `unit`, `name`, heights — is optional. From here, [guide/start.md](guide/start.md) (Japanese) is a managed path from this one room to a two-storey house with per-floor plans, a circulation check, and a daylight check.
65
+ `grid` and `level` must be declared before anything that refers to them, and the type (`room`, the second positional word) is required; everything else — the `koyu` version line, `unit`, `name`, heights — is optional. From here, [docs/start/](docs/start/index.md) is a managed path from this one room to a two-storey house with per-floor plans, a circulation check, and a daylight check.
65
66
 
66
67
  ## Usage
67
68
 
@@ -91,11 +92,13 @@ npm run koyu -- site examples/tower/main.muro # showcase: polygon site, t
91
92
 
92
93
  `koyu-mcp` is a zero-dependency MCP server over stdio (ADR-0012): an LLM agent reads the building (`layers`), edits it (`write_layer`), and `check` acts as the build gate — errors come back with layer:line provenance. `doors` / `light` / `site` / `stats` are the same description read different ways. The whole 4,786m² showcase is 8,099 tokens as source (measured; IFC4 is 14x, IFCX 25x — see [examples/comparison/](examples/comparison/README.md)), so a whole building fits in one context with room to work. Whether an agent can *edit* it correctly is the next watershed — an edit eval is planned, not yet run ([docs/horizon.md](docs/horizon.md)). The horizon design (digital twin, ontology alignment via W3C BOT, city connection) is in the same document.
93
94
 
94
- Registering it is one line (`claude mcp add koyu -- npx -p @kensnzk/koyu koyu-mcp`). Setup for Claude Code, Claude Desktop, and other clients, plus the standard loop, is in [guide/en/howto/agent-mcp.md](guide/en/howto/agent-mcp.md).
95
+ Registering it is one line (`claude mcp add koyu -- npx -p @kensnzk/koyu koyu-mcp`). Setup for Claude Code, Claude Desktop, and other clients, plus the standard loop, is in [docs/howto/install-mcp.md](docs/howto/install-mcp.md).
96
+
97
+ The MCP server and the CLI are the half that *judges*; the knowledge for working in muro ships separately as agent skills, loaded locally by the client so they cost nothing per call — [koyu-design](skills/koyu-design/SKILL.md) writes a building, [koyu-validate](skills/koyu-validate/SKILL.md) judges and repairs one, [koyu-revise](skills/koyu-revise/SKILL.md) changes one without breaking the rest. One skill per question the processor answers. Installation (Claude Code, Claude.ai, Claude Desktop) is in [skills/README.md](skills/README.md).
95
98
 
96
99
  ## Layout
97
100
 
98
- The learning material lives in [guide/](guide/README.md) — tutorial, concepts, how-to, diagnostics, CLI/API. The current specification lives in [spec/](spec/README.md) — language reference, semantics (derivations, checks, queries), the attribute ledger, the canonical JSON format, and the tool reference (CLI / MCP / API). ADRs record why decisions were made; spec/ states what is true now. The historical record of how the notation was chosen (with the DSL/YAML/JSON comparison) is [spec/notation-v0.md](spec/notation-v0.md); coverage against the IFC4 architectural core is [docs/ifc-coverage.md](docs/ifc-coverage.md); design decisions are recorded in [docs/decisions/](docs/decisions/); the roadmap is [docs/roadmap.md](docs/roadmap.md); daily logs are in [docs/log/](docs/log/). The implementation is ~7,500 lines in src/ (parser, graph, checks, plan generation, CLI, MCP server), tests in test/. Reading notes on IFCX are in [docs/ifcx-notes.md](docs/ifcx-notes.md); the same two rooms written three ways (this notation, IFC4, IFCX) is in [examples/comparison/](examples/comparison/README.md).
101
+ The documentation lives in [docs/](docs/index.md) — tutorial, explanations, how-to, and the normative reference (the notation, diagnostics, verdicts, CLI, MCP, API, the derived form, canonical JSON). **That tree is authoritative**; ADRs in [docs/decisions/](docs/decisions/) record why each decision was made and are never amended, so they are history rather than current truth. Coverage against the IFC4 architectural core is [docs/ifc-coverage.md](docs/ifc-coverage.md); the roadmap is [docs/roadmap.md](docs/roadmap.md); daily logs are in [docs/log/](docs/log/). The implementation is ~7,500 lines in src/ (parser, graph, checks, plan generation, CLI, MCP server), tests in test/. Reading notes on IFCX are in [docs/ifcx-notes.md](docs/ifcx-notes.md); the same two rooms written three ways (this notation, IFC4, IFCX) is in [examples/comparison/](examples/comparison/README.md).
99
102
 
100
103
  ## Technical stance
101
104
 
@@ -111,4 +114,4 @@ The file extension is `.muro` (室, *muro* — room). The unit a file holds is n
111
114
 
112
115
  ## License
113
116
 
114
- Code (src/, test/, examples/, …) is under the [Apache License 2.0](LICENSE). Documents (docs/, spec/, and the essay "[建築を書く / Writing Architecture](docs/writing-architecture.md)") are under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Citation metadata is in [CITATION.cff](CITATION.cff).
117
+ Code (src/, test/, examples/, …) is under the [Apache License 2.0](LICENSE). Documents (docs/, and the essay "[建築を書く / Writing Architecture](docs/writing-architecture.md)") are under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Citation metadata is in [CITATION.cff](CITATION.cff).