TRANSLATIONS.md

Translations

Translate the core Loop Engineering concepts for new audiences while preserving the boundaries and facts in the full English guide.

Available

• English
• 中文
• Español
• Français
• Deutsch
• 日本語
• 한국어
• Português

Wanted

Maintainers and contributors are welcome for:

• Русский
• Italiano
• العربية
• हिन्दी

Translation Rules

• Preserve the narrow definition: AI/coding-agent Loop Engineering as the layer above prompt, context, and harness engineering.
• Do not translate unrelated meanings into scope: event loops, control theory, growth loops, generic automation, or non-AI feedback loops.
• Keep the English README as the source of truth for the full resource list.
• Prefer translating the introduction, mental model, Loop Contract, maturity model, and contribution instructions first.
• If you translate the full resource list, keep URLs unchanged and translate only annotations.
• Add yourself as a translation maintainer in your PR if you can help keep the file current.
• Every translation carries a <!-- last-synced: YYYY-MM-DD --> marker near the top. When you review a translation against the current English README, bump the date. CI fails when a marker is missing or older than 180 days.

Suggested File Names

• README.de.md
• README.es.md
• README.fr.md
• README.ja.md
• README.ko.md
• README.pt-BR.md
• README.ru.md

Translation PR Checklist

• The translation links back to the full English guide.
• The language switcher has been updated in README.md.
• The <!-- last-synced: YYYY-MM-DD --> marker is present and current.
• The translation preserves the scope boundary.
• Resource URLs are unchanged.
• Technical terms are translated consistently or left in English where that is clearer.