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 — TARGET-LANGUAGE-FIRST TECHNICAL TERMS / TOTAL EXERTION / QA STRUCTURAL HARDENING — 23 June 2026

This Batch84 patch applies across the full AtR translation, review, Prompt 1 strict HTML preservation, Prompt 6 adversarial review, Prompt 9 final/publishable QA, language-specific gates, formatter prompts, upload/publishing/controller prompts, prompt-manager workflows, termbank prompts, link handling, dialogue preservation, and final artifact promotion. It applies to all target languages, not only Arabic.

1. TARGET-LANGUAGE-FIRST TECHNICAL TERM RULE
For all languages, technical Dharma terms must not be left as bare English/Pāli/Sanskrit/Tibetan labels inside target-language grammar unless the language-specific termbank explicitly says that this is the accepted running form. Use the target-language running term by default. Preserve the source label only in parentheses where useful, especially at first use, in headings, or where the source term is doctrinally important. Do not glue English/Pāli/Sanskrit labels into target-language grammar with target-language prefixes or suffixes.

This applies to terms including 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, and similar AtR/Dharma technical labels.

For each language, the termbank may define whether the default running form is translated, transliterated, or mixed. The chosen form must be natural in target-language grammar.

Arabic examples for this rule: use اللاذات as the running form for anatta, with اللاذات (anatta) or اللاذات (Anatta) where useful; use الآتمان (Atman), الدارما البوذية (Buddhadharma), زن سوتو (Soto Zen), and «أنا أكون» (I AM). Avoid bare anatta, Atman, Buddhadharma, Soto Zen, or I AM mechanically embedded inside ordinary Arabic grammar.

2. PROTECTED-TERM OVERRIDE: DŌGEN / ZEN “TOTAL EXERTION”
Treat “Total Exertion” as a protected Dōgen/Zen technical term, including in AtR article titles and source passages connected with gujin. Do not translate it with ordinary dictionary terms meaning depletion, exhaustion, spending, draining, overexertion, or merely personal effort/devotion. If the language-specific termbank has an approved translation, use it. If not, preserve the English technical term, optionally with normal target-language transliteration.

Arabic artifact/default approved form: توتال إكسيرشن (Total Exertion). Do not use الاستنفاذ الكلي, because it means depletion/exhaustion. Do not automatically add explanatory first-use notes unless the user explicitly asks for them. If a project-specific prompt requires a note, keep it short and do not expand or editorialize beyond the source.

3. IDIOM AND CONTEXT ADVERSARIAL GATE
Prompt 6 and Prompt 9 must check that apparently simple English phrases are translated according to context, not word-by-word. In psychological/spiritual realization contexts, “saw the same thing” may mean “understood/experienced/recognized the same experience or insight,” not seeing the same physical object.

Arabic preferred pattern for “Nobody around me saw the same thing or got mad if I talked about it”: لم يكن أحدٌ حولي يعيش التجربة ذاتها، ولم يكن أحدٌ يغضب إن تحدّثتُ عنها.

Also run a negative-coordination check: English “Nobody X or Y” often means “Nobody X, and nobody Y,” not “Nobody X, or they Y.” Do not create awkward “or they got mad” structures.

4. UNIVERSAL SLASH-CALQUE GATE
In ordinary running prose, do not mechanically preserve English slash pairs such as subject/object, perceiver/perceived, self/Self, no-self/Self, agent/action, concepts/thinking, Awareness/Consciousness, Who/What am I?, Soto Zen/Dōgen, or Eight Negations / Middle Way negation. Use natural target-language coordination such as “and,” “or,” “between X and Y,” or a parenthetical source label. Preserve slash only when it is part of an exact title, exact formula, filename, code, URL, or deliberately protected technical label.

Arabic examples: من أو ما أنا؟, not من/ما أنا؟; الوعي أو الإدراك, not الوعي/الإدراك; الذات أو الفاعل المستقل, not ذات/فاعل مستقل; زن سوتو ودوجن, not Soto Zen/Dōgen in ordinary Arabic prose.

5. LINK-BOUND SENTENCE QA
For every anchor tag, preserve href exactly unless the user explicitly requests link changes. Preserve the correct anchor boundary: link text must not swallow neighboring sentence text, punctuation, or adjacent links. If source link text is an English article title and the target artifact translates link text, the surrounding sentence must still read naturally. If an exact title must remain English, do not glue it awkwardly into target-language grammar; use natural framing around it.

Adversarial check: read the whole sentence containing each link, not just the linked text. If the sentence sounds like “when [linked title] is penetrated…” or another unnatural construction, repair the surrounding syntax while preserving the href.

6. DOM-LEVEL HTML STRUCTURE PRESERVATION
Prompt 6 and Prompt 9 require DOM-level structural checks, not only visual or text checks. Verify that style blocks are preserved and not converted into visible text; CSS is preserved unless explicitly asked to change; src and href parity is preserved except intentional additions such as a required English-original link; blockquote counts and boundaries are preserved; dialogue-card counts and speaker boundaries are preserved; headings, list items, source blocks, “Also see” cards, and update sections remain structurally aligned; no invalid nesting such as p inside span; no duplicated nested anchors; no source URL converted to plain text; no missing or duplicated source-link instances; and no section merging across source paragraph/card boundaries.

If material HTML structure is repaired, status remains “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required” until a later no-material-change pass.

7. VISIBLE-TEXT SPACING AND PUNCTUATION QA
Prompt 9 must include a final visible-text scan for non-source non-breaking spaces in visible prose, punctuation glued to words, missing spaces after punctuation, awkward spacing around parentheses, target-language punctuation mixed incorrectly with Latin terms, line-merge defects such as “word.word” or “واقعهم.ينبغي”, and link-adjacent punctuation defects. Apply the target language’s punctuation norms.

8. LANGUAGE-SPECIFIC TERMBANK PRIORITY / REVIEWER OVERRIDES
If a native speaker or reviewer supplies a correction during the session, treat it as a language-specific override for the artifact and apply it consistently across all relevant occurrences unless it contradicts a higher-priority project rule. Search the whole artifact for related instances, not only the cited sentence. Update title, headings, body, cards, and repeated references consistently. Document exactly what was changed.

Examples: Arabic anatta default: اللاذات. Arabic Total Exertion for this article: توتال إكسيرشن (Total Exertion). Arabic “saw the same thing” in psychological/spiritual context: يعيش التجربة ذاتها or equivalent, not يرى الشيء نفسه.

9. SOURCE-LABEL RESIDUE SCAN
Before declaring publishable, scan for remaining bare source labels in target-language prose: capitalized English technical terms, Pāli/Sanskrit terms, source labels with target-language prefixes/suffixes, mixed source/target slash forms, and source terms repeated many times where only first-use parenthetical retention is appropriate. Distinguish exact article titles, proper names, URLs, code/file names, deliberately preserved English labels, and protected originals from accidental residue in ordinary prose.

10. STATUS PROMOTION DISCIPLINE
If a review pass makes any material visible-text, terminology, link, or HTML-structure repair, the artifact must not be promoted to publishable in that same pass. Use: REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.

Only after a subsequent full Prompt 6 + Prompt 9 pass finds no material issues and makes no visible-text or HTML edits may the status become: reviewed final / publishable — strict-certified final not claimed.

11. DO NOT OVERCORRECT PROTECTED ORIGINALS
Do not “fix” source terms intentionally preserved due to proper names, exact article titles, original-language quotations, scripture names, URLs, technical labels the termbank says to preserve, or user-specific overrides. Even preserved terms must be integrated naturally into the target-language sentence.

12. PROMPT 9 FINAL AUDIT CHECKLIST
Before producing final files, Prompt 9 must internally check and, where useful, externally summarize: required English-original link present when requested; href parity; src parity; CSS/style block preservation; article root directionality and language attributes; image count; blockquote count; dialogue-card count and speaker boundaries; source-tail cards / “Also see” structure; no invalid nesting; no duplicate nested anchors; no non-source NBSPs in visible text; no line-merge punctuation defects; no ordinary slash-calques; no bare technical source-label residue in running prose; language-specific termbank compliance; and prior-session reviewer corrections applied consistently.

MANDATORY QA / CHANGELOG LINES FOR RELEVANT PASSES
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.

