本课目标

学完本课，你能够：

• 找出专业说明中的过程、目的和保护措施；
• 用通俗词汇重组复杂被动流程；
• 使用有限类比帮助理解而不声称两件事完全相同；
• 明确听者无需执行的技术动作和仍需采取的实际行动；
• 完成一段2分钟的非专业流程说明。

本课边界

本课仍使用虚构目录迁移信息包。Mateo是一次性虚构系统工程师，流程、字段和验证规则只服务语言训练，不构成真实数据迁移、网络安全或档案管理建议。通俗解释必须保留“原系统不被覆盖”“自动检查不等于内容正确”“异常项需人工复核”三项限制。

场景词汇

• export 导出文件／导出
• checksum 校验值
• field 数据字段
• mapping 对应关系
• automated check 自动检查
• manual review 人工复核
• flag 标记
• overwrite 覆盖原数据

---

Plain English removes unnecessary terminology, not necessary safeguards

Mateo gives Robin a technical process note. Robin tests a public-facing explanation while Mateo checks whether each simplification remains accurate.

Part A — Turning a process into visible steps

Mateo: The formal note says, “Once an immutable export has been generated, a checksum is calculated and the source object is retained outside the import environment.”

Robin: Let me put that in plain English. First, a fixed copy of the selected records is made, and the original catalog is left unchanged.

Mateo: Good. The checksum does not prove that every description is correct. It helps us detect whether the exported file changes unexpectedly after it is created.

Robin: In other words, it checks whether we are still working with the same package of data, not whether every fact inside the package is true.

Mateo: Exactly. Next, each old field is matched to a place in the test system: creator to creator, date to date and item number to item number.

Robin: Think of it as matching columns on two forms. The analogy helps with structure, although real fields can contain rules that a paper form does not show.

Mateo: After the mapping has been applied, the three hundred records are imported into a separate test area.

Robin: What happens first is copying and checking the package; what happens next is matching the fields and loading the test copy.

Mateo: Then automated checks look for missing item numbers, impossible date formats and record-count differences.

Robin: You don’t need to run those checks yourself; the project team runs them. Volunteers only report a visible error with the item number.

Part B — Explaining what automation cannot decide

Mateo: Records that fail a structural check are flagged and set aside. They are not silently corrected or deleted.

Robin: So “flagged” means the team stops that item for review, not that the source record has been judged wrong.

Mateo: Correct. Some accurate historical descriptions use unusual dates or names, so a warning may identify an exception rather than an error.

Robin: The important limit is that automated checks can find patterns and missing fields, but a person must decide whether the content makes sense.

Mateo: A sample is also reviewed manually against the unchanged source. If a mapping rule caused repeated errors, the test batch would be rejected and rebuilt.

Robin: Does “rejected” mean the archive is lost?

Mateo: No. Only that test import is discarded. Because the source was not overwritten, the team can correct the rule and create another test.

Robin: Then my analogy needs a warning: it is like checking a copied packing list against the original, but the system also applies field rules that a packing list does not.

Mateo: That works. An analogy should illuminate one relationship and then state where the comparison stops.

Robin: My final version will give five steps, the volunteer action and three limits. That is plain English without pretending the process is effortless or foolproof.

Five-step public explanation

Step	Plain-English action	Protection or limit
1	make a fixed copy	original catalog stays unchanged
2	confirm the copy has not unexpectedly changed	checksum does not verify factual accuracy
3	match old fields to new fields	some fields contain special rules
4	load 300 records into a separate test area	not a public replacement
5	run structural checks and human review	warnings may be valid exceptions

Check the story

1. What does the checksum help detect?
2. What does it not prove?
3. Which analogy does Robin use for field mapping?
4. What should volunteers do?
5. Why can an accurate record be flagged?
6. What happens if one mapping rule creates repeated errors?

---

通俗不是删除所有技术关系

checksum可以先解释成“检查导出文件是否意外变化”，但仍要补一句它不核验内容事实。只说“确保数据正确”会过度承诺。

被动语态可以保留过程重点

A fixed copy is made.
Unmatched records are set aside for review.

公众说明不必每句都命名技术执行者，但若责任或下一行动重要，应补the project team或a reviewer。

类比必须说明停止点

“两张表对列”解释字段对应很有用，却不能呈现全部规则。好类比包含It is like … in one respect, but …。

---

本课负荷说明

本课主动掌握6个新词块。L90六个双来源综合词块在第7部分C完成近R；GR066在新的非争议技术流程中完成远迁移。

1. Let me put that in plain English.

提示将专业说明转换为非专业版本；中性、帮助性。

Let me put that in plain English: the original catalog is not replaced during the test.

2. In other words, …

用不同措辞重述同一关系。

