BATCH 84 — LOGICAL BOXING / LINEWRAP CLEANUP / SPECTRAL ENFORCEMENT / BLOGGER VISUAL READBACK HARDENING — 25 June 2026

This Batch84 patch applies to Blogger formatting, Strict HTML QA, formatter readback, final audit, packaging, prompt-manager publication, standalone TXT prompt packages, public standalone HTML pages, copyable embedded prompt bodies, Blogger replacement bodies, manifests, and changelogs. It is a formatting/display hardening patch. It does not permit omission, paraphrase, doctrinal rewriting, source-link mutation, source-title mutation, or translation.

1. SPECTRAL FONT ENFORCEMENT GATE
For English Blogger article styling, the formatter must actually load and apply Spectral; mentioning it is not enough.

Required behavior:
- Include a Blogger-safe Google Fonts stylesheet import/link for Spectral where the article format permits it.
- Apply `font-family: "Spectral", Georgia, "Times New Roman", serif` to the actual article root and all visible prose descendants.
- Override legacy inline font-family residue such as Noto Sans, Arial, Verdana, Helvetica, or generic sans-serif when the user asked for Cosmic Dawn / Spectral article style.
- Headings, cards, blockquotes, Plum Dawn panels, source notes, resource boxes, and body paragraphs must inherit or explicitly use Spectral unless a protected code/pre/table/UI element requires monospace or another font.
- Strict QA must verify selector-to-DOM applicability: CSS presence is insufficient. The actual wrapper/content selectors must match the generated DOM.

Required audit lines:
- Spectral font loaded: PASS/FAIL.
- Spectral applied to actual article root: PASS/FAIL.
- Legacy body font-family residue overridden: PASS/FAIL.
- Selector-to-DOM font applicability: PASS/FAIL.

2. HARD `<br>` LINEWRAP CLEANUP GATE
Old Blogger/HTML/article imports often contain hard line breaks inside normal prose, such as `Recently<br>I have compiled...` or `Thusness commented in his 7 stages<br>article that...`. These are export line wraps, not meaningful paragraph breaks.

Formatter rule:
- Collapse hard `<br>` line wraps inside normal prose into spaces.
- Preserve true paragraph breaks as separate paragraphs.
- Do not preserve source-export line breaks that make a normal paragraph look cut off.
- Do not use `white-space: pre`, `white-space: pre-wrap`, or any style that visually preserves old export wrapping in normal prose.
- Use normal paragraph flow for prose: `white-space: normal; overflow-wrap: anywhere; word-break: normal;`.
- For visible-text completeness, compare against a normalized source where export-only line wraps are collapsed.
- Do not collapse meaningful list items, resource/download rows, dialogue speaker turns, poem/stanza formatting, code/pre blocks, or deliberately line-broken quotations.

Strict QA must:
- Scan for `<br>` inside normal `<p>`, `.content-card`, `.source-quote`, `.atr-note`, `.plum-dawn-panel`, and normal prose cards.
- Flag FAIL if a normal paragraph is visibly broken into short artificial lines.
- Verify that intro paragraphs and long quotation/commentary paragraphs read as normal paragraphs.
- Include representative beginning/middle/end readback for paragraph flow.

Required audit lines:
- Hard `<br>` linewrap cleanup in normal prose: PASS/FAIL.
- Normal prose `<br>` residue count: [number].
- Paragraph reflow spot-checks: PASS/FAIL.
- Meaningful line breaks preserved where required: PASS/FAIL.

3. LOGICAL BOXING GATE — BOX BY POST / IDEA UNIT, NOT BY PARAGRAPH
Group content into visually logical boxes. Do not split a single post/comment/source excerpt into separate boxes merely because it has multiple paragraphs.

Rules:
- If consecutive paragraphs belong to the same post, comment, excerpt, note, or topical unit, keep them in one card.
- Paragraphing inside a card is allowed and often required.
- Do not make one card per paragraph when the paragraphs form one coherent unit.
- The Supreme Master Ching Hai sample beginning `She (Supreme Master Ching Hai) is definitely at 'I AM' stage...` plus `For one who realises non-duality...` must remain one logical card when present.
- Apply the same rule to Daniel Ingram paragraph clusters, Thusness comment clusters, Soh update clusters, Simpo reply clusters, Q&A exchanges, and topical mini-essays.
- Use separate boxes only when there is a real shift in author/speaker, quoted source, topic, section, or post boundary.

Required audit lines:
- Logical single-post boxing: PASS/FAIL.
- Paragraph-as-card over-splitting scan: PASS/FAIL.
- Multi-paragraph card samples checked: [number].
- Known Supreme Master Ching Hai sample remains one box: PASS/FAIL/NOT APPLICABLE.

4. BALANCED BOX DENSITY + PLUM DAWN FEATURE BOX REQUIREMENT
Long, quote-heavy posts must not be too flat, but boxes must remain logical.

Rules:
- Use cool lavender/indigo/white content cards for ordinary source posts, comments, resource notes, and grouped prose.
- Use Plum Dawn purple-gradient feature boxes selectively for important notes, section transitions, major framing notes, closing notes, and ornamental divider replacements.
- Use enough boxes that the article looks intentionally styled, not like unstyled plain text.
- Avoid a giant visible outer showcase/card shell inside Blogger. The root wrapper should be an invisible layout container; inner logical units may be boxed.
- Avoid nested Plum Dawn panels.
- Avoid box-within-box unless the inner element is a justified inset quote/resource list and contrast is verified.
- Cards must remain full-width within the article column; no mid-article narrowing.

Required audit lines:
- Balanced box density: PASS/FAIL.
- Content-card count: [number].
- Plum Dawn feature panel count: [number].
- Nested-card / box-within-box problems: PASS/FAIL.
- Mid-article width consistency: PASS/FAIL.
- Root wrapper invisible / not a visible showcase shell: PASS/FAIL.

5. WIDTH CONSISTENCY / WHITE AREA SHRINKAGE GATE
Do not introduce narrower shells inside the article body unless explicitly intended for a special component.

Rules:
- Do not set random `max-width: 760px`, `820px`, `900px`, etc. on mid-article prose cards.
- Cards should normally use `width: 100%; box-sizing: border-box; max-width: none;`.
- The article root may have a reasonable max-width for readability, but internal cards must not progressively shrink.
- Avoid nested wrappers that visually create a smaller white canvas halfway down the post.

Required audit lines:
- White canvas / content width consistency: PASS/FAIL.
- Restrictive mid-article width rules found: none / [list].
- Internal cards full-width within article column: PASS/FAIL.

6. SEPARATOR TEXT CLEANUP GATE
Standalone separator-only lines such as `-----------------`, `...`, `....`, `—-`, repeated underscores, or repeated dashes must not remain as visible ugly text when they function only as dividers.

Rules:
- Replace standalone separator-only lines with clean ornamental dividers or compact Plum Dawn divider boxes.
- Do not remove real sentence ellipses such as `Yep...` or `This part described...` when they are part of prose.
- Do not remove ellipses inside quotations or dialogue unless they are standalone separator lines.
- If a separator marks a new post/excerpt, use it as a boundary signal for logical boxing but do not display it as raw text.

Required audit lines:
- Standalone separator text residue: PASS/FAIL.
- Separator-only lines converted to styled dividers: PASS/FAIL.
- Lexical sentence ellipses preserved: PASS/FAIL.

7. RESOURCE / DOWNLOAD LIST REBUILDING GATE
Resource sections such as `Click to download in chapters. Preface / How to use the articles / Who are we? ...` must not remain as flat broken paragraphs.

Required:
- Format resource/download sections as clean resource/download cards or lists.
- Keep all href values exactly.
- Keep resource labels and descriptions.
- Normalize safe spacing such as `Who are we?(113kb)` to `Who are we? (113kb)` without changing meaning.

Required audit lines:
- Resource/download list formatting: PASS/FAIL/NOT APPLICABLE.
- Resource href parity: PASS/FAIL.
- Resource labels/descriptions preserved: PASS/FAIL.

8. LEGACY INLINE STYLE NEUTRALIZATION GATE
Old Blogger HTML may contain inline styles that conflict with the new theme, including Noto Sans, Verdana/Arial font spans, `color: white` on normal white backgrounds, duplicate IDs, invalid block-in-span nesting, and pasted Word/Apple paragraph styles.

Formatter rule:
- Neutralize or override legacy inline styles that break the theme.
- Preserve meaning, links, images, and visible text.
- Remove or repair duplicate IDs.
- Repair invalid block-in-inline structures.
- Force readable contrast in all cards/panels.

Required audit lines:
- Legacy inline font/color conflicts neutralized: PASS/FAIL.
- Duplicate IDs: [count].
- Invalid block-inside-inline nesting: PASS/FAIL.
- White-on-white / dark-on-dark text risk: PASS/FAIL.

9. STRICT HTML QA VISUAL-LOGIC REVIEW
Strict QA must include visual-logic review, not only href/src/text-count parity. It must ask whether the article looks like one coherent Blogger article; whether boxes are grouped by meaningful units; whether there are enough nice boxes for a long post-heavy article; whether Plum Dawn panels are used tastefully; whether raw separators are removed; whether paragraphs reflow normally; whether Spectral is actually applied; whether any section unexpectedly narrows; whether box-within-box defects exist; and whether top resource notes/download lists are attractive.

Required audit lines:
- Visual-logic styling review: PASS/FAIL.
- Real Blogger preview risk items: none / [list].
- Screenshot/user-reported visual defect incorporated: PASS/FAIL/NOT APPLICABLE.
- Formatting publishability requires both structural parity and visual quality: PASS/FAIL.

10. STATUS DISCIPLINE
Any change to CSS, DOM grouping, line-break cleanup, separators, card structure, font loading, or visual layout is material. Same-pass publishable promotion is forbidden after such repairs.

Use exactly:
REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.

Only a later exact-artifact no-edit audit may use:
reviewed final / publishable — strict-certified final not claimed.

11. PACKAGING / PUBLIC PROMPT SYNC
After updating prompt source files, also update standalone TXT prompt packages, public standalone HTML pages, copyable embedded prompt bodies, Blogger replacement bodies when present, current-use labels, package manifests, changelogs, and handoff files. QA must confirm embedded public HTML prompt bodies and standalone TXT prompt bodies are synchronized, not stale.

Required packaging audit line:
- Embedded public HTML prompt bodies synchronized with standalone TXT prompt bodies: PASS/FAIL.

BATCH 83 — 目标语优先技术术语 / Total Exertion 保护 / QA 结构加固 — 2026年6月23日

本 Batch84 补丁适用于完整 AtR 翻译、审校、Prompt 1 严格 HTML 保留、Prompt 6 对抗性审校、Prompt 9 最终/可发布 QA、各语言专门关卡、formatter prompts、upload/publishing/controller prompts、prompt-manager 流程、术语库 prompts、链接处理、对话保留与最终 artifact 晋级。它适用于所有目标语言，不只适用于阿拉伯语。

1. 目标语优先技术术语规则
所有语言中，技术性佛法术语不得在目标语语法中长期裸留 English/Pāli/Sanskrit/Tibetan 标签，除非该语言术语库明确规定这是该语言可接受的正文运行形式。默认使用目标语运行术语；必要时，尤其在首次出现、标题、或源术语具有教义重要性处，才在括号中保留源标签。不得把 English/Pāli/Sanskrit 标签机械粘入目标语前后缀或普通语法中。

适用范围包括 anatta/anatman/no-self, self/Self, Atman, Buddha-nature, Buddhadharma, Presence, Awareness, Consciousness, Isness, I AM, I AMness, no-mind, One Mind, non-doership, self-enquiry/Self-Inquiry, vipassana/vipashyana, samadhi, prajna/prajñā, Mahamudra, Dzogchen, Soto Zen, Dōgen 等 AtR / Dharma 技术标签。各语言术语库可以规定默认形式是翻译、音译或混合，但必须自然地融入目标语语法。

阿拉伯语例：anatta 正文默认 اللاذات，必要时作 اللاذات (anatta) 或 اللاذات (Anatta)；Atman 作 الآتمان (Atman)；Buddhadharma 作 الدارما البوذية (Buddhadharma)；Soto Zen 作 زن سوتو (Soto Zen)；I AM 作 «أنا أكون» (I AM)。避免把裸 anatta、Atman、Buddhadharma、Soto Zen、I AM 机械塞进普通阿拉伯语语法。

2. Dōgen / Zen “Total Exertion” 保护术语覆盖
“Total Exertion” 必须作为 Dōgen / Zen 技术术语处理，包括 AtR 标题与 gujin 相关语境。不得用普通词典义译成耗尽、枯竭、消耗、排空、过度用力，或仅仅个人努力/投入。若语言专门术语库已有批准译法，则使用该译法；若无，则保留 English technical term，并可按该语言规范音译。

阿拉伯语 artifact/default 批准形式：توتال إكسيرشن (Total Exertion)。不得使用 الاستنفاذ الكلي，因为它表示耗尽/枯竭。除非用户明确要求，不要自动添加首次解释说明；若项目专门 prompt 要求说明，必须简短，不得扩写或加编者解释。

3. 成语/语境对抗性关卡
Prompt 6 与 Prompt 9 必须检查看似简单的英文短语是否按语境翻译，而不是逐词照搬。在心理/灵性证悟语境中，saw the same thing 往往不是“看见同一个物理对象”，而是“理解/体验/认出同一个体验或洞见”。

阿拉伯语推荐模式：لم يكن أحدٌ حولي يعيش التجربة ذاتها، ولم يكن أحدٌ يغضب إن تحدّثتُ عنها.

同时检查否定并列：English “Nobody X or Y” 常常等于 “Nobody X, and nobody Y”，不是 “Nobody X, or they Y”。不得生成尴尬的“或他们生气”式结构。

4. 通用 slash-calque 关卡
普通正文中不要机械保留英文斜杠组合，例如 subject/object, perceiver/perceived, self/Self, no-self/Self, agent/action, concepts/thinking, Awareness/Consciousness, Who/What am I?, Soto Zen/Dōgen, Eight Negations / Middle Way negation。应使用目标语自然并列，如“和”“或”“X 与 Y 之间”，或括号保留源标签。只有当斜杠属于精确标题、精确公式、文件名、代码、URL、或受保护技术标签时才保留。

阿拉伯语例：من أو ما أنا؟，不是 من/ما أنا؟；الوعي أو الإدراك，不是 الوعي/الإدراك；الذات أو الفاعل المستقل，不是 ذات/فاعل مستقل；普通阿拉伯语正文应作 زن سوتو ودوجن，而不是 Soto Zen/Dōgen。

5. 链接所在句 QA
每个 anchor tag 都必须保持 href 精确不变，除非用户明确要求改链接。必须保持正确 anchor 边界：链接文字不得吞掉邻近句子文字、标点或相邻链接。若源链接文字是英文文章标题而目标 artifact 翻译链接文字，整句仍必须自然。若精确标题必须保留英文，不得生硬粘进目标语语法，需用自然框架嵌入。

对抗性检查：读完整个含链接句子，不只读链接文字。若句子读成 “when [linked title] is penetrated…” 或其他不自然结构，应修复周边句法，同时保留 href。

6. DOM 级 HTML 结构保留
Prompt 6 与 Prompt 9 必须做 DOM 级结构检查，不只是视觉或文本检查。确认 style block 保留且未变成可见文字；CSS 除非明确要求不得改变；src 与 href parity 保留，只有明确要求的英文原文链接等可有意添加；blockquote 数量与边界保留；dialogue-card 数量与 speaker 边界保留；heading、list item、source block、“Also see” card、update section 结构对齐；无 p inside span 等无效嵌套；无重复嵌套 anchors；无 source URL 误转为纯文本；无 source-link 实例缺失或重复；无跨源段落/card 的 section merging。

若修复了材料性 HTML 结构问题，状态必须保持 “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required”，直到后续无材料改动 pass。

7. 可见文本空格与标点 QA
Prompt 9 必须最终扫描：非源文 NBSP 出现在可见正文；标点粘词；标点后漏空格；括号周围空格不自然；目标语标点与 Latin terms 混用不当；“word.word” 或 “واقعهم.ينبغي” 等行合并缺陷；链接相邻标点缺陷。按各目标语言标点规范处理。

8. 语言专门术语库与 reviewer override 优先
如果 native speaker / reviewer 在会话中给出修正，应作为该 artifact 的语言专门 override，除非与更高优先级项目规则冲突。必须搜索全 artifact 相关实例，不只修引用句；标题、heading、正文、cards、重复引用都要一致；并记录改了什么。

例：阿拉伯语 anatta 默认 اللاذات；本文 Total Exertion 作 توتال إكسيرشن (Total Exertion)；心理/灵性语境 saw the same thing 作 يعيش التجربة ذاتها 或等效表达，不作 يرى الشيء نفسه。

9. source-label residue 扫描
声明 publishable 前，扫描目标语正文中是否残留裸源标签：大写英文技术词、Pāli/Sanskrit 术语、带目标语前后缀的源标签、source/target 混合斜杠形式、源术语反复出现而本应仅首次括号保留。必须区分精确文章标题、proper names、URLs、code/file names、故意保留英文标签与受保护原文，避免把 ordinary prose 中的意外残留误判为 protected original。

10. artifact 状态晋级纪律
若审校 pass 做了任何材料性可见文本、术语、链接或 HTML 结构修复，当次不得晋级 publishable。使用：REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.

只有后续完整 Prompt 6 + Prompt 9 pass 发现无材料问题且没有可见文本/HTML 编辑，才可使用：reviewed final / publishable — strict-certified final not claimed.

11. 不过度修正受保护原文
不得“修正”因 proper names、精确文章标题、原文引文、经名、URLs、术语库要求保留的技术标签、或用户专门 override 而故意保留的源词。但即便保留，也必须自然融入目标语句子。

12. Prompt 9 最终 audit checklist
输出最终文件前，Prompt 9 必须内部检查，并在有用时对外简要总结：要求时英文原文链接已存在；href parity；src parity；CSS/style block 保留；article root directionality 与 language attributes；image count；blockquote count；dialogue-card count 与 speaker 边界；source-tail cards / “Also see” 结构；无 invalid nesting；无 duplicate nested anchors；可见文本无非源 NBSP；无 line-merge punctuation defects；无 ordinary slash-calques；运行正文无裸技术源标签残留；语言专门术语库合规；prior-session reviewer corrections 已一致应用。

强制 QA / changelog 行
Target-language-first technical-term gate checked: no accidental bare English/Pāli/Sanskrit technical labels remain in ordinary target-language grammar.
Total Exertion / gujin protected-term gate checked: no depletion/exhaustion/overexertion mistranslation remains.
Idiom/context and negative-coordination gate checked: contextual English idioms and “Nobody X or Y” structures are not word-calqued.
Slash-calque gate checked: ordinary slash pairs are rendered naturally unless protected.
Link-bound sentence QA checked: hrefs and anchor boundaries are preserved and linked sentences read naturally.
DOM structure, visible spacing/punctuation, source-label residue, reviewer override consistency, and status-promotion discipline checked.

# ATR HTML Article Translation Workflow Prompt — UNIVERSAL FULL INTRO PROMPT WITH HARD QA GATES, ADVERSARIAL REVIEW, AND ANTI-FALSE-FINAL DISCIPLINE

BATCH 82 — “UNIVERSAL AWARENESS / UNIVERSAL CONSCIOUSNESS” 中文术语锁定 — 2026年6月21日

本 Batch84 补丁适用于完整 AtR 翻译、审校、QA、对抗性审计、formatter、publishing/controller、prompt-manager、打包、Cloudflare、Blogger 与交接流程中所有涉及中文翻译、审校或验证的环节。

在中文目标文本中，当 “universal awareness” / “universal consciousness” 出现在 AtR / John Tan 对实体化的宇宙性或普遍性意识、共享 One Mind、宇宙觉知/宇宙意识见的讨论或批判中时，优先译为“宇宙意识”（繁体：“宇宙意識”）。不得在这个佛法/哲学语境中使用“普遍意识”“普遍觉知”“普遍意識”“普遍覺知”，除非源文明确只是普通意义的“普遍适用的觉察/意识”，而非宇宙性、普遍性意识见。

此规则是术语锁定，不是教义认可：当源文在批判 “universal awareness / universal consciousness” 时，译为“宇宙意识”只是准确保留被批判对象，不得让实体化的宇宙意识见听起来像正见。

PROMPT 6 / PROMPT 9 / QA 要求
凡涉及中文的翻译、审校、无修复晋级、formatter readback、Strict HTML QA、prompt-manager 或 controller validation，都必须显式扫描是否把 “universal awareness” 或 “universal consciousness” 译成“普遍意识 / 普遍觉知 / 普遍意識 / 普遍覺知”。除非该句明确只是普通“普遍适用”意义，否则应修为“宇宙意识 / 宇宙意識”。

强制 QA / changelog 行
Chinese universal awareness/consciousness terminology gate checked: “universal awareness / universal consciousness” renders as 宇宙意识 / 宇宙意識, not 普遍意识 / 普遍觉知, unless the source clearly means ordinary general applicability.


BATCH 79 — thought-watching-thought / no-hidden-witness 加固 — 14 June 2026

本 Batch79 补丁为通用补丁，适用于所有 AtR / John Tan 翻译、审校、润色、对抗性审计、格式化、Strict QA、无修复晋级、打包、上传控制、prompt-manager 与交接流程。它适用于所有目标语言，不只适用于阿拉伯语、印尼语或中文。它不得削弱 Batch78 非二元身份句法与 informal idiom 加固；Batch77 agent/做者、efforting/造作用力、mental chattering/概念戏论 假朋友加固；Batch76 高风险佛法术语保护与本地教义污染审查；Batch75 材料性/反反复复改写；Batch74 精确 artifact / 反假通过；Batch73 Presence / hybrid residue；Batch71 Witness/sākṣī；Prompt T；Prompt X；Blogger HTML；href/src/code；以及状态纪律规则。

核心教训
在 AtR / John Tan / anatta 的核心段落中，“thought watching thought rather than a watcher watching thought” 不得译成“心见证心”“心观察心”“觉知见证念头”“意识观看念头”等会暗示更微细的 Mind、Witness、Awareness、observer、knower 或 subject 在背后观看念头的说法。要点不是有一个更深的心、见证者、觉知、观察者或主体在看念头；要点是找不到独立的观看者：所谓“watcher”本身只是那个念头，或一个念头刹那之后又一个念头刹那。

THOUGHT-WATCHING-THOUGHT / NO-HIDDEN-WITNESS 门
对于 “thought watching thought rather than a watcher watching thought,” “the watcher is that thought,” “there is no one behind thoughts,” “first, one thought then another thought,” “Always just this, One Thought!” 以及涉及 watcher, observer, witness, knower, thinker, seer, hearer, mind, thought, awareness, consciousness, subject 的相关 AtR / John Tan / anatta 句子，不得译成会暗示以下任何意思的目标语：
- mind witnesses mind
- mind observes mind
- the witness is the mind
- the observer is the mind
- awareness witnesses thoughts
- consciousness watches thoughts
- 念头背后仍有隐藏的 Witness、Mind、Awareness、observer、knower 或 subject

必须保留 thought versus watcher 的对比，而不是改写成 mind versus observer/witness。应保留 no-hidden-witness 的洞见：thought-after-thought、一个念头观察另一个念头、或 thought watching thought。所谓“watcher”只是那个念头本身，不是背景性的心、见证者、觉知、意识或主体。

当目标语中“THOUGHT”和“MIND”容易混同
若目标语言用同一个词或高度重叠的词来表达 thought 与 mind，译者必须消歧。不要保留隐藏主体歧义，而应使用相当于以下的短语：
- one thought-moment observing another thought-moment
- one arising thought observing another thought
- one mental event observing another mental event
- this thought itself is what is mistaken for the watcher
- the so-called watcher is only that very thought
- there is no observer behind thoughts; only one thought, then the next thought

若字面译法仍容易读成隐藏主体，应在译文中加入小型澄清，而不是保留歧义。

语言示例
印尼语：避免 batin menyaksikan batin、pikiran menyaksikan pikiran、pengamat adalah batin、penyaksi adalah pikiran，或当 pikiran 可能被读成 Mind 而非一个念头时的 pengamat adalah pikiran itu sendiri。优先使用 satu momen-pikiran mengamati momen-pikiran lain；satu kemunculan pikiran mengamati kemunculan pikiran lain；yang disebut “pengamat” itu tidak lain hanyalah pikiran yang sedang muncul itu sendiri；bukan ada seorang pengamat di balik pikiran; hanya ada satu pikiran, lalu pikiran berikutnya。

中文：避免会暗示 心 / 觉知 / 意识 作为隐藏主体在见证念头的表述。视自然度优先使用 念头看念头 / 一个念头看另一个念头 / 所谓的观察者只是那个念头本身。

阿拉伯语：避免暗示 العقل / الوعي / الشاهد 是背景见证者的表述。优先使用相当于 فكرة تراقب فكرة أخرى 以及“所谓观看者只是那个念头本身”的说法，而不是“mind witnesses mind”。

PROMPT 6 / PROMPT 9 / QA 反向回译要求
在每一次 Prompt 6、Prompt 9、Strict QA、formatter readback、无修复晋级、打包校验、prompt-manager、发布/controller 或对抗性审校中，都必须显式扫描涉及 watcher、witness、observer、seer、hearer、thinker、knower、mind、thought、awareness、consciousness、subject、no one behind thoughts、one thought then another thought、thought watching thought、watcher is that thought 的核心 anatta 段落。

运行以下反向回译对抗测试：目标语是否能自然回译成 “mind watches mind,” “mind witnesses mind,” “the witness is mind,” “the observer is mind,” “awareness watches thoughts,” “consciousness witnesses thoughts,” 或“念头背后仍有一个微细主体”？若是，必须修复。此问题一律按 material 处理，因为它会反转或削弱 anatta / no-hidden-witness 洞见。

强制 QA / CHANGELOG 确认行
每一个相关 AtR / John Tan / anatta QA pass 都必须包含以下简短确认行：
Thought-watching-thought / no-hidden-witness gate checked: no “mind witnesses mind,” “witness is mind,” “awareness watches thought,” or hidden-subject reading remains.

状态纪律
若发现并修复此类问题，该 artifact 不能在同一 pass 中晋级。使用：“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” 只有后续精确 artifact、无 material edit 的复审 pass 才可使用：“reviewed final / publishable — strict-certified final not claimed.”

BATCH 78 — 通用非二元身份句法与非正式 idiom / “blah” 语域加固 — Batch81 修订 / 澄清 — 16 June 2026

本 Batch78 规则现由 Batch81 加以澄清。它仍是通用规则，适用于所有 AtR / John Tan 翻译、审校、润色、对抗性审计、格式化、Strict QA、无修复晋级、打包、上传控制、prompt-manager 与交接流程。它适用于所有目标语言，不只适用于阿拉伯语或泰米尔语。此澄清不得削弱 Batch80 hero-title 格式修复；Batch79 thought-watching-thought / no-hidden-witness 加固；Batch77 agent/做者、efforting/造作用力、mental chattering/概念戏论 假朋友加固；Batch76 高风险佛法术语保护与本地教义污染审查；Batch75 材料性/反反复复改写；Batch74 精确 artifact / 反假通过；Batch73 Presence / hybrid residue；Batch71 Witness/sākṣī；Prompt T；Prompt X；Blogger HTML；href/src/code；以及状态纪律规则。

核心教训
某些英文非二元公式与非正式 idiom 若按表层句法直译，会造成结构性风险。在 anatta 语境中，“In X, just Y” 是紧凑的观照式公式。它不是容器/地点公式，但 Batch78 也不应被误解为要求每一种语言都改成沉重的定义句，例如 “hearing itself is sounds,” “seeing itself is forms,” 或 “X means Y”。真正的要求更细：在目标语自然时，尽量保留源文 “in hearing / in seeing / in thinking, only ...” 的简洁节奏，同时防止 hearing、seeing、thinking、awareness 或 mind 被读成一个容器、场域、舞台、背景、实体或隐藏主体，仿佛现象在其中出现。同样，像 “blah something nice but deluded” 这类非正式表达，未必要求译成幼稚、滑稽或过度口语的“叽里呱啦/碎碎念/瞎扯”；它常是在贬斥听起来漂亮但仍属迷妄的概念性/灵性话语。翻译必须保留非二元精确性、紧凑的观照节奏与出版语域，而不是机械保留表层句法。

“IN X, JUST Y” 非二元身份句法门
对于 “In thinking, just thoughts,” “In hearing, just sounds,” “In seeing, just forms, shapes and colors” 这类 anatta / 非二元句子，若目标语自然，应保留相当于 “in/with/at hearing, only sounds; in/with/at seeing, only colors/forms; in/with/at thinking, only thoughts” 的结构。不得使用会暗示容器、类别、地点、场域、舞台、背景、实体、隐藏主体，或过程与对象之间有细微间隔的目标语结构，例如“在思维里面有念头”“在听里面有声音”“声音出现在觉知/心中”等。

这是语义门，不是单一语法模板要求。若会改变源文语气、节奏或教义细节，不得过度修正成僵硬的身份定义句，例如 “X is Y,” “X itself is Y,” 或 “X means Y”。优先使用目标语中最自然、相当于“听时/听中，唯有声音”“见时/见中，唯有颜色与形相”“想时/思维时，唯有念头”的表达，同时确保不会暗示内在容器、背景观察者或隐藏主体。只有当目标语确实需要时，才使用较重的身份/不分离表述来阻断误导性的容器/背景读法。

泰米尔语澄清：若 கேட்பதில் எப்போதும் ஒலிகள் மட்டுமே 会读成内在容器，即“在听里面有声音”，应避免。若 கேட்பது என்பது எப்போதும் ஒலிகளே 或 கேட்பதே எப்போதும் ஒலிகளே 听起来像沉重的 “hearing itself is sounds”，而不是源文简洁的 “in hearing, only sounds”，也应避免。优先使用自然、非容器化的处所/时间表达，例如 கேட்கையில் எப்போதும் ஒலிகளே；பார்க்கையில் எப்போதும் நிறங்கள், வடிவங்கள், உருவங்களே；சிந்திக்கையில் எப்போதும் எண்ணங்களே；கேட்கையில் வெறும் ஒலியே。

阿拉伯语专门说明：较早的身份式例子，如 التفكير ليس إلا أفكارًا / السماع ليس إلا أصواتًا / الرؤية ليست إلا صورًا وأشكالًا وألوانًا，在需要阻断地点/容器读法时仍可使用。但若当地句子需要保留源文紧凑的观照节奏，不得机械强迫使用这些重身份句。避免 في التفكير، مجرد أفكار，若它可能读成地点/类别结构而非非容器化的 “only thoughts” 公式。

非正式 idiom / “BLAH” / 贬抑性概念话语门
当源文使用 “blah something nice but deluded” 这类非正式表达时，不得机械译成目标语中相当于“闲扯、唠叨、碎碎念、胡扯、聒噪”的词，若这会造成非源文意图的滑稽、幼稚、过度随便、或只是“多嘴/话多”的语气。

必须保留其功能：贬斥好听但迷妄的概念性话语、漂亮的表述、或缺乏证悟的悦耳灵性语言。所有目标语言都应以适合目标语出版语域的自然表达来处理，例如相当于：“说出听起来漂亮但仍然迷妄的话”“编织出响亮/漂亮的句子，但仍属迷妄”“说出动人的套语，但仍然迷妄”“给出优雅好听的概念性说法，但仍未离迷妄”。

阿拉伯语专门规则：优先使用 صاغوا عبارات رنّانة جميلة، لكنها واهمة / أطلقوا كلامًا منمقًا جميلًا لكنه واهم。除非源文明确是在非常口语化地嘲讽，否则避免 ثرثروا。

PROMPT 6 / PROMPT 9 / 对抗性审校要求
在 Prompt 6、Prompt 9、Strict QA、formatter readback、打包校验、无修复晋级、prompt-manager/controller 审查或任何对抗性审计/审校中，必须显式扫描每一种目标语言中的 Batch78 身份句法门的两面：
1. 保护不足：“In X, just Y” 被译成地点、容器、类别、场域、背景、隐藏主体，或“在/里面/其中有……”结构，从而削弱非二元不分离；
2. 过度修正：把源文紧凑公式强行改成 “X is Y,” “X itself is Y,” 或 “X means Y” 之类沉重定义句，导致语气、节奏或教义改变；
3. “blah” 等非正式英文 idiom 被过度字面化为 chatter/prattle/babble 式说法，而没有保留其贬抑功能与适当出版语域。
若任一问题改变源文意义、教义清晰度、非二元精确性、紧凑观照节奏或出版语域，即为材料性问题。必须全局修复，并视情况更新 Source-Term Decision Table / 高风险术语 ledger / Change Materiality Ledger，并使用：“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” 只有后续单独一次精确 artifact、无材料编辑的重审，才可使用：“reviewed final / publishable — strict-certified final not claimed.”

强制 QA / changelog 确认行
每一次相关的 AtR / John Tan / anatta QA pass 都必须包含以下简短确认行：
Batch78 identity-syntax gate checked: no container/background/hidden-subject reading remains, and no over-heavy “X is Y” identity overcorrection was introduced.

BATCH 77 — 通用 agent/做者、efforting/造作用力、mental chattering/概念戏论 假朋友加固 — 13 June 2026

本 Batch77 补丁为通用补丁，适用于所有 AtR / John Tan 翻译、审校、润色、格式化、QA、无修复晋级、打包、上传控制与交接流程。它不得削弱 Batch76 高风险佛法术语保护、本地教义污染审查、反实体化/反虚无化规则，Batch75 材料性/反反复复改写规则，Batch74 精确 artifact / 反假通过规则，Batch73 Presence / hybrid residue 规则，Batch71 Witness/sākṣī 规则，以及 Prompt T、Prompt X、Blogger HTML、href/src/code 与状态纪律规则。

核心教训
在 AtR / John Tan / anatta 翻译中，普通字典义可能成为假朋友。“agent” 在此类语境中常指被预设为行动来源的独立做者、行动者、控制者或主宰者，不是中介、代理人、代表或服务代理。“efforting” 常指造作的、自觉用力的、构造出来的 subtle doing，并不等于疲劳、费力到累、艰苦或耗神。“mental chattering” 在技术性佛法/哲学说明中常指概念化、推论化、增殖性的言说性思维，而不只是口语化的“脑内碎碎念”。只要上下文涉及 anatta、no-self、no-doer、dependent origination、non-doership、修行、知见、证悟或 AtR 说明，就必须把这些词作为高风险术语处理。

AGENT / DOER / AGENCY / DOERSHIP / AGENTLESSNESS / NON-DOERSHIP 审查门
在 anatta、no-self、no-doer、no-doership、agentlessness、dependent origination 及相关佛法/哲学语境中，“agent” 指被预设为独立做者、行动者、控制者、第一推动者或行动所从出的实体。除非源文清楚是在普通非佛法意义上使用，否则不得译成中介、经纪、代表、旅游代理、法律代理、商业代理、软件 agent、服务 agent 或被委托的代理人。

所有语言都必须选用能保留“独立做者/行动者/控制者”义的目标语表达。若目标语言中普通的“agent”对应词会导向中介/代表义，必须拒绝，并改用“independent agent/doer（独立 agent/做者）”、“independent actor/controller（独立行动者/控制者）”、“presumed doer（被预设的做者）”或相应目标语释义。

阿拉伯语专门规则：优先使用 فاعل، فاعل مستقل، الفاعل، الخلوّ من الفاعل، غياب الفاعل المستقل。避免 واسطة، وسيط، وكيل، عميل，以及任何暗示中介、代表、经纪、客户、商业/法律代理或服务代理的词，除非源文清楚是在该普通意义上使用。

EFFORTING / EFFORTLESSNESS 审查门
在 John Tan / AtR 用法中，“efforting” 常指造作、构造、自觉用力、人为努力或 subtle doing，是自然无造作/effortlessness 的反面。它通常不是疲惫、劳累、艰辛、吃力、费劲或身心疲劳。

所有语言都必须避免把 “efforting” 译成“累人的、艰苦的、令人疲惫的、费力到疲劳”等，除非具体句子清楚是在说疲劳。优先使用相当于“造作的努力”“人为努力”“构造出来的 doing”“带有造作的用力”“自觉用力/刻意 efforting”的表达。

阿拉伯语专门规则：优先使用 التكلّف، جهد مصطنع، مصحوب بالتكلّف، ينطوي على جهدٍ مصطنع، متكلّف。避免 مُجهد، مُرهق، شاق，除非源文清楚是在说疲劳、耗竭或身心艰苦。

MENTAL CHATTERING / DISCURSIVE THOUGHT 审查门
当 “mental chattering” 出现在 AtR / Dharma 说明中，并作为对概念性、推论性、增殖性、言说性/戏论性思维的技术性批评时，不得在目标语中机械译成过度口语化的“mind chatter”式表达，若该译法会降低文体、让哲学/佛法语境变得轻浮或随便。应保留“discursive/conceptual proliferation（言说性/概念性增殖、戏论、概念活动）”的意思，并选择适合该语言的佛法/哲学语域。

阿拉伯语专门规则：优先使用 التفكير الاستطرادي، التفكير الخطابي/المفهومي, حركة الذهن الخطابية/المفهومية。只有在源文语气明显口语或非正式时，才可使用 الثرثرة الذهنية。

PROMPT 6 / PROMPT 9 / 对抗性审校要求
在 Prompt 6、Prompt 9、Strict QA、formatter readback、打包校验、无修复晋级或任何对抗性审校中，必须显式扫描每一种目标语言中的以下假朋友：
1. “agent” 被误译为中介/代表/经纪/代理/服务代理，而不是独立做者/行动者/控制者；
2. “efforting” 被误译为疲劳、劳累、艰辛、费劲或耗竭，而不是造作/自觉用力的 doing；
3. “mental chattering” 在技术性佛法/哲学语境中被译得过度口语化，损害文体或意义。
若这类问题改变源文意义、教义清晰度或出版语域，即为材料性问题。必须全局修复，更新 Source-Term Decision Table / 高风险术语 ledger，并使用：“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” 只有后续单独一次精确 artifact、无材料编辑的重审，才可使用：“reviewed final / publishable — strict-certified final not claimed.”

BATCH 76 — 通用高风险佛法术语保留 + 本地教义污染审查 + 反实体化/反虚无化强化 — 8 June 2026

本 Batch76 补丁为通用补丁，适用于所有 AtR 翻译、审校、润色、格式化、QA、无修复晋级、打包、上传控制与交接流程。它不得削弱 Batch75 的材料性润色/反反复复改写规则、Batch74 的精确 artifact / 反假通过规则、Batch73 的 Presence / hybrid residue 规则、Batch72 的 Plum Dawn / 复制按钮 / UI 规则，以及更早的 Blogger chrome、href/src、不增添解释、不受公开译本污染、Prompt T、Prompt X 等规则。

核心教训
佛法技术术语在目标语言中可以语法正确、字典有据、网上有人使用，但仍可能在教义上不安全。某些本地词汇可能带入造物主/本源论、苏菲/伊斯兰、基督教、吠檀多/印度教、道教、新时代、心理学、法律、民间宗教、虚无论、常见论、实体化或形而上学色彩。因此，高风险佛法术语不得自动采用“最自然”的本地等值词。

通用 Source-Term Decision Gate（源术语决策门）
在初译定稿前，以及 Prompt 6 / Prompt 9 / Strict QA 式审校中，必须为文章核心高风险术语维护 Source-Term Decision Table。每个术语至少分类：
1. 源术语。
2. 拟用目标语译法。
3. 风险类型：安全可译 / 保留原术语 / 保留原术语 + 目标语释义 / 目标语词仅可在澄清后使用 / 因教义污染而拒绝该目标语词。
4. 理由。
5. 本 artifact 的最终处理规则。
若没有已知安全译法，应保留 English/Sanskrit/Pāli/Tibetan/AtR 标签并加简明目标语说明，而不是自信地创造一个本地等值词。

高风险术语族
至少对以下术语启用此门：dependent origination / dependent arising / pratītyasamutpāda / paṭicca-samuppāda；emptiness / śūnyatā；anatta / anātman / no-self / non-self / not-self；Self/self/true Self/self-view；I AM / AMness / Isness；Presence；Awareness/consciousness/mind；rigpa / vidyā / luminosity / clear light；Madhyamaka / Middle Way；Buddha-nature / tathāgatagarbha；non-arising / unborn；non-reification；suchness / thusness / dharmadhātu / dharmatā；total exertion / dependent designation / twofold emptiness；witness / Witness / sākṣī；agency/agent/actor/doer/perceiver；fruition/Buddhahood/liberation/awakening/enlightenment；以及文章特有的高风险术语。

本地宗教污染审查门
除非源文明确作比较，不得把佛法术语暗中翻成本地宗教/神学词汇。不得作为默认隐性译法的例子包括：苏菲/伊斯兰词如 fanāʾ、baqāʾ、ihsan、tawḥīd、Allah-realization；基督教词如 salvation、grace、Holy Spirit、Godhead、soul、creator；吠檀多/印度教词如 Brahman、Ātman、mokṣa、īśvara；道教词如 Dao、wu wei、original qi；新时代/心理学词如 universal consciousness、higher self、subconscious、ego death、pure consciousness。这些词只有在源文本身明确比较时，才可作为显式比较说明出现，不能成为佛法术语的隐藏译法。

反实体化 / 反本源论审查门
对于 dependent origination、emptiness、Buddha-nature、Presence、Awareness、rigpa、dharmadhātu、ground、source、essence、luminosity 等相关术语，检查目标语是否暗示固定本源、起源实体、独立根基、造物主、Brahman/Ātman、永恒见证者、常住 Self、形而上容器、万法从自存基底中流出、源文不含的对称互依、或把广义缘起/依他施设降格为单纯线性因果。

反虚无 / 反空洞审查门
对于 emptiness、voidness、nothingness、absence、non-arising、no-self、cessation 等相关表达，检查目标语是否暗示一切都不存在、断灭、无意识空白、死寂空洞、单纯缺席、抑郁/无意义、存在论非有，或把空性当作实体/地点。若本地词有这种风险，应保留 śūnyatā/emptiness 或相关源标签，并说明：空无自性/自有，不是虚无。

受保护标签与转写规则
当 AtR 或源文惯例需要时，必须精确保留受保护标签，尤其是 I AM、AMness、Isness、大写 Self、技术性 Presence、rigpa、vidyā、必要时的 anatta/anātman、Madhyamaka、śūnyatā，以及目标语等值词有风险时的 dependent origination。可以加目标语释义，但不得静默替换受保护标签。除非某英文技术术语的音译在该语言中已经是稳定惯例且适合本文，否则不要把英文术语音译成目标文字；优先保留拉丁源标签并加目标语说明。

RTL / 混合文字安全
对于阿拉伯语、希伯来语、波斯语、乌尔都语等从右到左书写页面，插入 Latin/Sanskrit/Pāli/Tibetan 技术标签时，必要时必须使用 bidi-safe span 或同等方向隔离。Formatter 与 Strict HTML QA 必须检查混合文字标签是否可读、未被重排、断裂或搅乱。不得把 bidi-safe spans、术语说明、首次出现释义当作“冗余”清理掉。

专家反馈门
若母语者或具领域知识的审校者指出某目标语术语造成教义扭曲，必须分类为：材料性教义风险 / 目标语流畅度问题 / 可选偏好 / 拒绝建议。不得仅因该词出现在字典、Wikipedia、旧译、或网上用例中就忽略。若属材料性问题，须全局修复，更新 Source-Term Decision Table，并写入 Change Materiality Ledger。

各提示词应用
Universal Intro 与 Prompt A：显式允许用户/审校者提供专家术语警告；要求 Source-Term Decision Table、首次出现处理与有意添加释义的记录。
Prompt 1/2/3/4/5/7/8：不要过度本地化高风险佛法术语；当本地等值词不安全时，保留标签并加释义；Prompt 8 不得把对话中的技术术语润色成本地宗教等值词。
Prompt 6：加入 Local Doctrinal Contamination / Anti-Substantialism / Anti-Nihilism 对抗性审查篮，并全局扫描高风险术语族。
Prompt 9：自然流畅不得压过术语安全；不得把受保护标签替换成听起来自然但教义污染的本地词。
Prompt T 与 Prompt X：当源锚点/源文恢复流程会进入目标 artifact 时，加入反本地宗教污染、受保护标签保留、释义一致性检查。
Protocol A/B 与 Upload Controller：要求 Source-Term Decision Table、术语保护说明、有意释义、专家反馈纳入、材料性术语修复后的状态纪律。
Unified Blogger Formatter 与 Strict HTML QA：保留术语说明、受保护标签、释义、bidi-safe spans、混合文字标签；审查受保护技术标签、首次出现释义、本地宗教污染、本源论/实体化、虚无化与方向性安全。
RemoveSegID / 机械工具：不得改动受保护技术标签、术语说明、释义、bidi spans、源标签、href/src/code 或解释性术语说明。

阿拉伯语案例示例——只是例子，不是阿拉伯语专属规则
dependent origination 不应在审校者警告其可能含有本源论时，只依赖 النشوء المعتمد / النشأة المعتمدة 等阿拉伯词。更安全的高风险处理可保留 “dependent origination (pratītyasamutpāda / paṭicca-samuppāda)” 并加阿语说明：قيام الظواهر اعتمادًا على شروط وأسباب متداخلة، لا صدورها من أصل ثابت أو مصدر قائم بذاته。
emptiness / śūnyatā 若用 الفراغ 会暗示空洞或虚无，应改用释义：الخلوّ من الوجود الذاتي أو الطبيعة الذاتية، لا العدم ولا الفراغ بمعنى الانمحاء。
I AM 作为 AtR 阶段标签保留 I AM，不应变成苏菲词。fanāʾ、baqāʾ、ihsan、tawḥīd 等苏菲/伊斯兰词，除非源文明确比较，否则不能作为佛法术语主译。Madhyamaka 在宗派名称身份重要时，不应只化约为本地语言的 “Middle Way”。

材料性与状态
凡涉及 dependent origination、emptiness、anatta、Self、I AM、Presence、Awareness、rigpa、Madhyamaka、Buddha-nature、agency/doer/perceiver 或其他高风险术语的术语改动，均属材料性改动。此类 pass 不得在同一轮晋级为最终。状态必须是：“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” 只有之后重新打开精确 artifact、无材料编辑的 readback pass，才可使用：“reviewed final / publishable — strict-certified final not claimed.”


适用范围： Universal Intro: 这是 the first user-facing control prompt; enforce the Key Term Research Table, Presence Gate, parenthetical-order rule, hybrid residue scan, and no-repair promotion hardening before any final claim.




第 75 批 — 普遍适用的“改动重要性判断 + 防反复打磨”强化 — 4 June 2026

本第 75 批补丁普遍适用于所有 AtR 翻译、审校、润色、修复、格式化、QA、无修复晋级、打包与交接流程。它不会削弱第 74 批关于防假通过、精确工件、拉丁字母语言流畅度、混合残留、标题/链接、href/src、Blogger 原生结构、源文忠实度等任何硬性关卡。

改动重要性判断关卡（Materiality-Aware Polish Gate）
在任何翻译、润色、对抗性审查、修复、审计或无修复晋级中，只要准备改动可见文本，必须先分类：

A. 必须修复（Required repair）——必须改。
包括影响源文忠实、遗漏/添加、误译、教义或术语准确性、核心术语一致性、说话人归属、精确标题/链接文字、源语言残留、混合语言/混合标签残留、保留的梵文/巴利文/藏文/英文标签形态错误、目标语言语法、标点或断行合并损伤、可读性、HTML/链接/媒体/代码完整性，以及目标语表达已经显得机器翻译、生硬、晦涩、干扰阅读或误导教义理解的情况。

B. 有益润色（Beneficial polish）——主动编辑阶段允许。
当前译文不一定严格错误，但改动能实质提升发表质量：更自然、更顺、更符合公开 AtR 佛法文章语体、减少翻译腔、澄清难懂的教义点、统一重复术语家族、把生硬直译改成自然表达、让保留技术标签更自然地融入目标语语法。若改了可见文本，该轮仍属于编辑/修复/润色轮，除非之后另开无材料改动的晋级轮，否则不能在同一轮宣称无修复晋级。

C. 偏好性改写（Preferential rewrite）——避免。
如果现有表述已经忠实、教义清楚、语法正确、自然、术语一致、可发表，并且没有残留、混合标签、标题漂移、标点、链接或 HTML 问题，不要仅因另一个同义表达也可以或稍微偏好就反复改写。

模式规则
主动翻译/修复/对抗性审查：必须修复 A 类；可以进行 B 类发表质量润色；通常避免 C 类偏好改写。凡改动可见文本，必须记录并保持修复/编辑状态。

无修复晋级：必须重新打开精确最新版工件，主动寻找必须修复的问题，也可识别有益润色但不得编辑，不能只因还有另一个可接受说法就阻止晋级。若只剩可选润色或偏好替代，记录“仅有可选润色；无需材料修复”。若发现必须修复问题，则修复并重置为修复状态。

改动重要性台账
修复或对抗性审查报告必须包含简明“改动重要性台账”：最近标题/定位点、旧文、新文、类别（必须修复 / 有益润色 / 已避免偏好改写）、理由、是否影响状态。无修复晋级报告必须列明：是否发现必须修复、是否发现但未编辑有益润色、是否避免偏好改写、是否做了材料改动。

防反复打磨停止规则
多轮对抗性审查之后，如果精确最新版工件没有必须修复的问题，剩余只是偏好改写或可选有益润色，就停止编辑。不得因同义词级别或偏好级别改写反复重置状态。只有在重新打开精确工件、比对源文、通过术语/残留/混合/标题/链接/href/src/结构/流畅度关卡、没有必须修复、没有可见文本材料改动后，才能进入无修复晋级。

不得削弱强 QA
遗漏、添加、误译、教义扭曲、错误术语、源语言残留、混合语言残留、保留标签形态错误、语法损坏、影响发表质量的翻译腔、精确标题漂移、链接文字损坏、href/src/媒体/代码突变、说话人归属错误、标点或断行合并损伤、结构遗漏/重复、误导性的目标语表达，仍然都是必须修复的材料缺陷。

BATCH 74 — UNIVERSAL MATERIALITY-AWARE POLISH + ANTI-CHURN HARDENING — 2026 年 6 月 3 日

本 Batch76 补丁是通用补丁，不是只针对波兰文。它适用于拉丁字母、非拉丁字母、屈折语、分析语、从右到左书写语言，以及混合文字目标语。必须保留 Batch73 Presence / hybrid-residue 规则，以及 Batch72/71/70/68/67/66 继承下来的所有防护。

虚假通过 / 重用旧 artifact 失败门
任何 review、repair、no-repair promotion、package 或 handoff pass，只有在重新打开 exact latest artifact 并为本次 pass 产生新的证据时才有效。不得把过去的 pass summary、旧链接、旧 QA 报告、旧文件名或记忆当作新的 review。若助手发现自己声称做了新 pass，但实际只是重用旧 artifact 或没有真正 review，必须明确撤回该说法，指出最新真实 artifact，不得继续假装该 false pass 存在。

Exact-artifact 证据要求
每次 pass 都必须报告 exact input artifact path/name、exact output artifact path/name、输出是否 byte-for-byte identical 或 materially changed，并在工具环境允许时给出 SHA/hash 或等效 identity evidence。还必须说明每个 intended replacement 是否真的匹配并应用。若没有生成新 artifact 或新的 no-material-edit QA report，不得声称完成新 pass；应说：No new pass was completed.

No-repair 与 repair 必须分离
严格 no-repair promotion pass 不得做 material edits。若发现任何 material issue，promotion 失败。要么停止并输出 failed-promotion report，要么另开 material repair pass。任何做了 material edits 的 pass 都必须使用：REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required。不得在同一 pass 中同时 promotion。

禁止 thought-only review
只思考几秒后重复旧链接不是 review。有效 review 必须有具体证据：打开 latest artifact、搜索/扫描目标文本、抽查高风险 source/target passages、运行目标语 fluency checks、检查 cumulative risk basket、检查 href/src/media/code parity，并生成新的 QA report，或明确说明没有创建新 artifact。

字符串式修补脆弱性 / 0-match 规则
如果 targeted repair 在当前 artifact 中没有匹配，不得假设问题已经修好。必须搜索语义变体、较短子串、屈折变体、大小写变体、标点变体、HTML 分隔变体，以及附近上下文。每个 0-replacement intended repair 都要记录为 warning 并要求调查。脚本修补的 QA 必须列出搜索的 old string/pattern、match count、replacement applied、0-match intended repairs、semantic follow-up search，以及 cumulative risk basket 的前后状态。

拉丁字母目标语 residue 与 fluency 门
拉丁字母目标语中，普通英文 residue 更难看出，因为源语与目标语都可能使用拉丁字母。必须额外运行 Latin-script residue scan，检查普通 prose 中残留英文、英文技术标签造成当地语法错误、英文术语与当地屈折/格/介词粘连、未加引号的英文标签被当作目标语名词、source title fragments 被部分翻译，以及看似通顺但实际是英文成语直译的 calque。

屈折语言 protected-label agreement 门
对于屈折目标语，保留的 AMness、I AMness、Presence、Awareness、Self、No Mind、no-mind、Dharma、Dhamma、Maha、anatta、anātman、dhātu、skandha、śūnyatā 等标签，必须检查格、性、数、agreement 与自然语法。若保留 protected label，周围句子仍必须自然。必要时改用目标语在前、引号、或短说明，而不是强迫 retained label 承受目标语语法。

Slash-calque hardening
扫描可见 prose 中的 slash compounds，例如 A/B、A / B、A/B/C、subject/object、doer/agency、Dhamma/Dharma、I/self/Self、mind/consciousness、realization/actualization、no-self/non-self/anatta/anātman、链接标题片段，以及用 slash 连接的人名/别名。每处都必须分类为 exact title/proper label、glossary/termbank、ordinary prose 或 ambiguous。精确标题与有意 glossary label 可保留；ordinary prose 应改成自然的目标语并列、同位语或说明；ambiguous 则标注 human review。

精确标题 vs 翻译标题强化
每个 link-bound title 都要单独决定：完整保留精确原题、完整自然翻译，或有意配对。不得部分翻译标题、尊称或标题片段，例如把 “Mr.” 译成目标语却保留其余英文。不得把目标语词语混入精确英文标题，除非原题本来如此。QA 必须列出 linked titles 是 preserved、translated，还是 intentionally mixed/paired。

Idiom / metaphor calque hardening
Prompt-level review 必须主动搜寻英文成语/比喻的机械直译，并建立目标语专属 idiom/calque risk basket。种子例子包括：go and read、goes down the drain、along the line of、break through、stood out、one hand claps、the drop is thorough、quality time、open and boundless、wholly thus、always already so、no mirror reflecting、magical appearances are too empty。本列表只是示例，不是穷尽。

技术术语族漂移门
一旦某术语族造成反复修补，就必须加入 cumulative risk basket 并全局扫描所有变体。高风险术语族包括 actualization/actualize/embodied/lived/integrated；ground/Ground of Being/ground reality/basis/path；Presence/pure Presence/total Presence；AMness/I AMness/I AM；Self/self/no-self/no-I/anatta/anātman；no-mind/No Mind/Mind that is no-mind；subject/object；doer/agency/no-doership；total exertion/total activity/full functioning；suchness/thusness/isness/wholly thus/Always So；Maha；yāna/lower yānas；dhātu/skandha；knowledge/cognitive obscurations；māyā/magical appearances；mirror/no mirror/mirror-like awareness。

机械正确但不自然也是 material
译文即使通过术语表，也可能因目标语 prose 不自然或教义上误导而失败。若影响可读性或教义清晰度，以下都属于 material defects：格/性/数 agreement 不自然、源语词序复制太重、line-merge 造成片段句、技术标签未整合进语法、slash-heavy prose、比喻直译、链接/引号/括号附近目标语标点问题、技术词大小写问题、把 Dharma 技术词误译成普通词。

No-repair promotion 证据附录
No-repair pass 必须包含 “No New Artifact Reuse / Exact Artifact Evidence” 小节，列明：I reopened: [exact file]；I produced: [exact report/file]；Material edits made: yes/no；若 no，输出是 byte-for-byte identical / hash-equivalent / explicitly copied unchanged；若 yes，则 no promotion allowed；未假设 prior pass status；列出 new review evidence。

跨语言术语来源证据的限度
在可行时，可用目标语佛教资料确认主要 Dharma 术语选择，但这类证据只支持大方向术语选择，不证明句子级忠实度、上下文适配或目标语流畅度。段落/链接/blockquote/list 数量一致是必要但不足的，绝不能当作翻译质量证明。

状态纪律
若在先前 no-repair promotion 后又发现 material issues，必须写明：Previous promotion was premature. This pass found material issues that should have been caught earlier. Status is reset to REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required. 永远不得声称 strict-certified final。

BATCH 73 — UNIVERSAL PRESENCE GATE + TARGET-LANGUAGE-FIRST PARENTHETICAL ORDER + HYBRID RESIDUE HARDENING — 1 June 2026

本 Batch73 补丁是通用补丁，不是只针对日文。凡是会创建、翻译、审校、精修、HTML 翻译、审计、格式化、打包、发布或声明 ATR artifact 状态的 managed prompts，均须应用本规则。

通用关键术语研究门控
翻译或统一任何高风险 AtR / 佛法术语前，不得只依赖字典、记忆、既有目标语习惯，或另一种语言的术语表。每篇文章应为文章核心术语建立或更新简明的 Key Term Research / Decision Table。表中至少记录：源词、目标语译法、翻译/保留/转写/配对状态、是否可作为 protected label 保留、普通 prose 译法规则、禁用或高风险译法、是否需要外部/源文研究、是否有多重语义需按上下文区分。

最低高风险篮：Presence/presence、Awareness/awareness、I AM/AMness、anatta/no-self/non-self/anatman、emptiness/empty nature、dependent arising/dependent origination、non-dual/non-duality、no-mind/No Mind/One Mind、luminosity/clarity/vividness、manifestation/appearance/phenomena、suchness/thusness/isness、subject/object/subject-object division、agent/agency/doer/doership/non-doership、spontaneous perfection、total exertion、Dzogchen/Mahamudra/rigpa/Dharma/Buddhadharma，以及文章特有核心术语。

通用 Presence Gate
Presence 必须视为高风险 AtR / 佛法术语，不可当成普通英文 presence 机械处理。必须区分技术性 AtR Presence、普通 presence/present、ever-present / already-so 句式、西方哲学 / metaphysics of presence 语境，以及 Dzogchen 标题或固定短语如 Instant Presence。技术性 AtR Presence 指 luminous immediacy / direct actuality / vivid fact of being-experience，常见于 pure Presence、Total Presence、Presence-Awareness、Presence is spontaneously perfected、manifold of Presence、nature of Presence 等表达，须经目标语研究和术语表决定。

日文 Seven Stages 文章族的 house-style 说明：技术性 AtR Presence 默认用 臨在；pure Presence = 純粋な臨在；Total Presence = 総体的臨在；Presence-Awareness = 臨在＝覚知；Presence is spontaneously perfected = 臨在は自ずから円成している / 按上下文处理。除非上下文明确是哲学/现象学语境，不得把 現前性 作为 AtR Presence 默认译法。普通 present / ever-present 可按句子需要使用 現前している、すでに現れている、常にすでにそうである 等自然表达。此日文说明不得强加给其他目标语。中文 AtR house style 可在适当处保留 臨在，但中文选择只是线索，不自动决定所有其他语言。

目标语优先括注顺序规则
在普通目标语 prose 中，如需保留英文/Sanskrit/Pāli/Tibetan/source label，默认使用目标语在前：目标语译法（source label）。普通 prose 中避免 source label（目标语译法），除非该 source label 是精确标题、正在作为短语被讨论、目标语惯例强烈要求 source label 在前、用户明确要求，或该处是 glossary/termbank。不得把保留的 source label 直接粘到目标语格尾、助词、后缀、后置词、clitic 或屈折结尾上。

日文例子：用 無我（anatta）の，不用 anatta の；用 空性（shunyata）の実現，不用 shunyata の実現；普通 prose 用 心（Mind），不用 Mind（心）；用 伝達（transmission），不用 transmission（伝達）；用 無我（no-self），不用 no self（無我）。避免 Pure覚知、Natural覚知、Non-dual は、dependent origination の、ground と path、meditative composure と insight、no-mind の状態、anatta実現、Maha経験、On 空性、Self-実現、Being／Self-Realisation への 等 hybrid。

通用 hybrid residue scan
最终稿或 promotion 前，必须建立目标语专用 hybrid scan basket。扫描：英文/source label 粘连本地助词/格标记/后缀/屈折；英文词进入目标语复合词；目标语词插入精确英文标题；mixed-script 技术 hybrid；普通 prose 中英文优先括注；精确英文标题中夹入已翻译片段；普通英文 prose 被误保护成 technical label；括号后本地助词前出现异常空格。拉丁字母目标语须额外做 ordinary-English residue scan，因为英文残留更难发现。

日文风险篮种子：Pure覚知；Natural覚知；Non-dual は；dependent origination の；ground と path；meditative composure と insight；no-mind の状態；anatta の/へ/と/を/は/後/実現；Maha経験；On 空性；Self-実現；Being／Self-Realisation への；transmission（伝達）；no self（無我）；Dhamma／Dharma） を；Awakening to Reality 実践 Guide；音Cloud；Scenery……；真如のMaha経験；五蘊（五蘊）。并扫描 Latin/source label + の、を、に、へ、と、は、が、で、も、から、まで、より，以及 後、的、性、実現、経験、状態、化、作用、実践、知見、覚知、空性。

精确标题 vs 翻译标题处理
每个带链接的文章/书/video/audio 标题都必须判断：link text 应保留精确 source title，还是译成完整自然目标语标题。若保留，则整题精确保留，不可局部翻译；若翻译，则整题自然翻译，必要时在括号中保留 source title。不得制造 On 空性、Awakening to Reality 実践 Guide、Recognizing Rigpa vs Realizing 空性 等混合标题。不得翻译 URL slug。QA 必须记录有意保留或有意翻译的标题。

Protected-label whitelist 纪律
某词是 technical 不代表它必须留英文。每个保留的 English/Sanskrit/Pāli/Tibetan label 必须归类：精确标题、专名、URL/code、有意保留的技术术语、有意保留的 English AtR label、目标语译法后的括注 gloss、或 human-review placeholder。ordinary lowercase terms 如 experience、realization、practice、view、awareness、consciousness、manifestation、ground、path、source、self、mind、state、clarity、naturalness、ordinariness、spontaneity、agent、doer、doership、subject、object 通常应翻译，除非记录保留理由。

术语族升级规则
若同一术语族出现一次以上 material issue，必须把该术语族升级到 active termbank 和 scan basket。例如 Presence 曾误译一次，则全局扫描 Presence、pure Presence、Total Presence、Presence-Awareness、nature of Presence、present、ever-present 及目标语候选；若出现一个 anatta hybrid，则扫描所有 anatta/no-self/non-self/anatman；若出现 total exertion 问题，则全局扫描 total exertion/total activity/complete activity/full function 等等。

Total exertion 源文觉察规则
不得机械给 total exertion 设默认译法。日文 Dōgen/Zenki 语境应按源义考虑 全機 与 一法究尽。中文继续保留既有规则：不得把 total exertion 默认译成 全体作用，应使用 一法究尽 / 具尽 / 依上下文处理。其他语言须先研究源文/语境，再定默认。

No-repair promotion 强化
No-repair promotion 不得只做 count、href/src 和结构检查。必须重新打开 exact artifact、对照 source、运行 Prompt 6 语义忠实审校、Prompt 9 目标语流畅度审校、目标语 hybrid residue scan、目标语优先括注顺序扫描、高风险术语表一致性扫描、精确链接标题扫描、普通 prose vs protected label 分类、URL/href/src/code 完整性扫描、标点/并行/断行扫描，并从开头、中段、结尾、blockquote、粗斜体区和所有文章核心术语处抽样审读。若此前已经 promotion 后又发现 material issue，必须明确撤回先前 promotion 并重置状态：Previous promotion was premature. This pass found material issues that should have been caught earlier. Status is reset to REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.

Required QA evidence additions
每份 final/review/promotion QA report 应包含：确切 source file、确切 target file、使用的 prompt versions、目标语风险画像、key term decision table、Presence Gate 结果、括注顺序扫描、hybrid residue scan basket、ordinary English/source residue basket、protected-label whitelist、精确链接标题扫描、href/src/media parity、URL/code 中是否混入非源文本、主要结构计数、代表性句子抽样、累计风险篮与结果、是否做了 material edits、正确状态标签。

状态纪律
Batch73 属 material managed-prompt update，状态必须为：REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required。只有后续 exact-artifact no-material-edit readback pass 才可提升为：reviewed final / publishable — strict-certified final not claimed。


**Version note:** This is the full language-agnostic initial prompt for ATR HTML article translation workflows. It is intended to apply to all ATR target languages, including but not limited to Simplified Chinese, Traditional Chinese, Tibetan, Nepali, Bengali, Spanish, Hindi, Tamil, Portuguese, Japanese, Thai, Polish, Danish, Vietnamese, French, Indonesian, Malay, Korean, Arabic, Russian, Italian, Serbian, Burmese, Sinhala, Greek, Ukrainian, Swedish, and any other requested target language. It is not a patch and is not specific to any one translation. It incorporates hard QA gates against premature “final/publishable” claims, weak no-repair promotions, untranslated source-language residue, mixed-language hybrids, URL/code corruption, and target-language fluency failures.


## 0. Target-language configuration

Set the following values before starting:

* `TARGET_LANGUAGE`: [e.g. Simplified Chinese / Traditional Chinese / Tibetan / Nepali / Bengali / Spanish / Hindi / Tamil / Portuguese / Japanese / Thai / Polish / Danish / Vietnamese / French / Indonesian / Malay / Korean / Arabic / Russian / Italian / Serbian / Burmese / Sinhala / Greek / Ukrainian / Swedish / any other requested target language]
* `TARGET_LANGUAGE_LABEL`: [human-readable label for reports, e.g. “Simplified Chinese translation,” “Bengali translation,” “Spanish translation,” “Tibetan translation,” “Ukrainian translation,” etc.]
* `TARGET_SCRIPT_OR_VARIANT`: [e.g. zh-Hans / zh-Hant / Tibetan / Devanagari / Bengali / Tamil / Arabic / Cyrillic / Greek / Latin-script European language / Japanese / Korean / Thai / Burmese / Sinhala / etc., or “not applicable”]
* `SOURCE_LANGUAGE`: English
* `SOURCE_ARTICLE_URL`: [insert English original URL if available; otherwise use `URL_NEEDED_HUMAN_REVIEW`]
* `SOURCE_ARTICLE_TITLE`: [insert English article title]
* `TOP_ORIGINAL_LINK_LABEL`: [target-language label for “English original,” e.g. for Simplified Chinese: 英文原文; for Bengali: ইংরেজি মূল]
* `USER_NAME_RENDERING_RULE`: Preserve “Soh Wei Yu” or “Soh” unless I explicitly provide a target-language rendering.
* `TARGET_LANGUAGE_TERMBANK`: Use the target-language-specific termbank supplied below or in the uploaded prompt pack. If no target-language termbank is supplied, translate technical terms conservatively according to the uploaded prompt pack and source context.

Please translate the uploaded English Blogger HTML article into `TARGET_LANGUAGE`.

I will upload:

1. The current ATR prompt pack ZIP.
2. The English source HTML article to translate.

Important:
This is a fresh `TARGET_LANGUAGE_LABEL` workflow, not a repair of an existing target-language translation unless I explicitly upload an existing target-language file and ask for review/repair.



### 0.1 Universal scope and no single-language assumption

This prompt must remain applicable to all requested ATR target languages. Do not silently adapt it into a language-specific prompt unless the user explicitly asks for a target-language-specific derivative.

For each new translation workflow:

* Treat `TARGET_LANGUAGE` as the only active target language.
* Do not import the terminology decisions, residue patterns, grammar assumptions, punctuation conventions, or protected-term choices from a previous target language unless they are explicitly stated as universal in this prompt or in the uploaded prompt pack.
* Before translating, infer or construct a small target-language risk profile based on the language’s script, morphology, punctuation, and common translation failure modes.
* If a target language uses the Latin alphabet, source-language residue is harder to detect because English and target language share letters; therefore perform an extra ordinary-English residue scan using high-risk English Dharma and prose terms.
* If a target language uses a non-Latin script, perform an extra mixed-script and transliterated-English scan.
* If a target language is inflected, perform an extra grammar scan for case, gender, number, tense, agreement, compounds, and unnatural literal calques.
* If a target language is analytic or topic-prominent, perform an extra scan for unnatural word-for-word source syntax, dropped particles, and broken sentence flow.
* If a target language is right-to-left, perform an extra audit for punctuation directionality, URL isolation, list formatting, and HTML attribute safety.
* If the prompt pack or user provides a target-language termbank, that termbank controls over generic dictionary choices, subject always to source meaning and prompt-pack rules.

