b173ac82a9
- adapt meta-/code-/obs- rules to the local Python benchmark pipeline - replace db-sql-ddl, code-config-env-scope, test-e2e-pytest with pipeline equivalents - add code-python-style, data-determinism, data-naming-units, bench-methodology, build-pipeline-tasks - normalize specs and README typography to ASCII per code-data-formatting - rewrite root CLAUDE.md trigger table; add .cursorrules and .gitignore - specs: pipeline plan and task specs 00-11 - rules: 19 binding rule files adapted for this project - docs: CLAUDE.md rule-trigger table - config: .cursorrules commit convention, .gitignore excluding out/ and .venv/ - docs: rewrite README.md with pipeline diagrams, setup guide, result placeholders - config: requirements.txt for the closed dependency list - datagen: make_lab_config.py writes out/config/lab_config.yaml and .done marker
1.5 KiB
Meta / Communication language and register
Binding on every response and on all prose directed at the user (explanations, status updates, questions, summaries, commit messages, PR text).
Rule
- Language: Russian. All communication with the user is in standard literary Russian.
- Register: neutral and professional. No jargon, no slang, no profanity.
- No profanity or vulgar words - in any language, under any circumstances.
- No slang or jargon: street slang, gamer/internet slang, or untranslated English buzzwords used as slang.
- Prefer the established Russian word over a transliterated English one whenever a normal Russian equivalent exists.
- Plain, grammatical, complete sentences.
Allowed terminology (not slang)
Field-standard technical terms are fine - they are terminology, not jargon: e.g. «коммит», «билд», «дебаг», «релиз», «мерж». When unsure whether a word is accepted terminology or slang, choose the neutral Russian equivalent.
Scope
Does not apply to source code, identifiers, file paths, code comments, shell/tool output, or verbatim quotes of errors and logs - those keep the language of the codebase.
Canonical source
This file is the project-level binding rule. It restates the project owner's standing preference (communication in Russian; code, docs, and artifacts in English). If a global user-level rule ever diverges from this file, the stricter wording wins.