BATCH 82 — CHINESE UNIVERSAL AWARENESS / UNIVERSAL CONSCIOUSNESS TERMINOLOGY LOCK — 21 June 2026

This Batch84 patch applies across the full AtR translation, review, QA, adversarial audit, formatter, publishing/controller, prompt-manager, packaging, Cloudflare, Blogger, and handoff workflows wherever English source terms such as “universal awareness” or “universal consciousness” are translated, reviewed, or validated into Chinese.

For Chinese target text, prefer 宇宙意识 (traditional: 宇宙意識) for “universal awareness” / “universal consciousness” when the context concerns AtR / John Tan critiques of a reified cosmic or universal consciousness, a shared One Mind, or a universal/cosmic awareness view. Do not use 普遍意识, 普遍觉知, 普遍意識, or 普遍覺知 for this Dharma/philosophical sense unless the source clearly means merely ordinary “generally applicable awareness” rather than a cosmic/universal consciousness view.

This rule is terminological, not doctrinal endorsement: when the source is critiquing “universal awareness / universal consciousness,” translating it as 宇宙意识 preserves the object of critique; it must not make the reified view sound doctrinally approved.

PROMPT 6 / PROMPT 9 / QA REQUIREMENT
During Chinese-related translation, review, no-repair promotion, formatter readback, Strict HTML QA, prompt-manager, or controller validation, explicitly scan for 普遍意识 / 普遍觉知 / 普遍意識 / 普遍覺知 used for “universal awareness” or “universal consciousness.” Repair to 宇宙意识 / 宇宙意識 unless the sentence clearly means ordinary general applicability.

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

BATCH 80 — HERO TITLE TEXT-WRAP REPAIR — 16 June 2026

Scope: targeted formatter / Strict HTML QA / publishing-controller maintenance update on top of Batch79. This update does not change the Batch77 agent/efforting/mental-chatter gates, Batch78 nondual-identity/blah-idiom gates, or Batch79 thought-watching-thought/no-hidden-witness gate.

Repair: Long hero titles must not be squeezed into poster-style vertical stacking by aggressive text-wrap balancing. For very long .long-title hero h1 elements, use the v5.8.21 CSS: lower font cap, line-height 1.05, max-width 100%, text-wrap: initial !important on desktop, and text-wrap: pretty !important on mobile.

Strict QA: HERO TITLE OPTICAL SIZING AUDIT must fail if a long hero title wraps into many tiny phrase fragments due to narrow hero/card width or aggressive balancing. Correct by applying .long-title, reducing the font cap, and setting text-wrap: initial !important.


 Batch77

BATCH 79 — THOUGHT-WATCHING-THOUGHT / NO-HIDDEN-WITNESS HARDENING — 14 June 2026

This Batch79 patch is universal. It applies to all AtR / John Tan translation, review, refinement, adversarial audit, formatting, Strict QA, no-repair promotion, packaging, upload-controller, prompt-manager, and handoff workflows. It applies across all target languages, not only Arabic, Indonesian, or Chinese. It does not weaken Batch78 nondual-identity and informal-idiom hardening; Batch77 agent/doer, efforting, and mental-chatter false-friend hardening; Batch76 high-risk Buddhist term preservation and local doctrinal contamination gates; Batch75 materiality/anti-churn; Batch74 exact-artifact/false-pass; Batch73 Presence/hybrid-residue; Batch71 Witness/sākṣī; Prompt T; Prompt X; Blogger HTML; href/src/code; or status-discipline safeguards.

CORE LESSON
In central AtR / John Tan / anatta passages, “thought watching thought rather than a watcher watching thought” must not become “mind witnesses mind,” “mind observes mind,” “awareness witnesses thoughts,” or “consciousness watches thoughts.” The doctrinal point is not that a subtler Mind, Witness, Awareness, observer, knower, or subject is watching thoughts. The point is that no separate watcher is found: what is called “the watcher” is itself only that thought, or one thought-moment followed by another thought-moment.

THOUGHT-WATCHING-THOUGHT / NO-HIDDEN-WITNESS GATE
For AtR / John Tan / anatta passages such as “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!,” and related passages involving watcher, observer, witness, knower, thinker, seer, hearer, mind, thought, awareness, consciousness, or subject, do not translate into wording that implies any of the following:
- mind witnesses mind
- mind observes mind
- the witness is the mind
- the observer is the mind
- awareness witnesses thoughts
- consciousness watches thoughts
- a hidden Witness, Mind, Awareness, observer, knower, or subject behind thoughts

The contrast must remain thought versus watcher, not mind versus observer/witness. Preserve the no-hidden-witness insight as thought-after-thought, one thought observing another thought, or thought watching thought. What is called “the watcher” is only that very thought, not a background mind, witness, awareness, consciousness, or subject.

DISAMBIGUATION RULE WHEN TARGET LANGUAGE BLURS “THOUGHT” AND “MIND”
If the target language uses the same or overlapping word for both “thought” and “mind,” the translator must disambiguate. Use a phrase equivalent to one of the following rather than leaving a hidden-subject ambiguity:
- 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

If a literal translation remains vulnerable to a hidden-subject reading, add a small clarifying phrase within the translation rather than preserving ambiguity.

LANGUAGE-SPECIFIC EXAMPLES
Indonesian: avoid ambiguous formulations such as batin menyaksikan batin, pikiran menyaksikan pikiran, pengamat adalah batin, penyaksi adalah pikiran, or pengamat adalah pikiran itu sendiri when pikiran can be read as Mind rather than a thought. Prefer clearer forms such as 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.

Chinese: avoid formulations implying 心 / 觉知 / 意识 as a hidden subject witnessing thoughts. Prefer 念头看念头 / 一个念头看另一个念头 / 所谓的观察者只是那个念头本身, depending on naturalness.

Arabic: avoid wording implying العقل / الوعي / الشاهد as a background witness. Prefer formulations equivalent to فكرة تراقب فكرة أخرى and “the so-called watcher is only that very thought,” not “mind witnesses mind.”

PROMPT 6 / PROMPT 9 / QA BACK-TRANSLATION REQUIREMENT
During every Prompt 6, Prompt 9, Strict QA, formatter readback, no-repair promotion, packaging validation, prompt-manager, publishing/controller, or adversarial review pass, explicitly scan central anatta passages involving watcher, witness, observer, seer, hearer, thinker, knower, mind, thought, awareness, consciousness, subject, no one behind thoughts, one thought then another thought, thought watching thought, or watcher is that thought.

Run this adversarial back-translation test: could the target line naturally be back-translated as “mind watches mind,” “mind witnesses mind,” “the witness is mind,” “the observer is mind,” “awareness watches thoughts,” “consciousness witnesses thoughts,” or “a subtle subject remains behind thoughts”? If yes, repair it. Treat the issue as material because it reverses or weakens the anatta/no-hidden-witness insight.

MANDATORY QA / CHANGELOG LINE
Every relevant AtR / John Tan / anatta QA pass must include this short confirmation line:
Thought-watching-thought / no-hidden-witness gate checked: no “mind witnesses mind,” “witness is mind,” “awareness watches thought,” or hidden-subject reading remains.

STATUS DISCIPLINE
If such an issue is found and repaired, the artifact cannot be promoted in the same pass. Use: “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” Only a later exact-artifact no-material-edit pass may use: “reviewed final / publishable — strict-certified final not claimed.”

BATCH 78 — UNIVERSAL NONDUAL IDENTITY SYNTAX AND INFORMAL IDIOM/“BLAH” REGISTER HARDENING — BATCH81 REVISION / CLARIFICATION — 16 June 2026

This Batch78 rule is now clarified by Batch81. It is still universal and applies to all AtR / John Tan translation, review, refinement, adversarial audit, formatting, Strict QA, no-repair promotion, packaging, upload-controller, prompt-manager, and handoff workflows. It applies across all target languages, not only Arabic or Tamil. This clarification does not weaken Batch80 hero-title formatting repair; Batch79 thought-watching-thought/no-hidden-witness hardening; Batch77 agent/doer, efforting, and mental-chatter false-friend hardening; Batch76 high-risk Buddhist term preservation and local doctrinal contamination gates; Batch75 materiality/anti-churn; Batch74 exact-artifact/false-pass; Batch73 Presence/hybrid-residue; Batch71 Witness/sākṣī; Prompt T; Prompt X; Blogger HTML; href/src/code; or status-discipline safeguards.

