Skip to content

docs(readme): translate the eight Russian sections into English (L3 PURITY) - #386

Open
gHashTag wants to merge 2 commits into
mainfrom
docs/readme-english
Open

docs(readme): translate the eight Russian sections into English (L3 PURITY)#386
gHashTag wants to merge 2 commits into
mainfrom
docs/readme-english

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 3, 2026

Copy link
Copy Markdown
Owner

README.md carried 76 lines of Cyrillic across eight sections while the rest of the file was already English. L3 PURITY requires English throughout - source, comments and documentation alike - so the file was half in violation of the law it ships with.

Prose only. Branched from current main (759f5e9).

Sections translated

What Tri-Net does, Three boards as the base of the network, the Metrics and DePIN-tokenomics table headers, Local flashing is the current priority, the Roadmap stage metaphors, the Science base / VAK section, and the Russian descriptions under Related repos and Key docs.

Structurally lossless

before after
Cyrillic lines 76 0
headings 19 19
table rows 54 54
markdown links 28 28
code fences 4 4
lines 240 240

The diff is 76 insertions, 76 deletions - exactly the 76 Cyrillic lines, so nothing but prose moved. Every figure, hash, date, chip name, contract check and URL is carried across verbatim.

Three judgement calls, stated rather than made silently

  1. The Roadmap preamble. It said each stage is given "in English (technical) and in Russian (metaphor)". With both halves now in English that sentence no longer describes the document, so it reads "Each stage is stated twice: technically, and as a metaphor." The metaphors are kept - they carry the document's voice.

  2. P6 needs a second opinion. Its last clause used the verb zakryvaetsya, literally "is closed", which contradicts both the preceding clause and this file's own rule that silicon-anchored claims stay [Open conjecture] until the die returns. I translated it to the meaning the rest of the document requires - the conjecture cannot be closed. If the Russian was meant literally, this line should be corrected rather than re-translated.

  3. One Cyrillic fragment was not prose: a heading anchor on the docs/W7_WEAK_POINTS_STRUCTURAL.md link. The anchor was dropped rather than transliterated, because that file does not exist on main. The citation itself is kept.

Found while checking the links survived - not fixed here

Five of the eight local documents this README points at are absent from main:

  • docs/STRENGTHEN.md
  • docs/W7_WEAK_POINTS_STRUCTURAL.md
  • docs/WAVE_DEPIN_2026-07-04.md
  • docs/WAVE_N3_AUDITABILITY_GAP_2026-07-04.md
  • docs/_recon/DEPIN_COMPETITORS_2026-07-04.md

A pre-existing condition, unrelated to language. Repairing it means deciding per document whether the file is restored or the reference retired, which is a separate change.

phi^2 + phi^-2 = 3

🤖 Generated with Claude Code

@gHashTag
gHashTag force-pushed the docs/readme-english branch from bc02184 to eaf885a Compare September 3, 2026 13:14
gHashTag and others added 2 commits September 3, 2026 20:22
…URITY)

README.md carried 76 lines of Cyrillic across eight sections while the rest of
the file was already English. L3 PURITY requires English throughout - source,
comments and documentation alike - so the file was half in violation of the
law it ships with.

Translated: "What Tri-Net does", "Three boards as the base of the network",
the Metrics and tokenomics table headers, "Local flashing is the current
priority", the Roadmap stage metaphors, the Science base / VAK section, and
the Russian descriptions in Related repos and Key docs.

Prose only. Nothing else moved, and the structure is unchanged: 19 headings,
54 table rows, 28 markdown links, 4 code fences, 240 lines before and after.
Every figure, hash, date, chip name, contract check and URL is carried across
verbatim.

Three notes on judgement calls rather than silent choices:

The Roadmap said each stage is given "in English (technical) and in Russian
(metaphor)". With both halves now in English that sentence no longer describes
the document, so it reads "Each stage is stated twice: technically, and as a
metaphor." The metaphors are kept - they carry the document's voice.

P6 ended with a clause whose verb was "zakryvaetsya" - literally "is closed" -
which contradicts the preceding clause and the file's
own rule that silicon-anchored claims stay `[Open conjecture]` until the die
returns. Translated to the meaning the rest of the document requires: the
conjecture "cannot be closed". If the Russian was meant literally, this needs
a second look.

The one Cyrillic fragment that was not prose was a heading anchor on the
docs/W7_WEAK_POINTS_STRUCTURAL.md link. It was dropped rather than
transliterated, because that file does not exist on main. The citation itself
is kept.

Not fixed here, found while checking that the links survived: five of the
eight local documents this README points at are absent from main -
docs/STRENGTHEN.md, docs/W7_WEAK_POINTS_STRUCTURAL.md,
docs/WAVE_DEPIN_2026-07-04.md, docs/WAVE_N3_AUDITABILITY_GAP_2026-07-04.md
and docs/_recon/DEPIN_COMPETITORS_2026-07-04.md. That is a pre-existing
condition, unrelated to language, and repairing it means deciding whether each
document is restored or the reference is retired.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
#380 refreshed the Metrics table row to 432 `#[test]` blocks but left the
prose reference in the Build & test section at 110, so one page asserted two
different numbers about the same thing.

432 is the correct one, established by running the command the table cites as
its own source rather than by trusting either figure:

    $ grep -rE '^\s*#\[test\]' src tests | wc -l
    432

Separate from the translation commit on purpose: that commit claims to be
prose-only and structurally lossless, 76 lines in and 76 out, and changing a
number inside it would make the claim false.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@gHashTag
gHashTag force-pushed the docs/readme-english branch from eaf885a to a637978 Compare September 3, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant