Languages

Italian and English

Koòrd exists in two languages, and which is which is not incidental.

Italian is where the method comes from. It was created, refined and tested most extensively in Italian: the document was written in it, and the practice that produced the method — the sessions, the corrections, the failures that shaped the rules — happened in it. The Italian text is the original of record.

English is the language in which Koòrd is published. A method proposed to people who work with language models has to travel, and it will not travel far in Italian alone. The English text carries the work outward; this wiki is written in it for the same reason.

Neither is a second-class version. The Italian has the longer record of use behind it; the English is the one most readers will meet first.

What exists in which language

	Italian	English
The method document, Markdown source	✓	✓
Styled renderings, light and dark	✓	✓
Claude skill	koordinated-thinking-it	koordinated-thinking-en
Open WebUI skills	✓	✓
FlatSkill, one self-contained file	koordinated-thinking-flatskill-it.md	koordinated-thinking-flatskill-en.md
This wiki	—	✓
Repository documentation, commit history	—	✓ (history in Italian)

The renderings are reachable from the entry point, which offers both languages and both themes without choosing for the reader.

If the two disagree

A difference in substance between the Italian and the English is a translation defect to report, not a variant to interpret. The instrument is one; two texts that say different things are a bug in one of them.

The same applies to the two Claude skills: they are the same skill, and each ships the method document in its own language as its rationale layer. Every copy of the document shipped inside a skill is kept identical to its source in the repository by a check that runs on every change — so a skill can never quote a version of the method that is no longer published.

Which skill to install

The one whose language you work in. Installing both is harmless: each is described in the language it applies to, and is selected by the language of the request.

On Open WebUI the same holds, with one difference of its own: the English Skill IDs carry an -en suffix, so both sets can be installed in the same instance without colliding.

The FlatSkills follow the same rule, and the language is in the filename because there is no front matter to carry it: paste or attach the file whose language you work in. Unlike the other two packagings this one carries the rationale condensed into a section rather than shipping the method document, so the language of the file is the only language present.