Back to Details

meaning-preserving-rewrite

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Meaning-preserving rewrite

保留原意的改写

Outcome

预期结果

Rewrite policies, plans, standards, notes, reports, and templates in clear prose without dropping, weakening, broadening, or hiding a rule or decision.
以清晰的文笔改写政策、计划、标准、笔记、报告和模板，不得遗漏、弱化、扩大或隐藏任何规则或决策。

Trigger and boundary

触发条件与适用边界

Use when a user asks for simpler policy or plan wording, a governed artifact needs a stated voice, shortening must preserve every clause, or a package needs a baseline, ledger, rewrite, and proof.
Do not use for ordinary code refactors, routine summaries with permission to omit detail, or one-off creative copy.
当用户要求简化政策或计划的措辞、受控文档需要统一表述风格、精简内容必须保留所有条款，或者需要为某个包提供基线、台账、改写及验证时使用。
不得用于普通代码重构、允许省略细节的常规摘要，或一次性创意文案撰写。

Required composition

必要前置准备

Read dependency reconciliation before work that also changes a skill package or depends on a host writing policy. This skill owns clause-level meaning and voice. A package simplification peer owns package modes and decomposition when one is installed.
If no equivalent owner exists, keep the package boundary unchanged. Do not invent a missing dependency or weaken a branch to avoid it.
在修改技能包或依赖宿主撰写政策的工作开始前，请阅读dependency reconciliation。本技能负责条款层面的含义与表述风格。当安装了包简化工具时，包简化同行负责包的模式与分解。
若没有对应的负责人，请保持包的边界不变。不得为规避依赖而凭空创建缺失的依赖或弱化分支。

Writing standard

写作标准

  • Start with the result or rule.
  • Use common words, active voice, and natural contractions.
  • Keep one rule per bullet when possible.
  • Name the owner, file, command, count, or check.
  • Define a technical term on first use.
  • Preserve exact paths, commands, hashes, setting names, source quotes, backups, and raw output.
  • Keep requirement strength explicit with 
    must
    , 
    must not
    , 
    may
    , or 
    prefer
    .
  • Keep exceptions as narrow as their sources.
  • Do not depend on prior conversation context.
  • Avoid em and en dash characters, filler, hedges, and polished closers.
  • Keep readable spacing between headings, paragraphs, and lists.
  • Put always-needed rules in the parent file. Move branch detail only to an owner-appropriate linked file with a backlink.
  • Keep each governed Markdown file below its host limits. Never remove readable spacing only to pass a size limit.
Read voice checks before the final prose scan.
  • 以结果或规则开篇。
  • 使用常用词汇、主动语态和自然的缩写形式。
  • 尽可能每条项目符号对应一条规则。
  • 明确负责人、文件、命令、数量或检查项。
  • 首次使用技术术语时给出定义。
  • 保留精确的路径、命令、哈希值、设置名称、原文引用、备份文件和原始输出。
  • 使用
    must
    、
    must not
    、
    may
    或
    prefer
    明确要求的强度。
  • 保持例外情况与其来源的范围一致。
  • 不依赖之前的对话上下文。
  • 避免使用破折号、填充语、模糊表述和冗余结尾。
  • 在标题、段落和列表之间保留易读的间距。
  • 将必备规则放在父文件中。仅将分支细节移至负责人对应的关联文件，并添加反向链接。
  • 确保每个受控Markdown文件不超过宿主限制。不得仅为通过大小限制而删除易读间距。
在最终文本检查前，请阅读voice checks。

Procedure

操作流程

1. Capture the baseline

1. 捕获基线

  1. Read the live sources instead of reconstructing them from memory.
  2. Record each present source path, hash, bytes, lines, headings, and mode.
  3. Mark a future path absent instead of inventing its hash.
  4. Copy each live target to an owner-only backup and prove byte identity.
  5. Record source and repository state when their behavior affects the rewrite.
  6. Stop on unexplained source drift.
Use the baseline and ledger contract for fields and checks.
  1. 读取实时源文件，而非凭记忆重构。
  2. 记录每个现有源文件的路径、哈希值、字节数、行数、标题和模式。
  3. 标记未来路径为缺失，而非凭空生成其哈希值。
  4. 将每个实时目标文件复制到仅负责人可见的备份，并验证字节级一致性。
  5. 当源文件和仓库状态会影响改写时，记录其状态。
  6. 若出现无法解释的源文件漂移，立即停止操作。
使用the baseline and ledger contract进行字段检查。

2. Build the meaning ledger

2. 构建含义台账

Give every source clause a stable ID. Split a paragraph when it contains several rules.
For each clause record the source, exact text, meaning, requirement strength, destination, replacement, action, and review state. Allowed actions are 
keep
, 
split
, 
move
, and 
clarify
. Never use 
drop
.
Add each new voice rule and the rule that the same voice applies to every planned artifact. Keep map and tuple shapes consistent in generated ledgers.
为每个源条款分配稳定的ID。若段落包含多条规则，将其拆分。
为每个条款记录来源、精确文本、含义、要求强度、目标位置、替代文本、操作和审核状态。允许的操作包括
keep
（保留）、
split
（拆分）、
move
（移动）和
clarify
（澄清）。禁止使用
drop
（删除）。
添加每条新的表述风格规则，以及同一风格适用于所有待处理文档的规则。确保生成的台账中映射和元组格式一致。

3. Check current sources

3. 检查当前源文件

When a rewrite claims complete official documentation or primitive coverage, inventory the current official source set before writing. Do not trust a stale snapshot or invent a page. Follow the documentation inventory contract.
当改写工作声称覆盖完整官方文档或基础内容时，在撰写前清点当前官方源文件集。不得依赖过时快照或凭空创建页面。遵循the documentation inventory contract。