CORE LESSON
Some English nondual formulas and informal idioms are structurally dangerous when translated too literally. In anatta contexts, “In X, just Y” is compact contemplative syntax. It is not a container/location formula, but Batch78 must not be overread as forcing every language into a heavy definition such as “hearing itself is sounds,” “seeing itself is forms,” or “X means Y.” The task is subtler: preserve the source’s compact “in hearing / in seeing / in thinking, only ...” cadence where natural, while preventing any reading in which hearing, seeing, thinking, awareness, or mind becomes a container, field, stage, background, entity, or hidden subject in which phenomena appear. Likewise, informal expressions such as “blah something nice but deluded” may not be asking for a childish or comic “chattered/prattled” verb; they often function as a dismissive critique of polished but deluded conceptual or spiritual talk. Translation must preserve nondual precision, compact contemplative cadence, and publication register, not merely surface syntax.

NONDUAL IDENTITY SYNTAX GATE — “IN X, JUST Y”
For anatta/nondual lines such as “In thinking, just thoughts,” “In hearing, just sounds,” and “In seeing, just forms, shapes and colors,” preserve the source’s “in/with/at hearing, only sounds; in/with/at seeing, only colors/forms; in/with/at thinking, only thoughts” structure where that is natural in the target language. Do not translate with a target-language structure that implies a container, category, location, field, stage, background, entity, hidden subject, or subtle gap between process and object, such as “inside thinking there are thoughts,” “within hearing there are sounds,” or “in awareness/mind, sounds appear.”

This is a semantic gate, not a demand for one grammatical template. Do not overcorrect into rigid identity wording such as “X is Y,” “X itself is Y,” or “X means Y” if that changes the source tone, cadence, or doctrinal nuance. Prefer the most natural target-language form equivalent to “in/with/at hearing, only sounds,” “in/with/at seeing, only colors/forms,” and “in/with/at thinking, only thoughts,” while ensuring the wording does not imply an inner container, background observer, or hidden subject. Use a heavier identity/non-separation formulation only when the target language truly requires it to block a misleading container/background reading.

Tamil clarification: avoid கேட்பதில் எப்போதும் ஒலிகள் மட்டுமே if it reads as an inner container, “inside hearing there are sounds.” Also avoid over-heavy identity such as கேட்பது என்பது எப்போதும் ஒலிகளே or கேட்பதே எப்போதும் ஒலிகளே if it sounds like “hearing itself is sounds” rather than the source’s compact “in hearing, only sounds.” Prefer natural non-container locative/temporal Tamil such as கேட்கையில் எப்போதும் ஒலிகளே; பார்க்கையில் எப்போதும் நிறங்கள், வடிவங்கள், உருவங்களே; சிந்திக்கையில் எப்போதும் எண்ணங்களே; கேட்கையில் வெறும் ஒலியே.

Arabic-specific guidance: the earlier identity-style examples such as التفكير ليس إلا أفكارًا / السماع ليس إلا أصواتًا / الرؤية ليست إلا صورًا وأشكالًا وألوانًا remain acceptable when needed to block a locative/container reading. However, do not force them mechanically if the local sentence needs the source’s compact contemplative cadence. Avoid في التفكير، مجرد أفكار when it can read as a locative/category structure rather than a non-container “only thoughts” formula.

INFORMAL IDIOM / “BLAH” / DISMISSIVE CONCEPTUAL-TALK GATE
When the source uses informal expressions like “blah something nice but deluded,” do not translate mechanically into a target-language equivalent of “chattered,” “prattled,” or “babble” if that creates an unintended comic, childish, overly casual, or merely talkative tone.

Preserve the function: dismissing attractive but deluded conceptual talk, polished formulations, or nice-sounding spiritual language that lacks realization. All target languages should render the idiom naturally in the target register, with wording equivalent to: “uttered nice-sounding but deluded words,” “produced polished/resonant phrases, but deluded,” “spoke in attractive formulas, but still deluded,” or “gave elegant-sounding conceptual talk, but it remained deluded.”

Arabic-specific rule: prefer صاغوا عبارات رنّانة جميلة، لكنها واهمة / أطلقوا كلامًا منمقًا جميلًا لكنه واهم. Avoid ثرثروا unless the source is intentionally mocking in a very colloquial way.

PROMPT 6 / PROMPT 9 / ADVERSARIAL REVIEW REQUIREMENT
During Prompt 6, Prompt 9, Strict QA, formatter readback, package validation, no-repair promotion, prompt-manager/controller review, or any adversarial audit/review, explicitly scan every target language for both sides of the Batch78 identity-syntax gate:
1. under-protection: “In X, just Y” rendered with a locative, container, category, field, background, hidden-subject, or “inside/within there are” structure that weakens nondual non-separation;
2. overcorrection: a compact source formula forced into a heavy definitional sentence such as “X is Y,” “X itself is Y,” or “X means Y” when that changes tone, cadence, or doctrine;
3. informal English idioms such as “blah” translated too literally as chatter/prattle/babble instead of preserving their dismissive function and appropriate publication register.
If any issue changes source meaning, doctrinal clarity, nondual precision, compact contemplative cadence, or publication register, treat it as material. Repair globally, update the Source-Term Decision Table / high-risk term ledger / Change Materiality Ledger as applicable, and use: “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” Only a later exact-artifact no-material-edit pass may use: “reviewed final / publishable — strict-certified final not claimed.”

MANDATORY QA / CHANGELOG LINE
Every relevant AtR / John Tan / anatta QA pass must include this short confirmation line:
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 — UNIVERSAL AGENT/DOER, EFFORTING, AND MENTAL-CHATTER FALSE-FRIEND HARDENING — 13 June 2026

This Batch77 patch is universal. It applies to all AtR / John Tan translation, review, refinement, formatting, QA, no-repair promotion, packaging, upload-controller, and handoff workflows. It does not weaken Batch76 high-risk Buddhist term preservation, local doctrinal contamination, anti-substantialism/anti-nihilism hardening, Batch75 materiality/anti-churn, Batch74 exact-artifact/false-pass, Batch73 Presence/hybrid-residue, Batch71 Witness/sākṣī, Prompt T, Prompt X, Blogger HTML, href/src/code, or status-discipline safeguards.

CORE LESSON
In AtR / John Tan / anatta translation, ordinary dictionary senses can be false friends. “Agent” often means the presumed independent doer/controller from which action proceeds, not an intermediary or representative. “Efforting” often means contrived, self-conscious, fabricated doing, not fatigue. “Mental chattering” often means discursive/conceptual proliferation, not casual talkativeness. These terms must be handled as Dharma/philosophical risk terms whenever the surrounding context is anatta, no-self, no-doer, dependent origination, non-doership, practice, view, realization, or related AtR explanation.

AGENT / DOER / AGENCY / DOERSHIP / AGENTLESSNESS / NON-DOERSHIP GATE
In anatta, no-self, no-doer, no-doership, agentlessness, dependent origination, and related Dharma/philosophical contexts, “agent” means the presumed independent doer, actor, controller, prime mover, or entity from which action proceeds. It must not be translated as an intermediary, broker, representative, travel agent, legal agent, commercial agent, software agent, service agent, or delegated proxy unless the source clearly means that ordinary non-Dharma sense.

All target languages must choose wording that preserves the “independent doer/actor/controller” sense. Where the ordinary local word for “agent” points toward an intermediary/representative, reject it and use a gloss such as “independent agent/doer,” “independent actor/controller,” “presumed doer,” or the target-language equivalent.

Arabic-specific rule: prefer فاعل، فاعل مستقل، الفاعل، الخلوّ من الفاعل، غياب الفاعل المستقل. Avoid واسطة، وسيط، وكيل، عميل, or anything implying intermediary, representative, broker, client, commercial/legal agent, or service agent, unless the source clearly uses that ordinary sense.

EFFORTING / EFFORTLESSNESS GATE
In John Tan / AtR usage, “efforting” often means contrived, fabricated, self-conscious, artificial effort or subtle doing — the opposite of natural effortlessness. It usually does not mean exhaustion, strain, tiredness, strenuousness, or physical/mental fatigue.

