Academic Writing Principles (The Press-Release Principle)

One-Sentence Principle

I. Narrative Rules

1. Organize the paper around strengths. Prioritize what is genuinely leading, distinctive, or irreplaceable in the work: a new capability, a new problem, a new mechanism, a new perspective, stronger applicability, lower cost, higher efficiency, better scalability, or a more meaningful trade-off. Content that does not constitute a strength does not enter the main narrative.
2. Do not write the paper as a work report. Do not organize it as "what we did first, what we tried later, and what failed." Retain only the logic that ultimately holds: why the problem matters → why existing methods are insufficient → what new solution this work provides → how the evidence supports it.
3. Do not turn an unwinnable dimension into the competition. If a metric is not an advantage, do not build the narrative around it. Instead, choose a task definition, evaluation dimension, application scenario, constraint, or comparison setup that better reflects the paper's value. Do not compete for a championship that does not belong to this work; clearly articulate that the paper wins a different and more meaningful competition.
4. State the advantages explicitly. Do not expect reviewers to discover the contributions on their own from the tables. Explain proactively: under which conditions the work performs best, why that advantage occurs, what practical problem it solves, and why it matters.
5. Control the scope of comparisons. Do not pursue "leading across every dataset and every metric." Make only claims that the evidence can robustly support. Persuasiveness comes from close alignment between claims and evidence, not from maximizing the number of comparison items.
6. Allow a complete reconstruction of the story. When the existing results cannot support the original narrative, do not defend that narrative. Redefine the problem, reorder the contributions, reselect the primary results, and redesign the title, abstract, introduction, and experimental structure. The story should serve the strongest evidence rather than remain loyal to the initial idea.

II. Language Rules (Preventing Self-Weakening)

• Prohibit self-weakening expressions such as "unfortunately," "only," "still trails significantly," "limited effectiveness," and "has serious shortcomings."
• Do not say the work loses. For results that are not favorable, do not use phrases such as "the proposed method is weaker than," "performance drops," or "failed to outperform." Evaluate the following in order: ① Is the result required to be discussed? ② Can it be explained in terms of different objectives, constraints, or application scenarios? ③ Does it represent a reasonable trade-off? ④ Can the claims be narrowed to avoid unnecessary head-to-head comparisons? ⑤ Should the main narrative be adjusted so that it no longer bears the responsibility of proving the core contribution?
• When a result does not constitute an advantage, there is no need to elevate it into a conclusion, much less help readers turn a local phenomenon into a rejection of the entire method.

III. Experimental Rules

• Demonstrate that the core method is effective;
• Demonstrate that the advantage comes from a key mechanism;
• Demonstrate that the method provides value in the target scenario;
• Rule out the most plausible alternative explanation.

IV. Structural Rules

V. Default Decision Rules (When Encountering Unfavorable Material, Handle It in This Priority Order)

1. Remove content unrelated to the core claim;
2. Narrow the claims to avoid meaningless head-to-head comparisons;
3. Change to evaluation dimensions that better demonstrate the value;
4. Interpret the results as differences in objectives or reasonable trade-offs;
5. Restructure the experiments so that the advantages become the visual and narrative center;
6. Redefine the paper's story;
7. Provide necessary explanations only when the issue cannot be avoided and genuinely affects the core conclusion.

VI. Pre-Submission Self-Check (Do Not Hand Reviewers a Knife)

• Does this sentence inadvertently expand the responsibility the paper must bear?
• Does it raise a question that nobody asked you to answer?
• Does it describe a local phenomenon as a universal flaw?
• Does it use a negative judgment broader than the evidence?
• Is the paper organized as a chronological account of "what we did"?
• Has a metric in which the work does not lead been made the main battlefield?
• Have both the problem and the contribution appeared within the first five sentences of the abstract?
• Does the conclusion abruptly introduce self-negation?

Final Goal