4. Rewrite

4. 执行改写

  1. Preserve every accepted meaning and its requirement strength.
  2. Keep always-needed rules in the parent artifact.
  3. Move branch-specific detail only to an owner-appropriate linked file.
  4. Keep one canonical owner for each procedure.
  5. Update ledger targets after every wording or section change.
  6. Diff live files against backups and tie each material block to ledger IDs.
  1. 保留所有已确认的含义及其要求强度。
  2. 将必备规则保留在父文档中。
  3. 仅将分支特定细节移至负责人对应的关联文件。
  4. 为每个流程指定唯一的规范负责人。
  5. 每次修改措辞或章节后更新台账目标。
  6. 对比实时文件与备份文件，将每个重要块与台账ID关联。

5. Validate

5. 验证

Check all of these:
  • Complete ledger coverage, unique IDs, allowed actions, approved review states, and exact target presence.
  • Line and character limits, links, context loading, hashes, modes, and secret safety.
  • Voice on prose only. Skip exact quotes, backups, raw output, inline code, and code fences that must remain exact.
  • Clear grammar on a full readback.
  • Agreement between human and machine reports.
  • Separate component result and whole-change status.
Never run a global contraction or punctuation replacement across mixed prose and code. Patch the exact prose occurrence, then recheck nearby code and syntax.
Temporary verifiers belong in an operating-system temp location and must be deleted after use. Label a focused probe as ad hoc rather than suite green.
Use the validation contract for review packets and closeout. If waiting for a separate reviewer would stop authorized main work and no external rule requires one, run the same checks in the main worker and label the result non-independent.
检查以下所有项：
  • 台账覆盖完整、ID唯一、操作合规、审核状态已批准、目标文件存在且精确。
  • 行数和字符数限制、链接、上下文加载、哈希值、模式和机密安全性。
  • 仅检查文本的表述风格。跳过必须保持精确的原文引用、备份文件、原始输出、行内代码和代码块。
  • 通读时语法清晰。
  • 人工报告与机器报告一致。
  • 组件结果与整体变更状态分离。
不得对混合文本和代码的文件执行全局缩写或标点替换。仅修改精确的文本部分，然后重新检查附近的代码和语法。
临时验证工具应放在操作系统临时目录中，使用后必须删除。将聚焦式探测标记为临时而非套件通过。
使用the validation contract处理审核包和收尾工作。若等待独立审核人会阻碍已授权的主要工作，且无外部规则要求独立审核，则由主执行者执行相同检查，并标记结果为非独立。

Proof threshold

验证阈值

Return 
PASS
only when:
  • Every source clause has an approved mapping and no action is 
    drop
    .
  • Every replacement keeps the source meaning, scope, exception, and strength.
  • Baseline and backup hashes still match.
  • Every linked target exists and matches the ledger.
  • Voice, grammar, security, and package checks pass.
  • A component result is not presented as whole-change proof.
  • Temporary verification files are gone.
Use 
PARTIAL
when bounded component proof passes but the whole threshold is incomplete. Use 
BLOCKED
when source drift, missing authority, inaccessible evidence, or an unresolved dependency prevents a safe rewrite.
仅当满足以下所有条件时返回
PASS
：
  • 每个源条款均有已批准的映射，且无
    drop
    操作。
  • 每个替代文本均保留源文件的含义、范围、例外和强度。
  • 基线与备份的哈希值仍匹配。
  • 每个关联目标文件均存在且与台账一致。
  • 表述风格、语法、安全性和包检查均通过。
  • 未将组件结果作为整体变更的验证依据。
  • 临时验证文件已删除。
当有限的组件验证通过但整体阈值未达标时，返回
PARTIAL
。当源文件漂移、权限不足、证据不可访问或依赖未解决导致无法安全改写时，返回
BLOCKED
。

Common failures

常见失败案例

  • Hashing a path that does not exist yet.
  • Omitting a source bullet or narrow exception.
  • Replacing an exact rule with a vague summary.
  • Leaving stale ledger text after a wording fix.
  • Scanning checker data or inline code as prose.
  • Corrupting code examples through whole-file cleanup.
  • Reporting a component PASS as whole-change PASS.
  • Claiming independent review when the main worker performed it.
  • Leaving temporary builders or stale review packets.
  • 对尚未存在的路径计算哈希值。
  • 遗漏源文件中的项目符号或窄范围例外。
  • 用模糊摘要替代精确规则。
  • 修改措辞后未更新台账中的过时文本。
  • 将检查器数据或行内代码当作文本扫描。
  • 通过全文件清理破坏代码示例。
  • 将组件的
    PASS
    报告为整体变更的
    PASS
    。
  • 当主执行者执行审核时，声称是独立审核。
  • 遗留临时构建工具或过时审核包。

Package resources

包资源

Use 
assets/meaning-ledger-template.json
as a field template. Read 
examples/policy-rewrite.md
, 
examples/blocked-drift.md
, or 
examples/package-reconciliation.md
for visible runs. Package maintainers use 
references/
, 
scripts/
, 
scripts/tests/
, and 
evals/
, then run 
mise run ci
; ordinary rewrites do not load those paths.
使用
assets/meaning-ledger-template.json
作为字段模板。参考
examples/policy-rewrite.md
、
examples/blocked-drift.md
或
examples/package-reconciliation.md
查看实际运行案例。包维护者使用
references/
、
scripts/
、
scripts/tests/
和
evals/
，然后运行
mise run ci
；普通改写无需加载这些路径。