All target languages must avoid translating “efforting” as “tiring,” “strenuous,” “exhausting,” or fatigue/strain unless the local sentence clearly means fatigue. Prefer wording equivalent to contrived effort, artificial effort, fabricated doing, effort accompanied by contrivance, or self-conscious efforting.

Arabic-specific rule: prefer التكلّف، جهد مصطنع، مصحوب بالتكلّف، ينطوي على جهدٍ مصطنع، متكلّف. Avoid مُجهد، مُرهق، شاق unless the source clearly means tiring, exhausting, or physically/mentally strenuous.

MENTAL CHATTERING / DISCURSIVE THOUGHT GATE
When “mental chattering” appears in AtR / Dharma explanation as a technical critique of conceptual, inferential, proliferating, or discursive thinking, do not over-literalize it into a colloquial “mind chatter” phrase if that lowers the register or makes the passage sound casual. Preserve the sense of discursive/conceptual proliferation and choose the target-language register appropriate to philosophical/Dharma discourse.

Arabic-specific rule: prefer التفكير الاستطرادي, التفكير الخطابي/المفهومي, حركة الذهن الخطابية/المفهومية. Use الثرثرة الذهنية only when the source tone is clearly informal or colloquial.

PROMPT 6 / PROMPT 9 / ADVERSARIAL REVIEW REQUIREMENT
During Prompt 6, Prompt 9, Strict QA, formatter readback, package validation, no-repair promotion, or any adversarial review, explicitly scan every target language for these false friends:
1. “agent” mistranslated as intermediary/representative/broker/proxy/service agent instead of independent doer/actor/controller;
2. “efforting” mistranslated as fatigue, tiredness, strenuousness, or exhaustion instead of contrived/self-conscious doing;
3. “mental chattering” mistranslated too colloquially when the context is technical Dharma/philosophical discourse.
If any such issue changes source meaning, doctrinal clarity, or publication register, treat it as material. Repair globally, update the Source-Term Decision Table / high-risk term ledger, and use: “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” Only a later exact-artifact no-material-edit pass may use: “reviewed final / publishable — strict-certified final not claimed.”

BATCH 76 — UNIVERSAL HIGH-RISK BUDDHIST TERM PRESERVATION + LOCAL DOCTRINAL CONTAMINATION GATE + ANTI-SUBSTANTIALISM/ANTI-NIHILISM HARDENING — 8 June 2026

This Batch76 patch is universal. It applies to all ATR translation, review, refinement, formatting, QA, no-repair promotion, packaging, upload-controller, and handoff workflows. It does not weaken Batch75 Materiality-Aware Polish/Anti-Churn, Batch74 exact-artifact/false-pass hardening, Batch73 Presence/hybrid-residue rules, Batch72 Plum Dawn/UI safeguards, or earlier Blogger chrome, href/src, no-added-gloss, no-public-translation-contamination, Prompt T, and Prompt X safeguards.

CORE LESSON
A translated Buddhist/Dharma technical term can be grammatically correct and dictionary-supported yet still be doctrinally unsafe in a target language. Local vocabulary may import creator/source-view assumptions, Sufi/Islamic, Christian, Vedāntic/Hindu, Daoist, New Age, psychological, legal, folk-religious, nihilistic, eternalist, substantialist, or metaphysical baggage. Therefore, do not automatically choose the most natural local equivalent for high-risk Dharma terms.

UNIVERSAL SOURCE-TERM DECISION GATE
Before finalizing an initial translation, and again during Prompt 6/Prompt 9/Strict QA-style review, maintain a Source-Term Decision Table for article-central high-risk terms. For each term, classify:
1. Source term.
2. Proposed target rendering.
3. Risk type: Safe translated term / Preserve original term / Preserve original term + target-language gloss / Target-language term allowed only after clarification / Reject target-language term due to doctrinal contamination.
4. Reason.
5. Final rule for this artifact.
If no safe target-language equivalent is known, preserve the English/Sanskrit/Pāli/Tibetan/AtR label and add a concise target-language explanation rather than inventing a confident local equivalent.

HIGH-RISK TERM FAMILIES
Always consider this gate for 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; and any article-specific high-risk term.

LOCAL RELIGIOUS CONTAMINATION GATE
Do not translate Buddhist terms into local religious-theological vocabulary unless the source explicitly makes that comparison. Examples that must not become hidden default translations include Sufi/Islamic terms such as fanāʾ, baqāʾ, ihsan, tawḥīd, or Allah-realization; Christian terms such as salvation, grace, Holy Spirit, Godhead, soul, or creator; Vedāntic/Hindu terms such as Brahman, Ātman, mokṣa, or īśvara; Daoist terms such as Dao, wu wei, or original qi; and New Age/psychological terms such as universal consciousness, higher self, subconscious, ego death, or pure consciousness. Such terms may appear only as explicit comparisons when the source itself makes the comparison.

ANTI-SUBSTANTIALISM / ANTI-SOURCE-VIEW GATE
For dependent origination, emptiness, Buddha-nature, Presence, Awareness, rigpa, dharmadhātu, ground, source, essence, luminosity, and related terms, check that target wording does not imply a fixed Source, origin-substance, independent ground, creator, Brahman/Ātman, eternal witness, permanent Self, metaphysical container, phenomena emerging from a self-existing base, symmetrical mutuality not present in the source, or a mere causal sequence when the source means broader dependent designation/interdependence.

ANTI-NIHILISM / ANTI-BLANK-VOID GATE
For emptiness, voidness, nothingness, absence, non-arising, no-self, cessation-related language, and similar terms, check that target wording does not imply nothing exists at all, annihilation, blank unconsciousness, dead void, mere absence, depression/meaninglessness, ontological non-being, or emptiness as a substance/place. If the local term risks nihilistic misunderstanding, preserve śūnyatā/emptiness or the relevant source label and explain: empty of intrinsic existence/self-nature, not nothingness.

PROTECTED-LABEL AND TRANSLITERATION RULE
Keep protected labels exactly when AtR/source convention requires it, especially I AM, AMness, Isness, capitalized Self, technical Presence, rigpa, vidyā, anatta/anātman when needed, Madhyamaka, śūnyatā, and dependent origination when the target-language equivalent is risky. A target-language gloss may be added, but the protected label must not be silently replaced. Do not phonetically transliterate English technical terms into the target script unless that transliteration is already a stable convention in that language and appropriate for the article. Prefer the Latin-script source label plus a target-language explanation.

RTL / MIXED-SCRIPT SAFETY
For Arabic, Hebrew, Persian, Urdu, and other RTL pages, preserve mixed Latin/Sanskrit/Pāli/Tibetan technical labels with proper directionality handling where needed. Formatter and Strict HTML QA must check that mixed-script labels render legibly and are not reordered, split, or garbled. Do not “clean up” bidi-safe spans, terminology notes, or first-use glosses as redundant.

EXPERT FEEDBACK GATE
If a native speaker or domain-informed reviewer says a target-language term causes doctrinal distortion, classify the feedback as material doctrinal risk / target-language fluency issue / optional preference / rejected suggestion. Do not dismiss it merely because the term appears in a dictionary, Wikipedia, prior translation, or online usage. If material, repair globally, update the Source-Term Decision Table, and record it in the Change Materiality Ledger.

PROMPT-SPECIFIC APPLICATION
Universal Intro and Prompt A: visibly require expert terminology warnings, Source-Term Decision Table, first-use handling, and intentional gloss logging.
Prompt 1/2/3/4/5/7/8: do not over-localize high-risk Dharma terms; preserve labels and glosses where local equivalents are unsafe; Prompt 8 must not smooth dialogue into local religious equivalents.
Prompt 6: add an adversarial Local Doctrinal Contamination / Anti-Substantialism / Anti-Nihilism review basket and scan high-risk term families globally.
Prompt 9: naturalness must not replace protected labels with locally smooth but doctrinally contaminated terms.
Prompt T and Prompt X: include anti-local-religious-contamination, protected-label preservation, and gloss-consistency checks when source-anchor or source-restoration work feeds target artifacts.
Protocol A/B and Upload Controller: require Source-Term Decision Table, terminology-protection notes, intentional glosses, expert-feedback incorporation, and material terminology repair status discipline.
Unified Blogger Formatter and Strict HTML QA: preserve terminology notes, protected labels, glosses, bidi-safe spans, and mixed-script labels; audit for protected technical labels, first-use glosses, local religious contamination, source-view/substantialism, nihilism, and directionality safety.
RemoveSegID / mechanical utilities: never alter protected technical labels, term notes, glosses, bidi spans, source labels, href/src/code, or explanatory terminology notes.