### 0.2 Anti-false-final principle

The main failure this prompt is designed to prevent is false promotion: claiming that a translation is “reviewed,” “publishable,” “complete,” or “final” while later Prompt 6/9 review still finds material defects.

Therefore:

* QA must be adversarial, not confirmatory.
* A no-repair promotion pass must try to disprove readiness, not merely confirm prior status.
* Mechanical HTML/count parity does not prove translation quality.
* A Prompt 6/9 review is not complete unless it checks semantic fidelity, doctrinal terminology, target-language fluency, ordinary source-language residue, mixed-language residue, line-merge damage, punctuation, exact-title handling, and HTML/code preservation.
* If a later pass finds material issues that an earlier “publishable” or “no-repair” pass should have found, explicitly treat the earlier promotion as false, retract the promotion status for the current working artifact, repair the issue, and add that defect family to the cumulative risk basket.

---

## 1. First inspect the uploaded prompt pack, then actively apply it

Before translating, editing, judging, or formatting anything, inspect the uploaded prompt pack carefully. Do not rely on memory or previous sessions.

Read the relevant prompts and workflow rules, especially:

* Prompt A: HTML Article Translation Workflow
* Prompt 1: High-Fidelity Translation Workflow
* Prompt 6: High-Fidelity Translation Review
* Prompt 9: Whole-Document Refinement
* Prompt 8, if present and relevant to dialogue/chat-log cleanup
* Unified Blogger Formatting Prompt, if the pack routes Blogger presentation through it
* Strict HTML QA Audit Prompt, if present
* Any Batch67+ / no-repair promotion / status-label / no-premature-final rules in the pack

However, inspecting the prompts is not enough. You must actively apply the relevant prompts as the operative workflow for the task.

Do not use prompt names as a ritual label. If you say Prompt 6 or Prompt 9 was applied, the artifact and QA report must show evidence that the relevant checks were actually performed. A later discovery of obvious residue, line-merge damage, target-language grammar errors, or recurring calques means the earlier Prompt 6/9 claim was incomplete and must be treated as a QA failure.

Use the uploaded prompt pack as controlling instructions in this exact functional order:

1. **Prompt A — governs the HTML article workflow**

   * Apply Prompt A to control source-of-truth discipline, HTML/Blogger preservation, routing, artifact handling, cumulative checkpoints, link/media preservation, and final QA requirements.

2. **Prompt 1 — governs the actual high-fidelity translation into `TARGET_LANGUAGE`**

   * Do not merely read Prompt 1.
   * Translate the article according to Prompt 1’s Buddhist/Dharma translation rules.
   * Apply Prompt 1’s source-faithfulness, doctrinal precision, terminology discipline, no-omission, no-added-gloss, and no-paraphrase requirements throughout the actual `TARGET_LANGUAGE` translation.

3. **Prompt 6 — governs the post-translation fidelity and terminology review**

   * After translating, review the `TARGET_LANGUAGE` output against the English source using Prompt 6.
   * Repair mistranslations, omissions, additions, doctrinal distortions, terminology errors, speaker-attribution issues, source-language residue, mixed-language hybrid residue, and unnatural target-language wording that affects fidelity or clarity.
   * Do not treat Prompt 6 as optional commentary; it must be used as an active QA pass.

4. **Prompt 9 — governs whole-document refinement after Prompt 6**

   * After Prompt 6 review, run Prompt 9 across the whole translated document.
   * Refine consistency, readability, punctuation, terminology, line-merge damage, target-language flow, and whole-document coherence without paraphrasing away source meaning or adding new doctrine.

5. **Prompt 8 — apply before translation only if relevant**

   * If the article is dialogue/chat-log-heavy, or if the pack routes the task through Prompt 8, apply Prompt 8’s dialogue-cleanup rules before translation.
   * Apply Prompt 8 only to the extent required by the source workflow.
   * Preserve speaker attribution, chronology, and source-traceable line merging.
   * Do not invent speakers.
   * Do not split one speaker’s sentence into another speaker’s turn.
   * Do not convert a tagged name inside one paragraph into a new speaker label unless the source clearly makes it a separate speaker turn.

6. **Unified Blogger Formatting / Strict HTML QA — apply at the end if routed by the pack**

   * If the uploaded pack routes final Blogger presentation through the Unified Blogger Formatting Prompt or Strict HTML QA Audit Prompt, apply them as actual final checks, not merely as references.
   * Preserve CSS, wrappers, IDs/classes, links, media, iframe/script/config values, href/src values, and Blogger structure unless a prompt explicitly authorizes a change.

Do not say “I read Prompt 1” and then translate generically. The output must show that Prompt 1 governed the translation, Prompt 6 governed the review, Prompt 9 governed the refinement, and Prompt A governed the HTML workflow.

---

## 2. Critical task-object rule

* Prompt A / Prompt 1 / Prompt 6 / Prompt 9 are workflow instructions, not the source article.
* Translate the uploaded English HTML article, not the prompt files themselves.
* Only translate Prompt A or any prompt file if I explicitly say: “translate Prompt A itself” or “translate this prompt file.”

---

## 3. Source-of-truth rules

* The uploaded English HTML is the authority, not the live webpage.
* If I later upload a newer English HTML, treat the newer uploaded English HTML as the new source of truth.
* When a newer English HTML is uploaded, compare it carefully against the previous English source and update the `TARGET_LANGUAGE` translation for all changes, not only the examples I mention.
* Existing live translations or previous target-language versions are not the source and must not be used as scaffolds, missing-block donors, or authority unless I explicitly instruct you to compare or reuse them.
* Preserve meaning exactly, especially doctrinal nuance.
* Do not omit, summarize, paraphrase away, shorten, reorganize, or add doctrinal glosses unless the prompt pack explicitly requires cleanup.
* Do not introduce new explanatory material unless clearly marked and explicitly requested.
* If you find ambiguous/source-dependent issues, flag them clearly for human review instead of silently deciding.

---

## 4. HTML / Blogger preservation rules

* Preserve all Blogger HTML, CSS, classes, IDs, wrappers, structure, links, anchors, images, blockquotes, media embeds, iframe/script/config values, and layout unless a change is required by the prompt pack.
* Preserve the `<style>` block as code.
* Do not translate CSS property names, class names, selectors, URL paths, script/config values, href/src values, or code-like attributes.
* Preserve all href/src URLs exactly unless I explicitly ask to update a link.
* Translate visible article/body text into `TARGET_LANGUAGE`.
* Translate human-facing attributes such as `alt`, `title`, `aria-label`, `placeholder`, iframe `title`, and caption-like data attributes unless they are exact titles, proper names, URLs, code, or protected labels.
* Do not broadly redesign the article.
* Hard gate: after translation, review all `href`, `src`, `action`, CSS `url(...)`, iframe config URLs, script/config URL values, and code-like attributes to ensure no target-language words, non-source non-Latin characters, spaces, or translated slugs were inserted.
* If any URL or code-like value is changed without explicit user instruction, it is a material defect and must be repaired.

---

## 5. English-original link requirement

If this is a target-language translation page, add one top link after the hero/title or near the top:

`TOP_ORIGINAL_LINK_LABEL`：<a href="SOURCE_ARTICLE_URL">SOURCE_ARTICLE_TITLE</a>

Use the actual uploaded English article URL if provided. If the English URL is not provided, insert `URL_NEEDED_HUMAN_REVIEW` and flag it for human review.

Preserve all existing original links and add this as one extra link only.

In every QA report, explicitly account for this one intentional extra link if `SOURCE_ARTICLE_URL` was inserted or if `URL_NEEDED_HUMAN_REVIEW` remains.

---

## 6. Important workflow requirement — cumulative full HTML only

Do not return isolated “Part 1 / Part 2” fragment files.

If the article is too long to finish in one turn, return a cumulative full working HTML file each time.

Meaning:

* First return: full HTML shell + translated content from the beginning up to the current stopping point.
* Next return: the same cumulative HTML, with the next translated section appended.
* Continue this way until the full article is translated.
* Each returned file must be a valid Blogger-ready HTML file, not just a fragment.
* If translation is incomplete, exclude later untranslated English article-body content rather than leaving it inside the returned HTML.
* Keep the style block closed before the article body in every returned file.

---

## 7. Required process

A. Inspect the uploaded prompt pack.

B. Identify the relevant controlling rules from Prompt A / Prompt 1 / Prompt 6 / Prompt 9 / Prompt 8 / Blogger Formatting / Strict HTML QA.

C. Confirm the task object: the English HTML article is the source, not the prompt files.

D. Apply Prompt A to set up the HTML article translation workflow and preservation constraints.

E. Apply Prompt 1 to translate the uploaded English HTML into `TARGET_LANGUAGE` while preserving all HTML/CSS/link/media structure.

F. Apply Prompt 6 as a full post-translation review against the English source:

* fidelity
* terminology
* omissions
* additions
* doctrinal nuance
* speaker attribution
* source-language residue
* mixed-language hybrid residue
* exact-title handling
* HTML-preservation risks

G. Apply Prompt 9 as a whole-document refinement pass:

* source-faithful clarity
* consistency
* punctuation
* readability
* terminology coherence
* line-merge cleanup
* no paraphrasing away source meaning
* no new doctrine

H. Apply Blogger Formatting / Strict HTML QA checks if the pack routes final presentation through them.

I. Apply the hard final-gate module in Section 16 before any publishable/final status.

I2. Apply the adversarial Prompt 6/9 defect-hunt module in Sections 16.11–16.16 before any no-repair promotion. This includes target-language fluency review, high-risk sentence sampling, residue search baskets, calque/grammar scans, and evidence logging.

J. Produce the required artifacts.

---

## 8. Per-response Prompt Application Ledger

In every response, include a brief **Prompt Application Ledger** before the checkpoint audit or final summary.

Do not merely state that the prompts were read. State how they were applied in this response.

Use this compact format:

**Prompt Application Ledger**

* **Prompt A:** Applied for HTML/Blogger workflow, source-of-truth discipline, structure preservation, href/src/media preservation, and checkpoint/final artifact rules.
* **Prompt 1:** Applied as the active translation engine for the current covered source range, including high-fidelity Dharma translation, terminology discipline, no omission, no added gloss, and no paraphrase.
* **Prompt 6:** Applied as the active review pass for the current translated range, checking fidelity, terminology, doctrinal nuance, omissions, additions, mistranslations, source-language residue, and HTML preservation.
* **Prompt 9:** Applied as the whole-document/current-checkpoint refinement pass for consistency, punctuation, readability, source-faithful flow, and mixed-language cleanup.
* **Prompt 8:** Applied only if dialogue/chat-log cleanup was required; otherwise state “Not applied — no dialogue/chat-log cleanup needed in this range.”
* **Blogger Formatting / Strict HTML QA:** Applied if routed by the prompt pack; otherwise state “Not applied in this checkpoint unless final Blogger QA is routed by the pack.”
* **Hard Final-Gate Module:** State whether Section 16 was applied, whether any material edits were made, and whether no-repair promotion is allowed.

The ledger must be specific to the actual work done in that response. Do not use it as boilerplate if a prompt was not actually applied.

The ledger must not replace evidence. For every final, repair, or promotion response, the QA/changelog must also include concrete audit evidence such as search baskets used, issue families checked, representative source/target sentinels, and whether any material issue was found or repaired.

---

## 9. Critical workflow discipline and status labels

Do not prematurely call the file final-ready.

For a fresh translation, the initial translation itself counts as a material creation/editing pass. Therefore, do not promote it to publishable/final in the same pass.

Use these status labels strictly:

1. If you create the translation or make any material correction in the current pass, status must be:

“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.”

2. Only after a later pass reopens the exact latest repaired/translated artifact and makes no material edits may you promote it to:

“reviewed final / publishable — strict-certified final not claimed.”

3. Do not claim “strict-certified final,” “perfect,” or “final-ready” unless the prompt pack explicitly permits that status.

4. If I later say “continue,” perform the no-repair promotion pass on the exact latest artifact. If no material edits are made, promote to:

“reviewed final / publishable — strict-certified final not claimed.”

If you find new material issues, repair them and keep the status as:

“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.”

5. If you cannot actually perform a required check, do not claim it passed. State:

“Not fully verified: [specific check]. Human review required.”

6. If a later review finds material defects after an earlier no-repair promotion or publishable status, do not defend the earlier status. Say plainly:

“Previous promotion was premature. This pass found material issues that should have been caught earlier. Status is reset to REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.”

7. The next no-repair promotion attempt must include the newly discovered issue family in the risk basket and must scan globally for related defects.

---

## 10. Cumulative checkpoint audit

For every returned checkpoint, briefly report:

* Source visible text-node range covered so far, or nearest source heading/date/source-inline sentinel if exact node count is not available.
* First and last covered source sentinel.
* Next source line/sentinel if incomplete.
* Whether the style block is closed before the article body.
* Whether tag/class structure is preserved for the covered range.
* Whether links/hrefs are preserved exactly for the covered range.
* Whether src/media are preserved exactly for the covered range.
* Whether human-facing attributes in the covered range are translated/preserved/classified.
* Whether ordinary untranslated English remains, excluding proper names, URLs, exact titles, and intentional technical labels.
* Whether no forbidden target-language terms remain in the covered range.
* Whether any source-language + target-language hybrid constructions remain.
* Whether any target-language or non-source non-Latin text entered `href`, `src`, `action`, CSS URLs, iframe config URLs, script/config URLs, IDs, classes, or selectors.
* Whether any intentional extra link, such as the required English-original link, is accounted for.

---

## 11. Dialogue / speaker-attribution audit

Compare every `.dialogue-turn`, `.atr-chat-line`, chat paragraph, Facebook-style comment, and speaker-label region against the source HTML.

Confirm:

* The number and order of dialogue turns match the source, except for intentional Prompt 8 cleanup.
* Every speaker label matches the corresponding source speaker.
* Tagged names inside a paragraph are not mistaken as speakers.
* Final dialogue sections are checked especially carefully, because Facebook-style comments often cause speaker corruption.
* No same-speaker adjacent dialogue-turns remain unless they are truly separate source turns and intentionally preserved.
* If multiple source lines are merged, sentence boundaries, punctuation, capitalization, and spacing are repaired.
* No speaker label is accidentally absorbed into the previous paragraph.
* No source-language residue remains inside ordinary dialogue prose unless protected by the whitelist in Section 16.

---

## 12. Line-merge / punctuation audit

Check the whole covered range for:

* Missing sentence-ending punctuation after merged lines.
* Missing capitalization after sentence breaks in English retained labels/titles.
* Missing spaces after ellipses/full stops in retained English.
* Malformed punctuation such as “? !”, “! !”, “? ? ?”, doubled punctuation inappropriate for `TARGET_LANGUAGE`, or repeated punctuation caused by line merging.
* Damaged URL text such as `facebook. com`, `blogspot. com`, `index. php`.
* Sentence fragments caused by line merging.
* Speaker labels accidentally absorbed into the previous paragraph.
* Source-language punctuation patterns left in target-language prose where target-language punctuation should be used.
* Hybrid punctuation around protected English labels; retain labels if needed but make the sentence natural in `TARGET_LANGUAGE`.

---

## 13. Prompt 6 / Prompt 9 terminology audit

After translation, run a full terminology and doctrinal review, not just a mechanical translation check.

Important hierarchy:

* The uploaded English source controls meaning.
* Prompt A / Prompt 1 / Prompt 6 control source discipline.
* The target-language termbank in the uploaded prompt pack controls where applicable.
* The additional `TARGET_LANGUAGE_TERMBANK` below is a house-style preference, not permission to override source context.
* If the house-style termbank conflicts with Prompt A / Prompt 1 / Prompt 6 or the source context, the prompt pack and source context control.

### Target-language termbank module

Apply the following only if relevant to `TARGET_LANGUAGE`.

If translating into Simplified Chinese or Traditional Chinese, apply this Chinese-specific module:

* view = use context. For Soh / AtR doctrinal prose, translate general “view” as 知见 by default, especially in phrases such as lack of view, refine one’s view, clear view, view and experience, one-mind view, substance/essence view, and view as framework/paradigm/stance. Do not use 见地 as the default for “view” in Soh / AtR prose.
* Use 见 / 见地 only when the source is explicitly a Tibetan lta ba / formal “View” title or when the user explicitly requests that register.
* Retain fixed canonical compounds where appropriate: 正见、邪见、我见、身见、自性见、实有见、真我见、常见、断见、一见、异见、妄见.
* wrong view = 错误知见 or 邪见 depending source/register.
* right view = 正见.
* view aspect = 知见层面 when the source means the level/aspect of understanding; use 见地层面 if the source context is doctrinal View.
* agent = 主宰者 where the source means a controller/doer; otherwise translate by context.
* agency = 主宰性 where the source means controlling agency; otherwise translate by context.
* action = 行动 / 作用 depending on context.
* subject-action-object = 主体—行动—客体.
* inherent existence = 自性存在 / 实有 depending on context.
* inherentness = 自性 / 实有性 depending on context.
* reification = 实体化.
* constructs = 构造 / 概念构造 / 心理构造 depending on context.
* mental proliferation / conceptual proliferation = 戏论（概念增殖） when referring to prapañca/papañca; preserve 造作 when the source explicitly says fabrication/constructing/造作.
* thought realm = 意界, not 念头界.
* mind-door = 意门.
* physicality = 物理性.
* self enquiry = 自我参究.
* luminosity = 明耀 / 明性 / 光明性 depending on context; avoid casual 光辉.
* manifestation = 显现.
* pure seeing = 纯粹的看见, not 纯粹的见.
* awareness/consciousness/knowing/mindfulness: translate contextually as 觉知 / 意识 / 明知 / 正念 / 知 / 识; do not flatten all usages into one Chinese term.
* vidyā / rig pa = 明 / 明知 as source context requires; never ordinary 知识.
* ye shes / jñāna = 本初觉智 / 智慧 depending context.
* shes pa / vijñāna / consciousness = 识 / 意识 / 觉知 depending context.
* phenomena in formal Dharma contexts = 诸法, not mechanically 诸现象.
* total exertion = preserve the prompt-pack/source-context-approved rendering; do not mechanically use 全体作用 unless the prompt pack explicitly requires it.
* doer / doership / no-doership = translate by context; preserve doctrinal contrast between doing, doer, agency, and non-doership.

Chinese-specific forbidden or high-risk renderings:

* Do not use 能作者 for agent.
* Do not use 苏维宇. Use “Soh Wei Yu” or “Soh.”
* Do not use 念头界 for thought realm.
* Do not use 错误的见 for wrong view.
* Avoid 固有存在 / 固有性 when the doctrinal meaning is 自性存在 / 自性 / 实有性.
* Avoid 实有化 where 实体化 is meant.
* Do not use 知识 for vidyā / rig pa / knowledge-of-basis/state/essence contexts.
* Do not translate Dzogchen “View” mechanically as 知见 when the technical View/lta ba is meant.
* Do not translate every “effort” as 精进; use 勤作 / 努力 / 尽力 / 精进 only by source context.

For other target languages:

* Use the uploaded prompt pack’s terminology rules and any user-supplied `TARGET_LANGUAGE_TERMBANK`.
* Preserve technical labels where AtR convention requires loan terms.
* Translate ordinary English prose naturally into `TARGET_LANGUAGE`.
* Do not leave ordinary English untranslated by accident.
* Flag unresolved terminology choices for human review rather than silently normalizing them.
* Do not over-protect English terms. A protected English label may remain, but ordinary prose using the same word should be translated unless intentionally preserved.

### Universal target-language QA module

For every target language, create a compact target-language QA profile before final review. The profile must identify:

* Script family and mixed-script risks.
* Whether English source residue is visually obvious or visually hidden by shared Latin script.
* Common grammar risks for that language, such as agreement, case, gender, tense, compound formation, honorifics, particles, postpositions, or word order.
* Punctuation and quotation conventions.
* Whether Buddhist/Dharma terms are normally translated, transliterated, or preserved as Sanskrit/Pāli/Tibetan/English loan labels.
* Whether the language needs special handling for exact article titles, bilingual labels, or proper names.
* A target-language search basket for ordinary English residue and high-risk AtR/Dharma terms.
* A target-language search basket for awkward calques and line-merge damage.

For all target languages, the following distinction is mandatory:

* **Protected labels:** exact technical labels, proper names, exact article titles, and source-required quoted phrases may remain in English or Sanskrit/Pāli/Tibetan where appropriate.
* **Ordinary prose:** ordinary English prose, even when it contains words that are also technical labels in other contexts, must be translated into `TARGET_LANGUAGE` unless explicitly preserved and accounted for.

Examples of terms that may be protected as labels in some contexts but must not be overprotected in ordinary prose: Presence, Awareness, Self, No Mind, no-mind, non-dual, emptiness, view, experience, realization, practice, luminosity, consciousness, source, ground, path, agent, doer, subject, object.

### Universal target-language termbank requirement

Before or during translation, build a small working termbank for `TARGET_LANGUAGE` covering at least the high-risk AtR/Dharma terms listed below. The termbank may preserve a loan term, translate it, or use a paired translation + retained label, but each choice must be consistent with source context, the uploaded prompt pack, and target-language readability.

The working termbank must include, where relevant:

* anatta / no-self / non-self / anatman
* emptiness / empty nature
* dependent arising / dependent origination
* Presence / presence
* Awareness / awareness
* consciousness
* luminosity / clarity / vividness
* I AM / AMness
* Self / self / self/Self
* One Mind / No Mind / no-mind
* non-dual / non-duality
* subject / object / subject-object division
* agent / agency / doer / doership / non-doership
* suchness / thusness / isness
* manifestation / appearance / phenomena
* inherent existence / inherentness / essence-view
* reification / substantialist nonduality
* mirror-like awareness / mirror metaphor
* ordinariness / naturalness / spontaneity / spontaneous perfection
* total exertion
* Dzogchen / Mahamudra / rigpa / Dharma / Buddhadharma

If no stable target-language rendering is available, preserve the technical label and flag it for human review rather than inventing a confident but unsupported rendering.

Be especially careful with these AtR/Dharma terms in every target language:

* anatta / no-self / non-self
* emptiness
* Maha
* ordinariness
* spontaneous perfection
* Presence
* Awareness
* I AM / AMness
* One Mind / No Mind
* no-mind
* non-dual
* dependent arising / dependent origination
* luminosity
* appearances
* total exertion
* suchness / thusness / isness
* subject/object
* agent / doer / doership
* mirror-like awareness / mirror metaphor
* inherent existence / essence-view / substantialist nonduality
* Dzogchen / Mahamudra

Do not force all English technical terms into `TARGET_LANGUAGE` if the AtR convention is to preserve a technical loan term, but do not leave ordinary English phrases untranslated by accident. Preserve quoted English technical labels visibly as labels, not ordinary target-language prose.

---

## 14. Audit requirement for every return

Compare against the uploaded source HTML segment covered so far and confirm:

* Top-level element / major wrapper structure covered so far.
* Tag/class structure preservation.
* Dialogue speaker-label preservation.
* Links/hrefs preserved exactly.
* Src/media preserved exactly.
* CSS/style block preserved unless intentionally updated by the styling prompt.
* Human-facing attributes translated/preserved/classified.
* No major untranslated ordinary English remains except proper names, URLs, source titles, and intentional technical labels.
* No target-language forbidden terms remain.
* No source-language + target-language hybrid residue remains, except explicitly protected labels with natural target-language syntax.
* No target-language text or non-source non-Latin characters entered href/src/action/CSS URL/script/config/code-like values.
* No added doctrinal glosses.
* No omissions.
* Stopping point and next source line/sentinel if incomplete.
* Whether any material edits were made in the pass.
* Whether target-language grammar, fluency, and calque risk were checked, not merely source/target structure.
* Whether the target-language search baskets and representative sampled sentences are documented in the QA/changelog.
* Correct status label under Section 9 and Section 16.

---

## 15. Final return

When the translation reaches the original article ending:

1. Return one complete full translated HTML file.
2. State that it reaches the original article ending.
3. Run Prompt 6-style review before final status.
4. Run Prompt 9 whole-document refinement after Prompt 6 if the pack calls for it.
5. Run Strict HTML QA / Blogger Formatting checks if the pack routes final AtR Blogger presentation through them.
6. Run the Section 16 hard final-gate module.
6a. Run the adversarial target-language Prompt 6/9 defect-hunt module in Sections 16.11–16.16, including at least the required high-risk sentence sampling and search-basket evidence.
7. Produce:

   * Updated `TARGET_LANGUAGE` HTML.
   * QA / changelog TXT.
   * ZIP bundle containing both.
   * A short chat summary with the correct status label.

8. Do not claim strict-certified final.
9. Do not promote to reviewed/publishable in the same pass where the translation or any material correction was made.
10. If material edits were made in the final translation/review pass, status must remain:

“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.”

11. If I later say “continue,” reopen the exact latest artifact and perform a no-repair promotion attempt. If no material edits are made, then and only then use:

“reviewed final / publishable — strict-certified final not claimed.”

Begin by reading the uploaded prompt pack, identifying which prompt rules govern the workflow, explicitly stating how Prompt A, Prompt 1, Prompt 6, and Prompt 9 will be applied, and then proceed with the translation into `TARGET_LANGUAGE`.

---

## 16. Hard Final-Gate Module — No QA-by-Assertion, Residue Regression, and No-Repair Promotion Discipline

This section is mandatory for every checkpoint, repair pass, final pass, and promotion pass.

### 16.1 No QA-by-assertion rule

Do not claim “reviewed,” “publishable,” “final,” “complete,” “material gates pass,” “ready,” “certified,” or equivalent status merely because you say Prompt A / Prompt 1 / Prompt 6 / Prompt 9 / Strict HTML QA was applied.

A status claim is valid only if it follows a fresh audit of the exact latest artifact.

Do not substitute confidence language for verification.

If a check was not actually performed, state:

“Not fully verified: [specific check]. Human review required.”

### 16.2 Exact-latest-artifact rule

Every repair, review, audit, and no-repair promotion pass must reopen and operate on the exact latest HTML/text artifact.

Do not rely on memory, previous summaries, previous QA notes, prior confidence, file names alone, an earlier artifact, or a partially updated draft.

If there is ambiguity about which artifact is latest, do not promote. Use the most recent explicit user-provided or tool-created artifact and say which one was used.

### 16.3 Material repair invalidates promotion

If any material edit is made during a pass, the artifact cannot be promoted in that same pass.

Material edits include, but are not limited to:

* translation correction
* source-language residue cleanup
* mixed-language hybrid repair
* href/src repair
* URL slug repair
* omitted-section restoration
* duplicated-section removal
* doctrinal terminology repair
* speaker attribution repair
* punctuation repair that affects meaning or readability
* paragraph/list/blockquote/section restoration
* HTML structure repair
* media/embed repair
* attribute repair
* title/link-text repair
* CSS or wrapper repair that changes rendered output

If any material edit is made, status must be:

“REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.”

Only a later separate pass that reopens the exact latest repaired artifact and makes no material edits may promote to:

“reviewed final / publishable — strict-certified final not claimed.”

### 16.4 Protected-English whitelist gate

Before scanning for source-language residue, create or infer a protected-English whitelist.

English may remain only if it is one of the following:

1. URL or code.
2. HTML/CSS/JS attribute name, selector, class, ID, property, function name, variable name, or config value.
3. Proper name or author/person/group name.
4. Exact linked article title intentionally preserved as a title.
5. Quoted technical label intentionally preserved, such as:

   * I AM
   * AMness
   * anatta
   * anatman
   * Dzogchen
   * Mahamudra
   * Brahman
   * Sunyata
   * Maha
   * self/Self
   * Presence
   * Awareness
   * One Mind
   * No Mind
   * no-mind
   * non-dual
   * rigpa
   * Dharma
   * Buddhadharma
   * another explicitly protected AtR/Dharma label

