anti-defensive-writing

Remove audit, defensive, self-critical, developer-facing and commitment writing from a manuscript, its Supplementary Information, figure legends, table notes, data and code statements and figure content, while keeping every number, definition, reproducibility fact, mandated statistical statement, null result and scope condition that sets a reported value. Audit voice is project process leaking into the paper (locked, frozen, hashed, verified, post hoc, leakage-safe, gate verdicts, implementation checks). Defensive voice argues with an imagined reviewer (does not establish, should not be read as, we do not claim, for completeness). Self-critical voice has the paper judge or apologize for itself (could not be identified, not directly comparable, only a small fraction, unused datasets listed, table columns that grade their own rows). Developer voice addresses whoever runs the repository instead of whoever reads the paper (folder paths, file names, workbook sheets, manifests, loaders, editable or generated LaTeX). Commitment voice promises what does not exist yet (will be released, planned before acceptance, access can be arranged). Also carries the rule for not adding any of these while editing. Runs at the rhetorical-posture layer, after the claim hierarchy is settled and before the sentence pass. Load when a draft or SI reads like an audit report, a rebuttal letter, a self-critique or a repository README, when a paragraph opens with a limitation, or on request: de-audit, less defensive, more direct, cut the hedging, remove developer notes, no promises, 去审计, 审计味, 防御性写作, 自我批评, 自我限制, 评判式写作, 去包装, 太多免责, 写得太怂, 太啰嗦, 让语气更肯定, 别老说自己不主张什么, 读者和编辑不关心的内容, 面向开发人员, 代码路径, 文件名, 事前承诺.

License

MIT