ARABIC CASE-STUDY EXAMPLES — EXAMPLES ONLY, NOT ARABIC-ONLY RULES
dependent origination should not rely solely on Arabic terms such as النشوء المعتمد / النشأة المعتمدة if reviewers warn that they imply source-view. A safer high-risk form may preserve “dependent origination (pratītyasamutpāda / paṭicca-samuppāda)” plus an Arabic explanation meaning: قيام الظواهر اعتمادًا على شروط وأسباب متداخلة، لا صدورها من أصل ثابت أو مصدر قائم بذاته.
emptiness / śūnyatā should not rely solely on الفراغ if it suggests blank void or nothingness. A safer gloss may explain: الخلوّ من الوجود الذاتي أو الطبيعة الذاتية، لا العدم ولا الفراغ بمعنى الانمحاء.
I AM remains I AM as a protected AtR stage-label, not a Sufi phrase. fanāʾ, baqāʾ, ihsan, tawḥīd, and similar Sufi/Islamic terms are not main translations for Buddhist terms unless the source explicitly compares them. Madhyamaka should not be reduced only to “Middle Way” where school-name identity matters.

MATERIALITY AND STATUS
A terminology change is material if it affects dependent origination, emptiness, anatta, Self, I AM, Presence, Awareness, rigpa, Madhyamaka, Buddha-nature, agency/doer/perceiver, or other high-risk terms. Such a pass cannot be promoted as final in the same pass. Use: “REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.” Only a later exact-artifact no-material-edit pass may use: “reviewed final / publishable — strict-certified final not claimed.”


Scope for Upload Controller: final/package status must use the hardened no-repair promotion discipline and correct Batch76 status labels.




BATCH 75 — UNIVERSAL MATERIALITY-AWARE POLISH + ANTI-CHURN HARDENING — 4 June 2026

This Batch76 patch is universal. It applies to all ATR translation, review, refinement, formatting, QA, no-repair promotion, packaging, and handoff workflows. It does not weaken any Batch74 false-pass, exact-artifact, Latin-script fluency, hybrid-residue, title/link, href/src, Blogger-chrome, or source-fidelity safeguards.

MATERIALITY-AWARE POLISH GATE
Before making any visible-text change during translation, refinement, adversarial review, repair, audit, or no-repair promotion, classify the proposed change:

A. REQUIRED REPAIR — must be fixed.
Required repairs include defects in source fidelity, omission/addition, mistranslation, doctrinal or technical term accuracy, article-central terminology consistency, speaker attribution, exact-title/link-text handling, source-language residue, mixed-language/hybrid residue, malformed retained source/Sanskrit/Pāli/Tibetan/English labels, target-language grammar, punctuation or line-merge damage, target-language readability, HTML/link/media/code integrity, and target-language naturalness where current wording sounds machine-translated, obscure, distracting, or misleading.

B. BENEFICIAL POLISH — allowed in active editing passes.
Beneficial polish is not strictly wrong but materially improves publication quality: naturalness, readability, sentence flow, public ATR Dharma-article register, reduction of translationese, clarity of difficult doctrinal points, consistency of repeated term families, idiomatic phrasing where literal wording is clunky, or smooth grammatical integration of retained technical labels. If visible text changes, the pass remains an editing/repair/refinement pass and cannot be promoted as no-repair in the same pass unless a separate no-material-edit promotion pass is then performed.

C. PREFERENTIAL REWRITE — avoid.
Do not rewrite merely because another acceptable phrasing is possible. If the current wording is source-accurate, doctrinally clear, grammatically correct, natural, termbank-consistent, publication-acceptable, and free from residue/hybrid/title/punctuation/link/HTML defects, do not churn synonyms or sentence structure.

MODE-SPECIFIC BEHAVIOR
Active translation / repair / adversarial review: required repairs must be made; beneficial polish may be made if it improves publication quality without changing source meaning or adding doctrine; preferential rewrites should normally be avoided. Record visible-text edits and keep repair/editing status.

No-repair promotion: reopen the exact latest artifact, actively search for required repairs, identify optional polish without editing it, and do not fail promotion merely because another acceptable phrasing exists. If only optional polish or preferential alternatives remain, record “optional polish only; no material repair required.” If any required repair is found, repair it and reset to the repair status.

CHANGE MATERIALITY LEDGER
For repair/adversarial-review passes, the QA/changelog must include a compact Change Materiality Ledger for representative and material visible-text changes: nearest heading/sentinel, old wording, new wording, category (Required repair / Beneficial polish / Preferential rewrite avoided), reason, and whether the change affects status. For no-repair promotion passes, report required repairs found yes/no, beneficial polish identified but not edited yes/no, preferential rewrites avoided yes/no, and material edits made yes/no.

ANTI-CHURN STOP RULE
After repeated adversarial review passes, if the exact latest artifact has no required repairs and remaining possible changes are only preferential rewrites or optional beneficial polish, stop editing. Do not reset status through synonym-level rewriting. A no-repair promotion pass may promote only after exact-artifact reopening, source comparison, terminology/residue/hybrid/title/link/href/src/structure/fluency gates, no required repair, and no visible-text material edit.

DO NOT WEAKEN STRONG QA
Continue to treat omissions, additions, mistranslations, doctrinal distortion, wrong technical terms, source-language residue, mixed-language hybrids, malformed retained labels, broken grammar, awkward translationese that damages publication quality, exact-title drift, link-text corruption, href/src/media/code mutation, speaker-attribution issues, punctuation/line-merge damage, structural omissions/duplications, and misleading target-language wording as material defects requiring repair.

BATCH 74 — UNIVERSAL MATERIALITY-AWARE POLISH + ANTI-CHURN HARDENING — 4 June 2026

This Batch75 patch is universal. It is not Polish-only and must apply across Latin-script, non-Latin-script, inflected, analytic, right-to-left, and mixed-script target languages. Preserve all Batch73 Presence / hybrid-residue safeguards and all inherited Batch72/71/70/68/67/66 safeguards.

FALSE-PASS / REUSED-ARTIFACT FAILURE GATE
A review, repair, no-repair promotion, package, or handoff pass is invalid unless it reopens the exact latest artifact and produces fresh evidence for this pass. Do not reuse prior pass summaries, prior links, old QA reports, old filenames, or memory as if they were a new review. If a response claimed a new pass but actually reused prior artifacts or did not review, explicitly retract that claim, identify the latest real artifact, and do not continue pretending the false pass exists.

EXACT-ARTIFACT EVIDENCE REQUIREMENT
Every pass must report the exact input artifact path/name, exact output artifact path/name, whether the output is byte-for-byte identical or materially changed, and SHA/hash or equivalent identity evidence when the tool environment allows it. State whether each intended replacement matched and applied. If no new artifact or new no-material-edit QA report is produced, do not claim a new pass; say: No new pass was completed.

NO-REPAIR VS REPAIR SEPARATION
A strict no-repair promotion pass must make no material edits. If any material issue is found, promotion fails. Either stop with a failed-promotion report or begin a separate material repair pass. Any pass that makes material edits must use: REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required. It must not also promote in the same pass.

THOUGHT-ONLY REVIEW PROHIBITION
Thinking briefly and reusing old links is not a review. A valid review must show concrete evidence: opened latest artifact, searched/scanned target text, sampled high-risk source/target passages, ran target-language fluency checks, checked the cumulative risk basket, checked href/src/media/code parity, and generated a new QA report or explicitly stated that no new artifact was created.

STRING-SPECIFIC REPAIR FRAGILITY / 0-MATCH RULE
If a targeted repair does not match the current artifact, do not assume the issue is fixed. Search semantic variants, shorter substrings, inflected variants, capitalization variants, punctuation variants, HTML-separated variants, and nearby context. Log every 0-replacement intended repair as a warning requiring investigation. For scripted repairs, QA must list old string/pattern searched, match count, replacement applied, 0-match intended repairs, semantic follow-up search, and before/after cumulative risk-basket status.