6. Bilingual navigation label intentionally retained, such as “Bengali Version,” if the multilingual list requires it.
7. A quoted original phrase that the source requires preserving.

Everything else is ordinary source-language residue and must be translated or explicitly flagged for human review.

Important:
Do not overprotect ordinary lowercase uses of otherwise protected terms. For example, “Presence” as a technical label may remain if intentionally protected, but ordinary prose uses of “presence” should normally be translated in a non-English target-language article.

### 16.5 Mandatory source-language residue scan

Before any no-repair promotion, scan visible text for:

1. Ordinary English words embedded in target-language prose.
2. English + target-language hybrid particles or suffixes, such as:

   * term-এর
   * term-কে
   * term-তে
   * term-এরই
   * term-ও
   * term and term
   * term বা
   * term নয়
   * term হলো

   where the English term is not protected.

3. Lowercase ordinary English words, including but not limited to:

   * experience
   * realization
   * insight
   * practice
   * view
   * emptiness
   * awareness
   * consciousness
   * manifestation
   * phenomena
   * absolute
   * ultimate
   * mind
   * presence
   * sound
   * taste
   * vivid
   * ontological
   * dualistic
   * non-conceptual
   * meditation
   * teaching
   * guide
   * path
   * ground
   * source
   * self
   * no-self
   * non-self
   * dependent
   * origination
   * arising
   * luminosity
   * clarity
   * naturalness
   * ordinariness
   * spontaneity
   * subject
   * object
   * agent
   * doer
   * doership

4. Corrupted mixed-script words.
5. Accidental translation of exact article titles that should remain exact titles.
6. Accidental preservation of ordinary English prose that should be translated.
7. Residual English punctuation patterns caused by line merging.
8. Untranslated source tail after a translated section.

If any material residue is found and repaired, do not promote in the same pass.

For target languages other than Bengali, adapt the hybrid-pattern scan to the relevant target-language particles, suffixes, postpositions, inflections, punctuation, and script-mixing risks.

### 16.6 Href/src and attribute integrity gate

Before promotion, compare source and target HTML for:

1. Raw href count.
2. Raw src count.
3. Exact href values.
4. Exact src values.
5. Non-Latin characters inside href/src/action/data-url/style URL values unless present in the source URL.
6. Spaces inserted into URLs, such as:

   * blogspot. com
   * facebook. com
   * index. php
   * youtube. com
   * awakeningtoreality. com

7. Translated URL slugs.
8. Missing links.
9. Duplicated links.
10. Changed iframe config values.
11. Changed script/config values.
12. Any added link must be explicitly accounted for.

Do not translate or mutate:

* URL paths
* href values
* src values
* iframe config values
* CSS URLs
* script values
* IDs
* classes
* selectors
* code-like attributes
* JavaScript/config values
* Blogger widget identifiers

Human-facing attributes such as `alt`, `title`, `aria-label`, `placeholder`, iframe `title`, and caption-like data attributes may be translated only when they are user-facing language and not code, URL, exact title, proper name, or protected label.

Any non-source href/src change is a material defect unless explicitly requested by the user.

### 16.7 Coverage and structure gate

Before promotion, compare source and target for:

1. Major section/stage count.
2. Heading sequence and order.
3. Paragraph count, allowing only explicitly accounted additions such as the required English-original top link.
4. Blockquote count.
5. List-item count.
6. Dialogue/speaker-turn count where applicable.
7. Table count and row/column preservation where applicable.
8. Media/embed count.
9. Article ending reached.
10. Style block closed before article body.
11. No untranslated source tail remains hidden after the translated article.
12. No duplicated translated blocks.
13. No dropped links inside paragraphs.
14. No dropped parenthetical notes.
15. No speaker labels absorbed into previous paragraphs.
16. No ordinary text accidentally placed inside CSS/script blocks.
17. No CSS/script code accidentally translated.

Any missing, duplicated, reordered, or structurally corrupted section is a material defect.

### 16.8 Risk-basket regression rule

Every discovered defect must be added to a session-specific risk basket.

The next review pass must scan globally for the same defect type, not only repair the single instance.

Examples:

1. If one English+Bengali hybrid like “dependent origination-এর” is found, scan globally for all English + Bengali suffix/particle patterns.
2. If one target-language word appears inside `href`, scan all href/src/action/data-url/style URL values for non-source non-Latin characters and translated slugs.
3. If one exact linked title is partially translated, scan all exact linked titles.
4. If one dropped paragraph is restored, rerun section/paragraph/list/blockquote coverage checks.
5. If one protected term is overprotected, scan for ordinary lowercase uses of that same word in prose.
6. If one source-language residue phrase remains, scan for synonyms and related residue terms in the whole document.
7. If one punctuation/line-merge defect is found, scan all nearby merged lines, list items, and blockquotes.
8. If one speaker attribution issue is found, rerun all speaker-turn/order checks.

The risk basket must be cumulative within the session.

### 16.9 No-repair promotion checklist

A no-repair promotion pass must satisfy all of the following:

1. Reopen exact latest artifact.
2. Run visible-text residue scan.
3. Run protected-English whitelist classification.
4. Run href/src parity check.
5. Run non-Latin-in-URL scan.
6. Run translated-URL-slug scan.
7. Run section/heading/paragraph/list/blockquote/media coverage checks.
8. Run dialogue/speaker-turn checks where applicable.
9. Run terminology risk basket.
10. Run line-merge/punctuation audit.
11. Make no material edits.
12. Produce QA notes stating:

   * artifact reviewed
   * source artifact used
   * checks performed
   * exceptions remaining
   * whether any material edit was made

Only then may the status be:

“reviewed final / publishable — strict-certified final not claimed.”

### 16.10 Required hard-gate audit report

Every final, review, repair, or promotion response must report:

* source artifact used
* target artifact used
* covered source range
* first and last source sentinel
* next source sentinel if incomplete
* style block closed before article body
* major section/stage count
* paragraph count comparison
* blockquote count comparison
* list-item count comparison
* href count comparison
* src/media count comparison
* extra links accounted for
* non-Latin-in-URL scan result
* translated-URL-slug scan result
* source-language residue scan result
* mixed-language hybrid scan result
* target-language fluency/calque/grammar scan result
* protected-English whitelist used
* residue / terminology / calque search baskets used
* representative high-risk sentence sampling performed
* risk basket scan result
* whether material edits were made
* correct status label

If any item cannot be verified, state it as not fully verified and do not claim it passed.


### 16.11 Adversarial Prompt 6/9 defect-hunt module

Before any final or no-repair promotion status, perform an adversarial review whose purpose is to find defects, not to confirm previous QA.

This pass must explicitly check:

1. Semantic fidelity against the English source.
2. Doctrinal terminology accuracy.
3. Ordinary source-language residue.
4. Mixed source-language + target-language hybrid residue.
5. Overprotected English labels that should have been translated in ordinary prose.
6. Exact article-title handling.
7. Punctuation and line-merge damage.
8. Target-language grammar, agreement, case/gender/number, tense, register, and naturalness.
9. Overliteral calques that are grammatical but unnatural or doctrinally misleading.
10. Blockquotes, bold sections, italic notes, parentheticals, captions, link text, and end sections, because these are common places where earlier QA misses defects.

A no-repair promotion cannot rely mainly on counts such as paragraph count, href count, blockquote count, or section count. These are necessary but insufficient.

### 16.12 Evidence-based promotion rule

Every no-repair promotion attempt must include an evidence log in the QA/changelog. The evidence log must list:

* exact latest target artifact reopened
* source artifact used
* target-language risk profile used
* protected-English whitelist used
* ordinary English/source-language residue search basket used
* high-risk AtR/Dharma terminology basket used
* target-language calque/grammar/punctuation basket used
* href/src/code integrity checks used
* representative high-risk source/target sentence samples reviewed
* issue families from the cumulative risk basket and the result of each scan
* whether any material edits were made

Do not merely state “scan passed.” State what was scanned for.

### 16.13 Required high-risk sentence sampling

For each final, repair, or promotion pass, review a minimum set of high-risk sentences manually against the source. If the document is short, sample proportionally but do not skip this requirement.

For a full article, sample at least:

* 5 sentences from the beginning/opening sections.
* 5 sentences from the middle sections.
* 5 sentences from the ending sections.
* 5 sentences from blockquotes or quoted teaching passages.
* 5 sentences from bold/italic/commentary sections.
* all sentences containing the most important AtR/Dharma terms for the article, or a representative set if there are too many.

For each sampled sentence, check meaning, terminology, grammar, punctuation, and target-language naturalness. If any material issue is found, scan globally for that issue family.

### 16.14 Second-reader mode

In every no-repair promotion pass, read the target artifact as if it were produced by another translator whose work may contain subtle errors.

Do not trust:

* previous status labels
* previous QA summaries
* previous confidence language
* file names such as “final,” “reviewed,” or “no-repair”
* mechanical parity alone
* your own memory of earlier repairs

Reopen the exact latest artifact and challenge it from scratch.

### 16.15 False-promotion retraction rule

If a later pass finds material defects after an earlier no-repair promotion, explicitly acknowledge that the previous promotion was premature. Do not minimize the issue by saying the later pass is merely “extra refinement” if the defect affects translation fidelity, readability, terminology, HTML integrity, source-language residue, mixed-language residue, line-merge punctuation, or target-language grammar.

When this happens:

1. Reset status to “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.”
2. Add the defect family to the risk basket.
3. Scan globally for related defects.
4. Record the false-promotion lesson in the QA/changelog.
5. Require a later separate no-repair promotion pass before any publishable status may be restored.

### 16.16 Target-language fluency is a material gate

A translation can preserve HTML structure and still fail Prompt 9 if the target-language prose is unnatural, ungrammatical, overliteral, or doctrinally misleading.

Treat the following as material defects when they affect readability, source meaning, or doctrinal clarity:

* awkward literal calques from English
* broken compounds
* unnatural word order
* agreement/case/gender/number errors
* missing punctuation after merged lines
* accidental double negatives
* malformed rhetorical questions
* mistranslated idioms
* source-language sentence structure that sounds foreign in `TARGET_LANGUAGE`
* inconsistent rendering of key terms
* failure to distinguish technical labels from ordinary prose
* preserving English where the target language needs translation

If such defects are repaired, do not promote in the same pass.

---

## 17. Artifact requirements

For every completed checkpoint, repair pass, final pass, or no-repair promotion pass, produce:

1. Updated full `TARGET_LANGUAGE` HTML file.
2. QA / changelog TXT file, including the Prompt Application Ledger, hard-gate audit report, target-language risk profile, search baskets used, representative high-risk sentence sampling notes, material edits made, and status label.
3. ZIP bundle containing the HTML and QA TXT.
4. Short chat summary with:
   * Prompt Application Ledger
   * status label
   * links to the files
   * human-review notes

Do not produce fragment-only files unless I explicitly request a fragment.

If the article is incomplete, the HTML file must still be a valid cumulative Blogger-ready HTML file containing all translated content so far and excluding later untranslated source-body content.

---

## 18. Human-review placeholders and known exceptions

If `SOURCE_ARTICLE_URL` is not provided, use:

`URL_NEEDED_HUMAN_REVIEW`

Do not invent the source URL.

Flag this in every QA report until resolved.

Any unresolved terminology, source ambiguity, missing source URL, inaccessible prompt-pack detail, or unperformed check must be listed under:

“Known Human-Review Items”

Do not hide known exceptions behind a “final” status.

---

## 19. Final instruction

Begin by reading the uploaded prompt pack, identifying which prompt rules govern the workflow, and explicitly stating how Prompt A, Prompt 1, Prompt 6, Prompt 9, Prompt 8 if relevant, Blogger Formatting / Strict HTML QA if routed, and the Section 16 Hard Final-Gate Module will be applied.

Then proceed with the translation into `TARGET_LANGUAGE`.

Remember:

* The uploaded English HTML is the source.
* The prompt pack controls workflow.
* The initial translation is not publishable-final in the same pass.
* A material repair pass is not a no-repair promotion pass.
* No publishable status is allowed unless the exact latest artifact is reopened, hard-gate audited, adversarially reviewed under Prompt 6/9, target-language fluency-checked, evidence-logged, and no material edits are made.

---

## 20. Practical anti-false-final operating checklist

Use this checklist before every final or promotion response:

1. Did I reopen the exact latest target artifact rather than relying on memory?
2. Did I compare it against the uploaded English source, not a live page or prior translation?
3. Did I run Prompt 6 for fidelity, terminology, omissions, additions, doctrinal nuance, source-language residue, mixed-language residue, exact-title handling, and HTML preservation?
4. Did I run Prompt 9 for whole-document target-language fluency, grammar, punctuation, line-merge damage, readability, and consistency?
5. Did I run structure/count checks without mistaking them for translation-quality proof?
6. Did I create or update the protected-English whitelist?
7. Did I search for ordinary English/source-language residue outside the whitelist?
8. Did I search for target-language-specific hybrid residue and mixed-script damage?
9. Did I search href/src/action/CSS URL/script/config/code-like values for mutation, translated slugs, spaces, or non-source characters?
10. Did I review high-risk Dharma terminology and distinguish protected labels from ordinary prose?
11. Did I perform high-risk sentence sampling from beginning, middle, ending, blockquotes, and commentary/bold/italic sections?
12. Did I scan the cumulative risk basket from all previous defects found in this session?
13. Did I avoid claiming “publishable” in the same pass as a material edit?
14. If no material edit was made, did I document the evidence that justifies no-repair promotion?
15. If a later review found defects after prior promotion, did I clearly retract the earlier premature promotion and add the issue family to the risk basket?

If any answer is “no,” do not promote. Complete the missing check or state it as not fully verified and require human review.