In other words, the check detects file changes, not factual errors.

3. Think of it as …

引出有限类比。

Think of it as matching columns on two forms.

4. What happens first is …

突出流程起点和顺序。

What happens first is making a fixed copy.

5. You don't need to …; the system／team …

区分听者责任与后台动作。

You don’t need to run the checks; the project team runs them.

6. The important limit is …

明确简化说明不能删除的边界。

The important limit is that an automated warning is not a factual judgment.

Don’t Say It That Way

容易说出的句子	问题	更准确的表达
The checksum proves the data is correct.	文件一致性被写成内容正确	The checksum helps detect unexpected changes to the exported file.
The computer fixes bad records.	自动检查、判断和修改混在一起	The system flags structural exceptions; a person reviews them.
It works exactly like a packing list.	类比范围无限扩大	It is like a packing list for matching fields, but the system applies additional rules.
Volunteers don't need to know anything.	删除其实际行动	Volunteers do not run checks; they report visible errors with the item number.

---

1. 时间连接词＋被动

Once the export has been created, a checksum is calculated.
After the mapping has been applied, the records are imported.

完成被动表示前一步已经完成；一般被动说明流程中的下一动作。

2. 限定性关系从句筛选对象

Records that fail a structural check are flagged.

不是所有记录都被标记。关系从句是范围控制，不可在通俗版中随意删除。

3. 情态被动表达能力与限制

Unexpected file changes can be detected.
Factual accuracy cannot be guaranteed by this check.

能力、必要性和保证强度必须与来源一致。

4. 被动不应隐藏关键行动者

Errors are reviewed若听者需要提交问题，应补：The archive team reviews them; volunteers send the item number.

快速练习

1. Once the export has been ______, a checksum is calculated. (created / creating)
2. Records that fail the check ______ set aside. (are / is)
3. Automated warnings cannot be ______ as factual judgments. (treated / treating)
4. 用after连接mapping和import。
5. 把The system fixes errors改成准确的被动流程。
6. 写一句明确志愿者和项目团队的不同动作。

---

FIRST, / a fixed copy is MADE.
NEXT, / the fields are MATCHED.
THEN, / the test records are IMPORTED AND CHECKED.

限制句放慢并重读否定：

The important limit is / that a warning does NOT prove / the record is WRONG.

影子跟读

Let me put that in plain English.
Think of the mapping as matching columns on two forms.
You don’t need to run the checks; the project team does that.
The important limit is that automation cannot judge every historical description.

---

A. 理解检查

判断正误：

1. The source catalog is overwritten during the test.
2. A checksum verifies every historical fact.
3. Field mapping connects old and new data locations.
4. Volunteers run automated checks.
5. A warning can identify a valid exception.
6. A failed test import can be discarded without deleting the source.

B. Process / Purpose / Actor / Limit

为五个步骤各写四栏。若原说明没有指出执行者，可以写not named，不要凭经验补充公司或职位。

C. L90近R：两位专家如何解释同一流程

使用Both experts agree that / Where they differ is / According to / places more weight on / doesn't necessarily contradict / The disagreement turns on比较两份流程说明；不得把术语多的一方自动当作更准确。

D. 类比压力测试

为checksum或field mapping写一个类比，再回答：它解释哪一项关系？会引出什么误解？哪一句限制必须紧跟其后？

E. 复杂被动改写

把一段六句技术说明改成五步公众流程。必须包含完成被动、一般被动、情态被动和一个限定性关系从句。

F. 2分钟通俗说明

听者只需要知道：会发生什么、为什么、自己做什么、不能据此得出什么。解释后让听者复述，记录一个误解并修订。

G. 中译英情境表达

1. 我换成通俗的话来说：首先会制作一个固定副本。
2. 换句话说，校验值检查文件是否变化，而不是每项事实是否正确。
3. 可以把字段映射想成把两张表的栏目对应起来。
4. 首先发生的是复制和检查数据包。
5. 你不需要运行检查；项目团队会运行。
6. 重要限制是，自动警告不等于事实判断。

---

解释一个自己熟悉的流程

选择不涉及敏感信息的工作或生活流程，写five steps / listener action / three limits / one analogy。删掉无法解释的缩写。

请外行反向复述

只听你的说明后，让对方回答：原件是否改变、谁做后台动作、自动结果能证明什么。误答处说明解释仍不够清楚。

三天后的复测

不用原稿，重新录90秒说明。检查是否为了流畅删掉限定性关系从句或“不保证”句。

---

• 我能把专业说明拆成过程、目的、行动者和限制。
• 我能用复杂被动保留顺序与对象范围。
• 我不会把自动检查说成自动判断或自动修复。
• 我会给类比加上停止点。
• 我完成了五步说明、反向复述和三天后复测。