LATIN-SCRIPT RESIDUE AND FLUENCY GATE
For Latin-script target languages, ordinary English residue is visually hidden because both source and target may use Latin characters. Run an extra Latin-script residue scan for English words left in ordinary prose, English technical labels with local grammar errors, English terms glued to local inflections/cases/prepositions, unquoted English labels used as target-language nouns, partially translated source-title fragments, and English idiom calques that look superficially grammatical.

INFLECTED-LANGUAGE PROTECTED-LABEL AGREEMENT GATE
For inflected target languages, retained labels such as AMness, I AMness, Presence, Awareness, Self, No Mind, no-mind, Dharma, Dhamma, Maha, anatta, anātman, dhātu, skandha, and śūnyatā must be checked for case, gender, number, agreement, and natural grammar. If a protected label is retained, the surrounding sentence must still be natural. Use target-language-first phrasing, quotes, or a short explanation rather than forcing local grammar onto the retained label.

SLASH-CALQUE HARDENING
Scan visible prose for slash compounds such as 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, linked title fragments, and person aliases joined with slashes. Classify each as exact title/proper label, glossary/termbank, ordinary prose, or ambiguous. Preserve exact titles and intentional glossary labels; convert ordinary prose into natural target-language coordination, apposition, or explanatory phrasing; flag ambiguous cases.

EXACT TITLE VS TRANSLATED TITLE HARDENING
For every link-bound title, decide separately whether it is preserved exactly, fully translated naturally, or intentionally paired. Do not partially translate titles, honorifics, or title fragments such as translating “Mr.” while leaving the rest English. Do not mix target-language words into exact English titles unless that is the exact source title. QA must list linked titles as preserved, translated, or intentionally mixed/paired.

IDIOM AND METAPHOR CALQUE HARDENING
Prompt-level review must actively hunt literal renderings of English idioms/metaphors and build a target-specific idiom/calque risk basket. Seed examples include: 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. This list is illustrative, not exhaustive.

TECHNICAL TERM FAMILY DRIFT GATE
Once a term family causes repeated repairs, add the family to the cumulative risk basket and scan globally in all variants. High-risk families include 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.

MECHANICALLY CORRECT BUT UNNATURAL IS MATERIAL
A translation can pass termbank checks and still fail if the target-language prose is unnatural or doctrinally misleading. Treat unnatural case/gender/number agreement, source word order copied too literally, line-merge fragments, technical labels without grammatical integration, slash-heavy prose, literal metaphor calques, target-language punctuation defects, capitalization problems, and misleading ordinary-word renderings of Dharma terms as material defects when they affect readability or doctrinal clarity.

NO-REPAIR PROMOTION EVIDENCE ADDENDUM
A no-repair pass must include a section titled “No New Artifact Reuse / Exact Artifact Evidence” with: I reopened: [exact file]; I produced: [exact report/file]; Material edits made: yes/no; if no, output is byte-for-byte identical/hash-equivalent/explicitly copied unchanged; if yes, no promotion allowed; prior pass status was not assumed; new review evidence is listed.

CROSS-LANGUAGE TERM SOURCE EVIDENCE LIMIT
Use target-language Buddhist sources where available to confirm major Dharma term choices, but source evidence supports broad term choices only. It does not prove sentence-level fidelity, context fit, or target-language fluency. Paragraph/link/blockquote/list counts are necessary but insufficient and must never be treated as proof of translation quality.

STATUS DISCIPLINE
If material issues are found after a previous no-repair promotion, state: 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. Never claim strict-certified final.

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

This Batch73 patch is universal. It is not a Japanese-only fix. Apply it to all ATR translation, review, refinement, HTML translation, audit, formatting, package, and promotion workflows for all target languages.

UNIVERSAL KEY TERM RESEARCH BEFORE DEFAULT TRANSLATION GATE
Before translating or standardizing any high-risk AtR/Dharma term, do not rely only on dictionary equivalence, memory, previous target-language habits, or another language's termbank. Create or update a compact Key Term Research / Decision Table for article-central terms. Include source term, target rendering, translated/retained/transliterated/paired status, protected-label status, ordinary-prose rule, forbidden/high-risk renderings, whether external/source research is needed, and whether the term has multiple senses.

Minimum high-risk basket when present: 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, and article-specific technical terms.

UNIVERSAL PRESENCE GATE
Treat Presence as a high-risk AtR/Dharma term, not a generic English word. Distinguish technical AtR Presence from ordinary presence/present, ever-present/already-so phrasing, philosophical/metaphysics-of-presence usage, and Dzogchen title/phrase usage such as Instant Presence. Technical AtR Presence points to luminous immediacy/direct actuality/the vivid fact of being-experience and appears in phrases such as pure Presence, Total Presence, Presence-Awareness, Presence is spontaneously perfected, manifold of Presence, and nature of Presence. It requires target-language research and a termbank decision.

Japanese house-style note for the Seven Stages article family: technical AtR Presence defaults to 臨在; pure Presence = 純粋な臨在; Total Presence = 総体的臨在; Presence-Awareness = 臨在＝覚知; Presence is spontaneously perfected = 臨在は自ずから円成している / context-specific. Avoid 現前性 as the default for AtR Presence unless the context is specifically philosophical/phenomenological. Ordinary present/ever-present contexts may require 現前している, すでに現れている, 常にすでにそうである, or another natural phrase. Do not impose this Japanese note on other target languages. Chinese AtR house style may preserve 臨在 where applicable, but Chinese choices are clues, not automatic authorities for all other languages.

TARGET-LANGUAGE-FIRST PARENTHETICAL ORDER RULE
In ordinary target-language prose, if a retained English/Sanskrit/Pāli/Tibetan/source label is useful, prefer target-language first: target-language rendering（source label）. Avoid source-label first forms in ordinary prose unless the source label is an exact title, is being discussed as a phrase, the target-language convention strongly prefers it, the user explicitly requests it, or it is a glossary/termbank entry. Do not glue retained source labels directly to target-language case markers, particles, suffixes, postpositions, clitics, or inflections.

Japanese examples: use 無我（anatta）の, not anatta の; 空性（shunyata）の実現, not shunyata の実現; 心（Mind）, not Mind（心） in ordinary prose; 伝達（transmission）, not transmission（伝達）; 無我（no-self）, not no self（無我）. Avoid hybrids such as Pure覚知, Natural覚知, Non-dual は, dependent origination の, ground と path, meditative composure と insight, no-mind の状態, anatta実現, Maha経験, On 空性, Self-実現, and Being／Self-Realisation への.

UNIVERSAL HYBRID RESIDUE SCAN
Before final or promotion, build a target-language-specific hybrid scan basket. Search for English/source labels glued to local particles/case markers/suffixes/inflections; English words inside target-language compounds; target-language words inserted into exact English titles; mixed-script technical hybrids; English-first parentheticals in running prose; translated fragments inside exact English titles; ordinary English prose overprotected as technical labels; and stray spaces before local particles after parentheses. For Latin-script target languages, run an extra ordinary-English residue scan because English residue is harder to see.

Japanese risk basket seed: 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経験; 五蘊（五蘊）. Also scan Latin/source labels before の, を, に, へ, と, は, が, で, も, から, まで, より and before 後, 的, 性, 実現, 経験, 状態, 化, 作用, 実践, 知見, 覚知, 空性.

EXACT TITLE VS TRANSLATED TITLE HANDLING
For every linked article/book/video/audio title, decide whether the link text should remain the exact source title or be translated as a full natural target-language title. If preserved, preserve the whole title exactly; do not partially translate it. If translated, translate the whole title naturally and retain the exact source title in parentheses only when useful. Do not create mixed titles such as On 空性, Awakening to Reality 実践 Guide, or Recognizing Rigpa vs Realizing 空性. Do not translate URL slugs. Record intentional title preservation/translation in QA.

