muchsci Paper Sailor has two iron rules. The first is “do not fabricate,” which gets talked about more; the second is often overlooked—the language version does not decide for you: Chinese and English manuscripts run as two independent production lines, and you choose once before submission.
At first glance it looks like a feature description; on closer inspection, it is a product philosophy question: why should even something like “Chinese or English” be written into an iron rule?
First, the flip side: the everyday reality of mixed production lines
Bilingual writing that is not governed by an iron rule usually looks like this: after finishing the Chinese draft, you want to produce an English version along the way, so the two versions overwrite each other in the same folder; file names evolve from “paper final draft” to “paper final draft 2 English final version,” and on the night before submission you are searching for “where exactly is the latest version?”; worse still, things get mixed up—Chinese paragraphs end up in the English manuscript, and you only find out after submitting.
The root cause of dual-manuscript chaos is not that you are not careful enough; it ismixed versions: the outputs in two languages share one set of storage, one naming scheme, and one status, so errors are only a matter of time.
The production-line solution: physical isolation
Paper Sailor's arrangement is straightforward: Chinese and English manuscripts are two independent production lines, each going through the full process of outline, first draft, review, and polishing; output directories and file names follow the language, all versions of the Chinese manuscript are archived independently, and the same goes for the English manuscript. Physical isolation means: you cannot mistakenly write an English paragraph into the Chinese manuscript's archive, because they never live in the same room from the start.
The “ask only once” design
The second half of the iron rule is “let you choose once before submission.” Once the process starts, the language path is set, and the tool no longer repeatedly asks “confirm English?”—one confirmation is design; repeated confirmation is noise. Turning a repeated decision into a one-time setting is exactly the value of “hard-coding it into the rules”:an iron rule is not a restriction; it automates the decisions that should be automated and solemnly leaves the decisions that should not be automated (your choice) to you.
Mixed production lines vs. separate production lines, clear in one table
| The everyday reality of mixed production lines | muchsci's arrangement |
| --- | --- |
| Chinese and English versions get mixed up; Chinese paragraphs end up in the English manuscript | Two languages, two production lines, physically isolated |
| File names make it impossible to tell which version is the English final draft | Directories and file names are named according to language rules |
| On the night before submission, searching for “where exactly is the latest version?” | One confirmation before submission, then no more changes |
Who the iron rule applies to
There are more scenarios requiring both Chinese and English manuscripts than you might imagine: a course requires a Chinese report, a graduation thesis requires an English abstract and full text, submitting to an international journal requires an English manuscript, and an advisor requires a bilingual comparison. As long as your writing crosses languages, muchsci's two-production-line isolation design is there to block a whole category of low-level accidents for you.
A tool's sense of boundaries is as important as the number of its features. The second iron rule is worth remembering—it governs the chaos most familiar to all bilingual writers, and the method it uses is plain and simple: let Chinese belong to Chinese, and English belong to English.