

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




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

This Batch75 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.