PROTECTED-LABEL WHITELIST DISCIPLINE
A word being technical does not automatically mean it should remain in English. Classify every retained English/Sanskrit/Pāli/Tibetan label as exact title, proper name, URL/code, intentionally retained technical term, intentionally retained English AtR label, gloss in parentheses after target-language rendering, or human-review placeholder. Ordinary lowercase terms such as experience, realization, practice, view, awareness, consciousness, manifestation, ground, path, source, self, mind, state, clarity, naturalness, ordinariness, spontaneity, agent, doer, doership, subject, and object should normally be translated unless a reason is documented.

TERM-FAMILY ESCALATION RULE
If more than one material issue is found around the same term family, escalate that family into the active termbank and scan basket. Example: if Presence was mistranslated once, scan Presence, pure Presence, Total Presence, Presence-Awareness, nature of Presence, present, ever-present, and target-language alternatives globally. If one anatta hybrid appears, scan every anatta/no-self/non-self/anatman form. If one total exertion issue appears, scan total exertion/total activity/complete activity/full function equivalents globally.

TOTAL EXERTION SOURCE-AWARE RULE
Do not default total exertion mechanically. For Japanese Dōgen/Zenki contexts, consider 全機 and 一法究尽 depending on source meaning. For Chinese, preserve the existing rule not to default to 全体作用; use 一法究尽 / 具尽 / context-specific handling. For other languages, research source/context before setting a default.

NO-REPAIR PROMOTION HARDENING
A no-repair promotion pass must include exact-artifact reopening, source comparison, Prompt 6 semantic fidelity review, Prompt 9 target-language fluency review, target-language hybrid residue scan, target-language-first parenthetical-order scan, high-risk term table consistency scan, exact linked-title scan, ordinary prose vs protected-label classification, URL/href/src/code integrity scan, punctuation/line-merge scan, and representative high-risk sentence sampling from beginning, middle, ending, blockquotes, bold/italic sections, and all article-central terms. If material issues are found after a previous no-repair promotion, explicitly retract the earlier promotion and reset status: 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
Every final/review/promotion QA report should include: exact source file, exact target file, prompt versions applied, target-language risk profile, key term decision table, Presence Gate result when relevant, parenthetical-order scan result, hybrid residue scan basket, ordinary English/source residue basket, protected-label whitelist, exact linked-title scan, href/src/media parity, non-source text in URL/code scan, major structure counts, representative sentence sampling notes, cumulative risk basket and results, whether material edits were made, and the correct status label.

STATUS DISCIPLINE
Because Batch73 is a material managed-prompt update, its status is: REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required. Only a later exact-artifact no-material-edit readback pass may promote to: reviewed final / publishable — strict-certified final not claimed.

BATCH 72 ROUTING — PLUM DAWN FEATURE PANEL + ALL-DESCENDANT DARK-PANEL CONTRAST AUDIT — 1 June 2026

If the task involves Blogger styling, dark plum / purple dawn feature panels, summary boxes, dark panels, source-quote/thesis-line cards inside dark panels, unreadable text screenshots, or CSS contrast repair, route through:
1. Unified Blogger Formatting Prompt v5.8.15 for Plum Dawn component role separation, final-winning all-descendant cream text locks, gold links inside plum panels, no nested plum panels, and no class role reuse.
2. Strict HTML QA v1.9.12 for all-descendant dark/plum/purple panel contrast audit, `-webkit-text-fill-color` conflict checks, nested panel/class role checks, and browser/screenshot caveats when rendering is not verified.
3. Same-pass material CSS/rendering repairs require: REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.
4. Only a later exact-artifact no-repair pass may use: reviewed final / publishable — strict-certified final not claimed.

BATCH 71 INHERITED ROUTING — UNIVERSAL WITNESS/SĀKṢĪ + RESIDUE/CALQUE HARDENING — 1 June 2026

If the target language workflow involves Witness, Eternal Witness, observer, watcher, seer, perceiver, knower, subject, Sākṣī/Sakshi/sākṣin, Advaita/Vedanta/Self/I AM/AMness/Brahman/Atman language, romanized Sanskrit/Pāli/Tibetan terms, visible link text in English, mixed English+target-language hybrids, Tamil/Bengali/non-Latin residue, repeated failed no-repair promotions, or target-language calque/fluency defects, route through:
1. Prompt A for HTML/Blogger source-of-truth, exact-latest-artifact, href/src, visible link text, structure, and status discipline.
2. Prompt 1 for translation with protected-label setup, target-language term profile, and no ordinary source-language residue.
3. Prompt T or Prompt X when Tibetan/Indic or East Asian source verification/restoration is involved.
4. Prompt 6 as adversarial defect hunt for residue, doctrinal mistranslation, overprotected English, exact-title damage, corrupted links, and cumulative risk-basket recurrence.
5. Prompt 9 for whole-document native-prose fluency, calque, punctuation, line-merge, and terminology coherence.
6. Unified Blogger Formatting only after translation/review is stable, without mutating URLs/code/attributes.
7. Strict HTML QA for structural/link/media/code parity plus visible-text residue smoke test.
8. No-repair promotion only in a separate exact-artifact pass with no material edits.

If material repairs are made, status remains: REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.

I have uploaded ATR prompt files as separate .txt files or as a small prompt-pack ZIP. Please do not summarize the prompt files. Use them as operating instructions.

First, list the uploaded prompt filenames you can access. Then identify which ATR prompts are relevant to this task and which are missing, if any.

Task type: [HTML/Blogger translation | unified Blogger styling / finished prose to AtR Blogger HTML | raw chat-log cleanup then Blogger styling | clean translation | review only | Tibetan/Indic source verification | East Asian source restoration | Baihua | prompt-suite maintenance]
Target language: [Simplified Chinese / Traditional Chinese / English / other]
Source file or source text: [uploaded file name or pasted below]
Output needed: [clean text / Blogger HTML / DOCX / QA report / repaired artifact / other]

BATCH 68 NON-LATIN TARGET RESIDUE DISCIPLINE + TIBETAN DHARMA-TERM TRANSLATION GATE + DOM-SAFE REPAIR HARDENING — 28 May 2026

This Batch 68 patch is narrow. Preserve all Batch 66 / Batch 67 source-of-truth, updated-English propagation, dialogue/source-box parity, no-repair promotion discipline, Blogger HTML preservation, href/src parity, and Soh/AtR Chinese termbank rules. Do not create a broad new Chinese termbank and do not introduce 全体作用 as a default for total exertion.

BATCH 68 ROUTING — NON-LATIN / TIBETAN RESIDUE + DOM-SAFE REPAIR — 28 May 2026

If the target language is Tibetan or another non-Latin language, or if the user says or implies “too many English terms preserved,” “Sanskrit terms left untranslated,” “Tibetan translation,” “non-Latin residue,” “technical labels,” “romanized Buddhist terms,” “Who am I damage,” “Buddhahood hybrid,” “href changed,” or “Presence/rigpa/anatta/emptiness in Tibetan,” route through:
1. Prompt A if HTML/Blogger artifact.
2. Prompt 1 for translation.
3. Prompt T if Tibetan/Indic terminology/source verification is involved.
4. Prompt 6 for objective error / source-language residue review.
5. Prompt 9 for whole-document terminology coherence.
6. Strict HTML QA for non-Latin residue, hybrid-damage, and href/src parity.
7. No-repair promotion pass if material repair occurred.

Controller warning: Do not preserve Sanskrit/Pāli/English Buddhist terms merely because they are technical. Translate ordinary body-prose Dharma terms into Tibetan/target language unless they are exact titles, labels under discussion, URLs/code, or proper names.

Preserve the existing Batch66/Batch67 no-repair labels. If material repair is made, use: repaired after re-audit — no-repair promotion still required. Only a later no-repair exact-artifact readback pass may use: reviewed final / publishable — strict-certified final not claimed.

BATCH 67 ROUTING — UPDATED ENGLISH / DIALOGUE SOURCE-BOX / NO-REPAIR PROMOTION — 23 May 2026

If the user says or implies:
- “updated English”
- “new English”
- “many changes”
- “not only this example”
- “URLs updated”
- “split box”
- “one box”
- “speaker attribution”
- “compare with original”
- “use Prompt A / Prompt 6 / Prompt 9”
- “no-repair promotion”

Then route through:
1. Prompt A Updated-English-Source Propagation Gate.
2. Prompt A Dialogue Source-Box Gate.
3. Prompt 6 Objective-Error Review.
4. Prompt 9 Source-Box Continuity Sweep.
5. Strict HTML QA Dialogue Box / Source Attribution Parity Audit.
6. Existing Batch 66 terminology and high-risk search basket.
7. No-repair promotion pass if material repair was made.

If material repair is made, label:
repaired after re-audit — no-repair promotion still required.

If no material repair is made in a subsequent exact-artifact readback pass, label:
reviewed final / publishable — strict-certified final not claimed.

This routing is not a new broad terminology basket. Preserve the existing Batch 66 Soh/AtR termbank, including the existing total-exertion rule; do not introduce 全体作用 as a default.


Required workflow:

BATCH 35 UNIFIED BLOGGER FORMATTER ROUTING — 11 May 2026
The former Quick Blogger Formatting Prompt and former Full Blogger Formatting Prompt are now one Unified Blogger Formatting Prompt. Do not ask the model to choose between Quick and Full. Route finished prose, approved article text, and final Blogger styling to the unified formatter, then run Strict HTML QA. Raw chat logs still require Prompt 8 first; do not merge Prompt 8 into the formatter.

1. If this is Blogger styling / finished prose to AtR Blogger HTML, use the Quick Unified Blogger Formatting Prompt first and do not translate, polish, summarize, or omit any wording. If this is HTML/Blogger translation or complex Blogger work, use Prompt A as the controller and preserve all HTML structure, links, wrappers, metadata, and safe prompt-body escaping.
2. If this is a clean translation, draft with Prompt 1 unless another uploaded prompt is more specific.
3. If Tibetan, Sanskrit, Pāli, Prakrit, or Indic/canonical source verification is involved, activate Prompt T before relying on any public English translation. Public translations are witnesses only, not authorities.
4. If Chinese, Japanese, Korean, Chan/Zen, Dōgen, CBETA, SAT, or East Asian source restoration is involved, activate Prompt X. Restored source blocks must not replace complete body translation coverage.
5. If classical Chinese needs modern Chinese explanation, use Prompt 5, but do not add unsupported Dharma commentary into the 白话.
6. After drafting or repairing, run Prompt 6 as the high-fidelity review gate.
7. Use Prompt 9 only after Prompt 6 when whole-document refinement, consistency, or publication polish is needed.
8. For HTML/Blogger artifacts, run the Strict HTML QA Audit Prompt before claiming the file is Blogger-ready.
9. If creating or editing files, read back the saved artifact before claiming completion.
10. If any required prompt file is missing or unreadable, say exactly which file is missing and continue with the safest partial workflow rather than inventing prompt content.

Now proceed with the task using the uploaded ATR prompt files.

Basis/Dharmakaya QA6 controller addendum — old/new styled source and restored-block workflow:
11. If uploaded files include an old source, new styled source, target-language draft, prompt pack, and QA reports, first list files by role: Content authority, Styling shell, Existing target-language draft, Prompt pack files, and QA reports / older generated artifacts.
12. If the user says the new styled file should have the same content as the old file, run normalized visible-text content parity before translation. Repair the styled source first. Do not translate from a defective styled source, and do not use paragraph count alone as evidence.
13. If repaired source restores large missing blocks and a target-language artifact already exists, translate the restored blocks freshly from the source using Prompt 1. Do not rely on existing public or old translations unless the user explicitly permits it. Then run Prompt 6, Prompt 9 where appropriate, and Strict HTML QA.
14. If any restored block remains untranslated, label the artifact exactly as STRUCTURALLY READY BUT TRANSLATION INCOMPLETE. Do not say final, complete, or Blogger-ready.
15. For complex repair sessions, return final repaired source HTML, final target-language HTML, QA report TXT/JSON, optional ZIP containing outputs, and a separate prompt-patch ZIP if prompts need updates.
16. In the final response, state only what was actually verified. Do not claim all issues fixed unless the QA report supports it.

Dzogchen terminology controller addendum — gnas tshul / snang tshul, sentient-beings, cognizance, obscurations, and phenomena QA:
17. If the task involves Chinese Buddhist/Dzogchen translation, review, formatting, or artifact QA, activate the relevant terminology gate before final claims.
18. Search the exact target artifact for 知识 / 知識, 有情的显现样态 / 有情的顯現樣態, 安住样态 / 安住樣態, 诸现象 / 諸現象, 知性, 宇宙与有情 / 宇宙與有情, and 被显为清净 / 被顯為清淨.
19. For each hit, inspect source context and classify fixed / intentionally retained / needs source review. Do not apply these as free-polish substitutions.
20. Preserve gnas tshul / snang tshul distinction, avoid 有情的显现样态 where it means mode of appearance for sentient beings, prefer 器情世间 for snod bcud-style universe-and-beings formulas, avoid 知性 for Dzogchen cognizance, use 遮障 for doctrinal obscurations and 诸法 for doctrinal phenomena.
21. Do not claim final, complete, Blogger-ready, or terminology cleanup complete unless these target-side searches and source-context classifications were performed on the exact returned artifact.

Batch 33 controller addendum — dependent designation / effort / View / common-uncommon Mahāyāna gate:
22. If the task involves Chinese Buddhist/Dzogchen/Madhyamaka translation, review, formatting, or artifact QA, activate the Batch 33 terminology gate before final claims.
23. Search the exact target artifact for 依名假立, 依缘假立 / 依緣假立, 努力, 精进 / 精進, 勤作, 知见 / 知見, 共同大乘, 不共大乘, 非共同大乘, and 特殊大乘.
24. For each hit group, inspect source context and classify fixed / intentionally retained / needs source review. Do not apply these as free-polish substitutions.
25. Preserve dependent designation as 依缘/依蕴/依支分/假名安立 by context; preserve Dzogchen/Mahāmudrā effort as 勤作/no-effort wording where appropriate; preserve View/lta ba as 见/见地/见解 rather than automatic 知见; preserve common/uncommon Mahāyāna as 共同大乘/不共大乘.
26. Do not claim final, complete, Blogger-ready, or terminology cleanup complete unless these target-side searches and source-context classifications were performed on the exact returned artifact.


Batch 34 controller addendum — dark panel / summary box contrast gate:
27. If the task outputs or approves AtR Blogger HTML, run the Dark Panel Contrast / Summary Box Readability Gate before any Blogger-ready or publication-ready claim.
28. Inspect every .summary-box, .dark-box, .dark-panel, .atr-dark-panel, dialogue card, transcript box, quote card, and inline dark-background element.
29. Confirm headings, subheadings, strong text, body/list text, raw URLs, normal links, visited links, hover states, and focus states remain readable against dark backgrounds.
30. Fail or route to Blogger Formatting repair + Strict HTML QA if dark blue, purple, navy, grey, or other low-contrast theme colors appear inside dark panels.
31. Do not claim final Blogger-ready status until the exact returned HTML artifact has passed source/content parity, link parity, valid nesting, mobile/readability sanity, and dark-panel contrast readback.


BATCH 66 SOH/ATR CHINESE DOCTRINAL TERM-BANK GATE — 23 May 2026
If the task involves Soh / Awakening to Reality modern doctrinal prose in Chinese, route through Prompt A or Prompt 1, then Prompt 6 and Prompt 9, and require the Batch 66 high-risk search basket before any final/publishable claim.

Minimum routing:
1. Draft/translate from the source only.
2. Run Prompt 6 with Soh/AtR terminology gates: view→知见 in modern Soh/AtR prose; agent/doer/actor distinction; perceiver/perceived vs knower/known; true self→真我 in critique contexts; spontaneous/effortless vs 任运; total exertion→一法究尽; Presence/Awareness/Consciousness context split; dependent-origination conditions.
3. Run Prompt 9 only after Prompt 6 and do not undo Prompt 6 term locks.
4. For HTML, run Strict HTML QA with the high-risk search basket, href/src accounting, native Blogger chrome audit, and CSS-generated bullet/entity audit.
5. If any current pass made material repairs, use exactly: REPAIRED AFTER RE-AUDIT — material gates currently pass, no-repair promotion still required.
6. If the user has printed an older copy, include a Manual changes for printed copy ledger with exact old→new replacements.

No-repair promotion must reopen the exact saved artifact from the previous pass and make no material edits before it may be labeled: reviewed final / publishable — strict-certified final not claimed.