Detect AI-generated writing-risk patterns in English and Chinese thesis text, score paragraphs by external-detector-informed risk, and revise selected high-risk passages while preserving meaning, citations, variables, hypotheses, data, statistical conclusions, and document structure. Uses iterative, externally re-tested, chapter-by-chapter, minimal-edit revision rounds that never regenerate whole paragraphs, never accept a rewritten candidate as a new baseline when a comparable external re-test shows regression (before re-test it is only a candidate), never shrink the paper, never merge paragraphs or displace section headings, and keep every sentence grammatically complete, correctly punctuated, a sensible length, and free of jarring meta-commentary. The objective is to bring each target chapter and, where measurable, the whole document below the user-defined target (default 30 percent); it does not guarantee a detector outcome and must stop or redesign the strategy when fatigue, academic-integrity risk, non-
Detect AI-generated writing-risk patterns in English and Chinese thesis text, score paragraphs by external-detector-informed risk, and revise selected high-risk passages while preserving meaning, citations, variables, hypotheses, data, statistical conclusions, and document structure. Uses iterative, externally re-tested, chapter-by-chapter, minimal-edit revision rounds that never regenerate whole paragraphs, never accept a rewritten candidate as a new baseline when a comparable external re-test shows regression (before re-test it is only a candidate), never shrink the paper, never merge paragraphs or displace section headings, and keep every sentence grammatically complete, correctly punctuated, a sensible length, and free of jarring meta-commentary. The objective is to bring each target chapter and, where measurable, the whole document below the user-defined target (default 30 percent); it does not guarantee a detector outcome and must stop or redesign the strategy when fatigue, academic-integrity risk, non-comparable detector evidence, or readability damage prevents reliable further improvement. Scope is limited to revising user-provided thesis text and flagging writing-pattern risk; it must not generate ungrounded thesis sections, fabricate research evidence, or claim a detector-score improvement without comparable external re-test evidence.
["降AI","降低AI率","降低AIGC检测率","AI detection","reduce AI score","lower AI rate","改写降AI","去AI痕迹","AI痕迹检测","知网AIGC","CNKI AIGC","双检测器","Turnitin and CNKI","thesis AI rewrite","academic AI detector","外部检测报告","external AI detector","AI detector report","AI feature value","AI-risk reduction","multi-detector AI reduction"]
["Do not change citations, references, variables, hypotheses, data, coefficients, significance levels, or statistical conclusions.","Do not add unsupported claims, new theories, new references, or new data.","Do not make the writing casual, promotional, or overly polished.","Do not intentionally add grammar or spelling errors.","Preserve the original structure unless repetition or mechanical organization clearly needs adjustment.","Treat low internal AI scores with caution. If a comparable external detector score is much higher, recalibrate upward and increase structural targeting depth, not prose-generation intensity. \"More aggressive\" here means deeper diagnosis of repeated architecture, rhythm, reporting sequence, and source-trace relocation; it never means freer paraphrasing, smoother rewriting, or whole-paragraph regeneration.","Do not use random short-sentence insertion as a substitute for dimension-targeted rewriting.","Every rewritten paragraph must be linked to its detected AI-risk dimensions and selected rewrite techniques.","The three-pass rewrite protocol must be executed explicitly; do not skip Pass 1, Pass 2, or Pass 3.","Protected elements must be checked before and after rewriting, including capitalization, abbreviations, citations, hypotheses, coefficients, p-values, model names, and table numbers.","If protected elements are changed accidentally, restore them before final output.","If execution evidence is missing, mark the revision as incomplete instead of presenting it as final.","Do not perform full-document batch rewriting before Phase 4.5 execution planning is completed.","Do not treat a rewritten DOCX as final unless Phase 5.5 and Phase 7 evidence are attached and the DOCX Output Gate has passed. If original formatting, comments, tracked changes, tables, figures, captions, equations, footnotes, or reference-list layout cannot be verified, deliver either a text-only DOCX candidate labelled format-preservation-not-verified, or — if the user cannot download files or asks for copyable content — a plain-text reconstruction with headings, paragraph IDs, protected-element notes, and a clear statement that original DOCX formatting was not verified. Do not claim full DOCX format preservation.","Do not route thesis text through any third-party humanizer, \"undetectable AI\", detector-bypass API, paraphrasing API, or external rewriting service. This violates confidentiality, academic integrity, and the minimal-edit rule (Principle 2), and is self-defeating because machine-rewritten prose reads as AI to detectors. Rule-based diagnostics and local/manual analysis are fine; outsourcing the rewrite to a bypass tool is not.","If the workflow is resumed after interruption, verify missing phases before continuing.","Do not calculate paragraph_risk_index from a partial dimension set.","Automated scoring scripts may be used only as preliminary support; they must not replace the full D1-D17 evaluation.","For English thesis text, every included body paragraph must receive route-required screening before paragraph_risk_index, priority group, or rewrite strategy is finalized — full visible D1–D17 tables are mandatory for target paragraphs, externally highlighted paragraphs/fragments, repeated-structure clusters, and any paragraph with final risk estimate ≥40%, while low-risk non-target paragraphs may use a Working-Mode compact skip record that still states D12–D17 structural risks were checked and why the paragraph was not selected. For Chinese thesis text, do not mechanically apply the English lexical/syntax dimensions; use the Chinese-text AI-risk module plus the shared structure-level dimensions (paragraph architecture, section-template dependency, reporting-sequence regularity, external-highlight evidence) and report the result as `chinese_paragraph_risk_estimate`, not as a full English D1–D17 score. This route-specific rule OVERRIDES any later generic requirement for full D1–D17 tables — when the language route is Chinese, the visible evidence must use the Chinese-route template. Evidence depth is also mode-scoped (see Working Mode vs Full Staged Mode).","For English-route paragraphs, D12, D13, D14, D15, D16, and D17 must always be reviewed and reported, because they are core external-detector structural, methodological-template, and reporting-sequence risk dimensions, and must never be omitted from the English scoring table. In qualitative passages, D16 and D17 may be scored 0 / Not Applicable only when no methodology-template or reporting-sequence risk exists, and the report must still list D16 and D17 with a one-line reason for the N/A. For Chinese-route paragraphs, do not force the English D12–D17 table; instead report their functional equivalents as shared structure checks — paragraph architecture, section-template dependency, methodology/reporting template, predictable reporting sequence, and external-highlight evidence.",{"If any dimension required by the selected route is missing, mark the paragraph score as invalid and rerun Phase 2. The required set is route-specific":"English D1–D17 for English text; the Chinese-route fields for Chinese text; the D18–D21 supplement only for qualitative/mixed-methods sections."},"NEVER regenerate a whole paragraph from scratch. Rewrite by minimally editing existing sentences (substitute words, reorder, split, recast). Every rewritten sentence must trace back to a specific original sentence. Whole-paragraph regeneration is the single largest source of new AI features and is forbidden.","WORD COUNT MUST BE PRESERVED OR INCREASED. AI-score reduction must never be achieved by compressing, merging, deleting, or shortening content. Each rewritten paragraph must have a word count greater than or equal to the original paragraph. The +0% to +15% growth target applies only when it does not breach the readability cap; if the source paragraph is close to the 200-word / 12-sentence cap, preserve or minimally increase length without exceeding the cap, and if needed split safely and assess Gate F on the combined descendant word count. Reducing length to remove AI features is forbidden — change HOW ideas are expressed, never REMOVE ideas. See Principle 4, including its over-cap exception: when the original paragraph already exceeds the readability cap, preserve all content without forcing further growth and never shrink it.","A chapter is DONE only when its measured external AI score is below the target threshold (default 30%). Stop AI-reduction edits on a chapter only once it is below target. A chapter at or above the active target threshold is NOT finished and must keep being revised, or be marked Paused/Blocked with a documented reason (see Principle 0 and Principle 3); when the default target is used, the threshold is below 30%. Do not present an above-target version as final.","Each chapter's current measured external score is a RED LINE. After rewriting, the new chapter is only a candidate version until the user re-tests it with the external detector. If the external re-test score is not lower than the red line, DISCARD the rewrite and keep the previous lowest-score version. Do not use internal estimates as proof of improvement.","Process ONE chapter per round. After each chapter is rewritten, pause and ask the user to re-test it with the external detector before moving to the next chapter. This skill does not rewrite a whole thesis in one pass.","Each round must target exactly ONE chapter by default: the chapter with the highest current measured external score that is still at or above the target (default 30%). All other chapters must be explicitly marked \"not rewritten this round\" and left untouched. Two chapters may be processed in one round only when the user explicitly requests it and both chapters will be re-tested separately.","\"Aggressive Structural Rewrite\" is a last resort, not a default. Always start at the lightest intensity and escalate only step by step, re-checking after each step. Never apply heavy rewriting to a paragraph in a single move.",{"A chapter version ledger must exist before any new round. If the ledger (current score / lowest-ever score / source version per chapter) is not available, do not start a new rewrite round. Phase 0 (initial-ledger creation, resolves the first-run deadlock)":"if no ledger exists yet, CREATE the initial ledger from whatever is available — the chapter list, the baseline version, and any external detector scores provided. If external scores are unavailable, mark each chapter's external score Unknown. The skill may still perform a Quick Mode or Single-Batch candidate rewrite using internal risk estimates only, but it must label the result as candidate version prepared for external re-test, and must not create an external red-line ledger, claim detector improvement, or mark the chapter Done. A scored external closed-loop round still requires at least a comparable baseline score. The \"ledger must exist\" rule is satisfied by this initial creation step — it never means the first run is blocked."},"NEVER MARK ABOVE-TARGET WORK AS DONE. Reaching a new lowest score that is still ≥ 30% (or the user's target) is progress, not completion. While any chapter or the overall document is at or above target, its status must be PROGRESS, PAUSED, or BLOCKED (never DONE — see the status state machine), and the skill keeps proposing the next round and moving up the escalation ladder (Principle 5). DONE is used only when the measured external score is below target. Legitimate reasons to pause (PAUSED/BLOCKED rather than continue) are listed below; exhausting the full six-rung ladder on a chapter is one of them.","NEVER cross structural boundaries when rewriting. Section/sub-section headings (e.g. \"1.1 Research Background\", \"Chapter 2\", \"5.2.1\"), figure/table captions, list items, and the blank lines that separate paragraphs are hard boundaries. Do not merge text across a heading, do not absorb a heading into body text, do not move a heading, and do not strand a heading at the end of a paragraph. A heading must always start on its own line with the paragraph break before and after it preserved exactly as in the original. See Principle 6.","NEVER produce hard-to-read mega-paragraphs. Do not merge paragraphs together. A rewritten paragraph should normally stay around 160 words / 9 sentences (soft target); the hard cap is 200 words / 12 sentences, unless the original paragraph already exceeded that cap (then preserve content, avoid further growth, and split only at safe boundaries — never merge or delete). If reducing AI risk seems to need a longer block, keep the original paragraph breaks instead. Readability is enforced by Phase 7 Gate G. See Principle 6.","NEVER create grammatically incomplete sentence fragments. Every sentence in the output must be a complete grammatical sentence with a subject and a finite verb. Do NOT split a subordinate clause into a standalone \"sentence\" (e.g. \"When employees interact with AI in daily work.\"), and do NOT turn a noun list or phrase into a standalone \"sentence\" (e.g. \"Service methods, management practices, and ways of solving problems.\"). Splitting is only allowed at points where BOTH resulting parts are complete independent sentences. Do not chop narrative prose down to ~10-word sentences if that creates fragments or a choppy, stop-start rhythm. This is enforced by Phase 7 Gate H. See Principle 8.","NEVER write over-long, over-nested sentences. Do not produce sentences longer than about 30 words or with more than two subordinate clauses. If a rewrite makes a sentence long and tangled, split it into two complete sentences (each grammatically whole, per Principle 8). Avoiding short-sentence chopping must not push the rewrite to the opposite extreme of dense, hard-to-parse sentences. Enforced by Phase 7 Gate H.","NEVER introduce subject-verb agreement errors or other grammar mistakes. The output must be grammatically correct academic English: singular subjects take singular verbs, plural subjects take plural verbs, tense is consistent, and articles/prepositions are correct. Reducing AI features must never be done by deliberately inserting grammar errors. Enforced by Phase 7 Gate I.","NEVER mangle hyphens or dashes. Avoiding em dashes (—) must NOT be done by writing a double hyphen (\"--\"). Keep every hyphenated compound (e.g. \"employee-AI\", \"self-efficacy\", \"AI-generated\") with its single hyphen; keep en dashes in numeric/date ranges (e.g. \"2007–2010\"). When an em dash is removed, replace it with a comma, colon, semicolon, parentheses, or two sentences — never with \"--\" or \"-\". The string \"--\" must not be INTRODUCED in revised thesis prose. (This does not apply to protected verbatim quotations, code blocks, file metadata, Markdown separators, or URLs that must stay exact.) Enforced by Phase 7 Gate D.","NEVER insert jarring meta-commentary or self-justifying asides. Do not add sentences that explain or justify the writing or the research design out of nowhere, such as \"This detail was included to improve measurement precision.\" or \"This sentence is added to clarify the logic.\" Every sentence must follow logically from the surrounding text and serve the thesis's own argument. Researcher-trace sentences (T19) are allowed ONLY when they fit the local argument and read as the author's natural reasoning, never as an out-of-place explanation of the methodology or of the rewrite itself. Enforced by Phase 7 Gate J.","NEVER over-simplify into thin, conversational sentences. A sentence can be grammatically complete yet still too shallow for a thesis (e.g. \"It explains one specific thing.\", \"The opposite can also occur.\", \"Self-efficacy is especially important in social cognitive theory. It explains one specific thing.\"). Do not reduce AI risk by flattening academic prose into short declarative statements that a textbook or a chat reply would use. Keep an appropriately academic register and information load. Enforced by Phase 7 Gate H (thin-sentence check) and Gate J.","NEVER fabricate content to look human. This applies especially to qualitative rewriting (T25–T28) and researcher-trace insertion (T19): do not invent researcher feelings or memories (\"stayed with me\"), positionality (\"As a researcher who had also...\"), non-verbal observations (\"looking down, pausing\"), participant quotes, longer versions of real quotes, \"surprise\" at a statistical result, or a documented \"silence/absence\". Fabrication is an academic-integrity violation AND self-defeating, because freshly generated \"human voice\" sentences read as AI to detectors. T19 may only relocate or lightly rephrase existing researcher-side material. T29 may reconstruct a new interpretive sentence only when it is fully traceable to existing quotations, codes, themes, documented methods, cited literature, or stated boundaries, and only with a completed Source Trace block; if the trace cannot be shown, write author confirmation needed instead of adding the sentence. If the needed material is not in the paper, use a different technique. Enforced by Gate B (protected quotes/data) and the T19/T25–T28 extraction-only rules."]
Detect AI-writing risk patterns in English and Chinese thesis text — English text uses the conservative D1–D17 framework, Chinese text uses the Chinese-text AI-risk module plus shared structure-level checks, and mixed documents are routed by language segment — score paragraph-level and document-level AI risk, and rewrite high-risk sections by reducing shared external-detector-sensitive features such as repeated templates, uniform rhythm, mechanical reporting sequences, and over-smooth academic reasoning.
The scoring system is intentionally conservative and calibrated for structural AI-risk signals commonly detected by external AI detection systems in formal master’s thesis writing.
This skill should not treat a low internal score as proof that the text is safe. When a known detector result is available, such as Turnitin AI = 48%, use it as a calibration signal and adjust the internal scoring more strictly.
Core Operating Architecture (READ FIRST — overrides any conflicting rule below)
Multiple failure modes have been observed in real multi-round use, including score regression, structural over-editing, word-count loss, readability damage, detector-comparison error, and unsupported researcher-trace insertion. The rules in this section exist to prevent them and override any conflicting rule anywhere else in this file.
Principle 0 — The goal is a TARGET, not merely "lower than last time"
The operational objective is to reduce traceable AI-writing-risk patterns in user-provided thesis text and to prepare candidate revisions for comparable external re-test. The target threshold (default 30%, or a stricter value the user specifies) is used only as a closed-loop stopping condition when comparable detector evidence exists; the skill must never guarantee, imply, or optimise for a detector outcome independently of academic integrity, meaning preservation, and evidence-based revision. Chapter scores are the primary closed-loop units; the whole-document score is a target only when a comparable whole-document external test is available. "Lower than the previous version" is NOT success. A version that is the lowest so far but still above the active target is NOT finished — it is work in progress.
Authorized-Use Boundary: this skill may be used only on thesis text the user owns, authored, co-authored, or is explicitly authorized to edit. It supports clarity, academic integrity, and detector-informed risk diagnosis; it must NOT be used to misrepresent authorship, hide prohibited AI use, fabricate research contribution, or bypass an institution's disclosure or assessment rules.
T19/T29 Master Boundary Rule: T19 is relocation or light integration of researcher-side material that already exists elsewhere in the thesis; T19 never creates new interpretive content. T29 is evidence-based reconstruction; T29 may add a new interpretive sentence only when a completed Source Trace block proves it is grounded in existing thesis materials, codes, quotations, methods, findings, or cited literature. For qualitative passages, any new interpretive sentence must use T29, never T19. If a source trace cannot be established, write "Author confirmation needed" instead of adding the sentence.
Strict Target Warning: if the user sets a target below 30% (especially below 15%), warn that the target may be unrealistic depending on detector behaviour, thesis genre, standardised methodology language, and required academic terminology; the skill can attempt risk-pattern reduction but cannot guarantee the target; and academic integrity, protected content, readability, and meaning preservation override the numeric target. A stricter user target changes the target threshold ONLY — it never relaxes any integrity, minimal-edit, no-fabrication, word-count, or quality-gate rule.
Definition of done:
A chapter is DONE only when its measured external score is < 30% (or the user's target).
The whole task is DONE only when every externally measured target unit is below target. If the external detector supports only chapter-level testing, the task may be DONE once every chapter is below target; if a comparable whole-document score is available, the whole document must also be below target.
Until then, the skill must keep proposing the next rewrite round. It must never present an above-target version as the final result or imply that no further reduction is possible.
Never-stop-early rule:
Reaching a new lowest score does not end the work; it only updates the baseline. If that lowest score is still ≥ 30%, immediately plan the next round on the highest-remaining chapter.
The legitimate reasons to pause are: (a) all measurable target units are below target; (b) the user asks to stop; (c) the full escalation ladder (Principle 5) has been exhausted and documented on a chapter AND the user has been told which specific structural constraint is blocking further reduction; (d) Rewrite Fatigue Detection is triggered; (e) no comparable external re-test is available; or (f) continuing would risk changing protected academic content or damaging readability. Rewrite Fatigue Detection overrides the never-stop-above-target rule: when fatigue triggers, restore the lowest-ever comparable version, report the next untried safe option, and do not run another round until the user chooses to continue.
"I cannot reduce it further" may only be said after every rung of the Principle 5 escalation ladder has been tried and documented for that chapter.
Principle 1 — Closed loop, one chapter per round
This skill does NOT rewrite a whole thesis in one response. Internal D1–D17 scoring cannot reliably predict the external detector result, so the only trusted verdict is a real re-test.
The mandatory loop is:
pick the single highest-scoring chapter that is still at or above the target (default 30%)
→ rewrite ONLY that chapter, using minimal edits at the current escalation rung
→ output the rewritten chapter + evidence
→ STOP and ask the user to re-test with CNKI / Turnitin
→ if the new score is BELOW target: lock it as done, move to the next-highest chapter
→ if the new score is lower than before but STILL above target: keep this version as the new baseline, mark the chapter PROGRESS (not DONE), AND plan the next round on the SAME chapter, moving UP one escalation rung (Principle 5). "Plan" means describe the next round; do NOT execute the next rewrite in the same response. Wait until the user supplies a comparable external re-test of this version (or the chapter text/version to revise) or explicitly asks to continue, per the mandatory re-test stop.
→ if the new score stayed the same or went UP: roll back to the chapter's lowest-ever version, then move UP one escalation rung and try a DIFFERENT technique on the same chapter
→ repeat until the chapter is below target or the escalation ladder is exhausted
Always tell the user explicitly: "Rewrite one chapter, re-test it, and continue. We keep going on each chapter until it is below the active target threshold, not just lower than before." The active target is the user-specified threshold when provided; otherwise it defaults to below 30%.
Principle 2 — Minimal edit only, never regenerate
The biggest cause of score regression (e.g. a chapter rising from 36% to 100%) is letting the model re-generate a paragraph as fluent new prose. Fluent AI-generated academic text carries strong AI features by construction.
Rules:
Rewrite by editing the EXISTING sentences: substitute individual words, reorder clauses, split long sentences, recast voice/structure, and relocate or integrate researcher-trace material drawn from existing content.
Every sentence in the output must be traceable to a specific original sentence (or be a permitted researcher-trace/breakpoint sentence based on existing content).
Preserve as much of the original human wording as possible — original human phrasing is what keeps the score down.
Whole-paragraph or whole-section regeneration is FORBIDDEN, even for A-class / P0 paragraphs.
Back-translation is FORBIDDEN. Never translate text to another language and back (e.g. Chinese → English → rewrite → Chinese) to reduce AI features. Round-tripping through translation is whole-paragraph regeneration in disguise: it discards the original human wording and emits fresh machine-distributed text — the exact failure mode that drove a chapter from 36% to 100%. Edit the existing sentences in place instead.
Do NOT delete content or merge sentences to reduce AI features. Splitting one sentence into two is allowed; merging two sentences into one is not allowed AS A ROUTINE AI-RISK TECHNIQUE (it loses length and is rarely necessary). Exception: a merge IS permitted to REPAIR a fragment, an accidentally split clause, or a thin/over-conversational sentence created during revision (Gate H); the repaired sentence must preserve the original meaning and must not reduce the chapter's substantive content. See Principle 4.
"Aggressive Structural Rewrite" means aggressive REORGANISATION of existing sentences (reordering, re-segmenting, changing entry point), never aggressive REWRITING into new prose.
Priority note: the principles are numbered in order (P1–P6) and the workflow Phases run in order (Phase 1 → 1.5 → 1.6 → 1.6A → 1.7 → 2 → 2b → 3 → 4 → 4.5 → 4.5A → 5 → 5.5 → 6 → 7 → 8 → 9). Numeric order is for reference only; it is NOT the conflict-resolution order. When two rules ever appear to conflict, apply this fixed priority instead: protect data/citations/quotes/hedges > preserve word count > readability soft-limits > AI-risk reduction; and external re-test result > internal risk estimate.
Conflict Resolution Hierarchy (full order, highest first): (1) academic integrity and protected elements; (2) user-specified scope and target; (3) Core Operating Architecture and Principles 0–9; (4) language-route rules (English D1–D17 vs Chinese route); (5) task-mode and staged-execution rules; (6) Phase gates A–J; (7) reference modules and technique files; (8) examples and prompts. Examples never override mandatory rules. Within this order, the data/word-count/readability/AI-risk and external-vs-internal sub-priorities above still apply.
Canonical Output Authority: SKILL.md is the only authority for workflow-level output structure (Phase order, target lock, ledger, Phase 7 Gate A–J, Phase 8/9 summary, external re-test stop, DOCX Output Gate). Reference files may provide paragraph-level evidence templates, examples, and technique-specific subfields only; if any reference output template conflicts with SKILL.md, SKILL.md overrides it.
Minimum Execution Map (anti-phase-skipping; full definitions remain in their own sections):
Issue list in the required (or user-provided) audit format
Principle 3 — Red lines, target lock, and the version ledger
Red line (never regress): Each chapter's lowest-ever measured external score is a hard ceiling for that chapter. A rewrite that scores higher than the chapter's lowest-ever version is discarded and the lowest-ever version is restored.
Target, not ceiling: The red line prevents regression; it does NOT define success. Success is reaching below the target threshold (default 30%). Keep working a chapter until it is below target, even after it reaches a new lowest score.
Protection floor = the target: Only a chapter already below the target threshold (default 30%) is protected and left alone. A chapter between 30% and 40% is NOT protected and must keep being rewritten — earlier versions of this skill wrongly froze chapters below 40%, which caused premature stopping above the 30% goal. Do not protect any chapter that is still at or above 30%.
Target lock: Each round may only touch ONE chapter by default: the highest current measured chapter that is still at or above the target. Everything below target is left untouched. Bounded-unit exception: if an external report highlights only a bounded subsection or a fragment cluster (e.g. one flagged sub-section of the introduction), the round MAY target that bounded unit instead of the whole chapter, while still tracking it under that chapter's ledger.
Escalation, not surrender: If a chapter changes by less than 5 percentage points in a round but is still above target, do NOT stop and do NOT merely "ask the user to confirm". Move up one rung on the escalation ladder (Principle 5) and try a stronger, still-safe technique on the same chapter next round.
Principle 4 — Word-count preservation (never shrink the paper)
Compression and merging are forbidden as AI-reduction methods. A thesis usually has a minimum word-count requirement, and shrinking it is a serious failure even if the AI score drops.
Rules:
Every rewritten paragraph must have word count ≥ the original paragraph (one-to-one rewrite), with the acceptable range being the original length up to about +15%. If an over-cap original paragraph is split into two or more descendant paragraphs at safe logical boundaries, Gate F is assessed on the COMBINED word count of all descendants against the original parent paragraph (record Parent Paragraph ID → New Paragraph IDs); the combined count must be ≥ the original parent.
Over-cap exception (resolves the conflict between "never shrink" and the 200-word / 12-sentence readability cap): the +0% to +15% growth target applies only when the original paragraph is WITHIN the readability cap. If an original paragraph already exceeds 200 words or 12 sentences, do NOT force further expansion. In that case preserve every piece of substantive content, meaning, evidence, citation, variable, datum, and conclusion; do not add filler merely to grow the count; keep the revised paragraph no longer than the original unless a source-supported clarification genuinely requires it; and prefer splitting the over-long paragraph at a natural logical break (this raises sentence count and readability without losing content) over leaving one mega-paragraph. Record Gate F as "Pass — no substantive shrinkage; original already exceeded the readability cap." This exception NEVER licenses removing or condensing substantive content; it only lifts the artificial growth target for paragraphs that are already too long.
Content deletion vs connector removal (resolves a common deadlock): deleting substantive content — data, reasoning, citations, claims, examples, limitations, findings — is FORBIDDEN. Removing a low-information connective or empty formulaic opener ("Furthermore,", "It is worth noting that", "综上所述") IS allowed, but only when (a) the logical relation stays clear without it and (b) the words removed are compensated within the same paragraph by concrete detail already in the thesis. Connector removal with same-paragraph compensation is NOT content deletion and does not violate the no-shrink rule.
AI features must be reduced by CHANGING how ideas are expressed (reorder, recast, vary rhythm, differentiate structure, integrate researcher reasoning already present), never by REMOVING ideas or condensing them.
"Compression", "condensing", "merging templates", "shortening", "trimming", and "removing repeated explanation" are all FORBIDDEN as length-reducing operations. Where older techniques (e.g. T17, T18) say "compress", reinterpret them as "rewrite the repeated template into varied, equally-long-or-longer prose" — break the pattern by restructuring and adding specificity, not by cutting words.
If breaking a repeated template would remove words, you must compensate by expanding elsewhere in the same paragraph (e.g. add concrete detail, a researcher-view judgment sentence, or a process narration sentence drawn from existing content) so net length does not fall.
Splitting a long sentence into two shorter sentences is encouraged (it varies rhythm AND tends to add words). Merging sentences is not allowed as a routine AI-risk technique, but IS allowed to repair a fragment or thin sentence (the repair exception in Principle 4 / Gate H).
Phase 7 Gate F enforces this: any rewritten paragraph shorter than its original FAILS the gate and must be redone.
Word-count preservation must NOT be achieved by generic filler, duplicated reasoning, empty transition sentences, or unsupported elaboration. Any added wording must preserve or clarify existing content and must pass Gate J's low-information-filler review. Reaching length by padding is itself an AI signal and a quality defect.
Report the before/after word count for every rewritten paragraph (see Phase 5.5 and Phase 8).
Principle 5 — Escalation ladder (how to keep reducing a stubborn chapter)
When a chapter is still above target, escalate through these rungs in order. Each rung is progressively more structural but every rung still obeys minimal-edit (Principle 2) and word-count preservation (Principle 4). Never jump straight to a high rung; never regenerate prose; never compress.
Rung 1 — Sentence-level: vary openings, transitions, sentence length, lexical choices (T1–T13).
Rung 2 — Rhythm & cadence: break uniform sentence-length patterns; split long sentences; vary clause order within sentences (T11, Pass 2).
Rung 3 — Paragraph architecture: change each paragraph's entry point and internal order; differentiate neighbouring paragraphs that share a template (T14, T15).
Rung 4 — Reporting-sequence & template breaking: reorder reporting steps; de-template methodology/variable/result patterns (T17, T18 — length-preserving versions).
Stop condition (centralised): escalation stops only by marking the unit PAUSED or BLOCKED, and only when academic integrity or protected content would be put at risk, readability damage cannot be avoided, external evidence is non-comparable, Rewrite Fatigue triggers, the user asks to stop, or the full six-rung ladder has been exhausted and documented. Escalation never stops by silently marking an above-target unit DONE.
Rung 5 — Source-extracted researcher-trace integration: relocate or lightly integrate more researcher-view judgment, process narration, scope-narrowing, boundary, and existing-data-anchor material already present in the thesis across the chapter (T19), as a previously observed potentially useful reducer (effectiveness not guaranteed; confirm by comparable external re-test). Never generate new researcher voice. "Integration" here means relocation of existing material, NOT saturation: use it sparingly, at most one relocated researcher-trace sentence per high-risk paragraph, and never insert researcher-trace sentences mechanically across consecutive paragraphs (repeated mechanical insertion is itself an AI-risk pattern).
Rung 6 — Functional reorganisation: change what each paragraph DOES (e.g. turn a flat "definition → source → result" report into a problem-driven or contrast-driven passage) by reordering and recasting the sentences WITHIN that paragraph. This never means shuffling the order of paragraphs across the section or changing the chapter's argument flow (see Principle 7). Still never regenerate prose; keep word count and the paragraph's position unchanged.
Rules:
Track the current rung per chapter in the ledger.
After each re-test that is still above target, advance one rung (or, if the last rung produced a clear drop, repeat the same rung more thoroughly before advancing).
Only after Rung 6 has been applied thoroughly and the chapter still will not drop below target may the skill tell the user that a specific, named structural constraint is blocking further reduction (e.g. an unavoidable standardized methodology section) — and even then it should offer the best available below-baseline version and ask whether to continue trying.
Escalating rungs must never violate Principles 2 and 4 (no regeneration, no shrinking).
Rewrite Fatigue Detection (mandatory stop condition):
Even before Rung 6 is exhausted, declare rewrite fatigue and pause if ANY of these is true for a chapter:
3 or more complete rounds (rewrite + external re-test) have been done on this chapter (this is a hard stop checkpoint — the user may explicitly authorize ONE additional controlled round, but the skill must never silently continue past it); OR
the change in measured external score across the last two rounds is < 3 percentage points (in either direction); OR
a rewrite increased the score (already handled by Score Regression Guard — fatigue is a wider net).
On fatigue, do NOT keep grinding the same chapter. Take this sequence:
Roll back to the chapter's lowest-ever measured version.
Look at the "Tried techniques on this rung" column in the ledger (see below). Try ONE clearly untried technique appropriate to the current rung.
If no untried technique remains for the current rung, advance one rung.
If Rung 6 is reached and still fatigued, STOP this chapter, report the situation honestly to the user, and recommend external editing rather than another model-driven round. Never imply that further mechanical rewriting will help when the data says it will not.
Principle 6 — Preserve structure and readability (no merged mega-paragraphs, no displaced headings)
Reducing the AI score must never make the paper read worse. Two failure modes are forbidden:
(a) Displaced or absorbed headings. Section and sub-section headings such as "1.1 Research Background", "Chapter 2 Theoretical Foundations", "5.2.1 Procedural Control Methods", as well as figure/table captions and numbered/bulleted list markers, are HARD STRUCTURAL BOUNDARIES.
Never merge body text across a heading.
Never pull a heading into a body paragraph or let a paragraph run straight into the next heading.
Never move a heading, renumber it, or strand it at the end of a paragraph.
Every heading keeps its own line, with the paragraph break before and after it exactly as in the original. If a heading text reads like "1.1 Research Background", it must appear on its own line, not inside or at the tail of a sentence.
Rewriting happens strictly INSIDE the body text between two headings; the headings themselves are protected elements (Gate B) and the boundaries are checked by Gate G.
(b) Merged mega-paragraphs. Do not combine paragraphs to fight cross-paragraph repetition. Merging produces over-long blocks (e.g. 212 words / 18 sentences) that are exhausting to read.
Keep the original paragraph breaks. Cross-paragraph repetition (D13) is reduced by DIFFERENTIATING neighbouring paragraphs (changing each one's entry point, order, and function), NOT by merging them.
A rewritten paragraph must stay within readable limits: about 160 words and about 9 sentences maximum (soft target), and must never exceed 200 words or 12 sentences (hard cap). If staying under the cap conflicts with reducing AI risk, keep the paragraph split — never merge to a longer block.
"Fragment cluster" and "paragraph group" are DIAGNOSIS units (for planning cross-paragraph differentiation). They are NOT licence to output one merged paragraph. Each original paragraph remains a separate paragraph in the output.
If a single original paragraph is itself longer than the hard cap, you may split it into two paragraphs at a natural logical break (this improves readability and adds no AI risk), but you may never merge.
Gate G (Phase 7) enforces both (a) and (b). Any output that violates them fails and must be redone.
Principle 7 — "Reorganisation" means within-paragraph only (never reorder paragraphs or change the argument)
Throughout this skill, "reorganise", "reorder", "change entry point", "paragraph architecture", and "functional reorganisation" mean changing the order and framing of sentences INSIDE a single paragraph, plus differentiating neighbouring paragraphs from each other. They do NOT mean:
shuffling the sequence of paragraphs within a section;
changing the logical development or argument structure of the chapter;
moving content from one section to another.
The document's paragraph order and argument flow are preserved. The skill has no technique that rearranges whole paragraphs or alters how the argument unfolds, and it must never invent one — doing so would break logical coherence and the reader's ability to follow the thesis.
What IS allowed (reporting-order variation within a unit): inside a single paragraph you may change the entry point and the order of its sentences — for example, open with the problem or the result before the background, instead of the AI-typical "background → purpose → method → result → conclusion" order. This is encouraged (T18, T14) and is how "reordering the argument's presentation" is achieved safely. What is NOT allowed: moving paragraphs around, changing which section makes which point, or altering the chapter's overall line of argument. Reorder the presentation inside a paragraph; never reorder the paragraphs or rewire the chapter.
Principle 8 — Safe sentence splitting (no fragments, no choppy prose)
Splitting long sentences is a useful rhythm tool, but it must never produce grammatically incomplete fragments or a stop-start, half-sentence reading experience. Three failure modes are forbidden.
Detection method — UNIVERSAL completeness test.
A fragment may start with ANY word and be ANY length. Do not detect fragments by matching a fixed list of opening words ("Including / Drawing on / Using / Based on / Considering ..."), and do not look only at a short 3–7 word window. Those approaches are a known failure mode that misses real fragments such as "Work engagement, and creative inspiration.", "Workplace communities, and internal corporate channels.", "Promoting, and implementing new ideas.", and any long "Including ..." continuation.
Instead, for every unit ending in a period, ask:
Does it have its OWN grammatical subject?
Does it have its OWN finite (tensed) main verb — not just an -ing / -ed participle, not just a to-infinitive?
Does it express a complete thought on its own?
If any answer is no, it is a fragment, regardless of its first word or its length.
Common types (illustrative, NOT a closed match-list):
Subordinate-clause fragments: "When employees interact with AI in daily work." — must attach to a main clause.
List/enumeration tails: "...the mediating roles of self-efficacy. Work engagement, and creative inspiration." / "...through online social platforms. Workplace communities, and internal corporate channels." / "...dependent variable. Gender, age...".
Subject-less verb phrases: "...it raises the problem. Builds the theoretical model.".
Gerund/participle continuations: "...statistical analysis. Including multivariate analysis, ..." / "...the model. Using SEM to test the paths." — -ing with no finite verb.
Choppy mechanical chopping into many ~10-word units that creates a robotic stop-start rhythm.
Rules:
A sentence may be split ONLY when both resulting parts independently pass the subject + finite-verb test. The safe split test: cover everything before the proposed period and read what remains; if it lacks its own subject or its own finite verb, do NOT split there.
NEVER place a period inside a list, before "and X", before a bare verb phrase, before an "Including / Such as / For example ..." phrase, or before any -ing/-ed continuation. In every such case keep it as one sentence.
After splitting, each piece must stand on its own and read aloud as a complete sentence.
Prefer a natural mix of short, medium, and long sentences. As a guide, keep most sentences roughly 8–30 words; an occasional shorter sentence is fine for emphasis, but avoid three or more ultra-short sentences in a row.
Upper bound, too: Do not over-correct into long, tangled sentences. Keep sentences at or under about 30 words and at most two subordinate clauses. A sentence that grows long or heavily nested during rewriting must be split into two complete sentences.
If reducing rhythm uniformity would require creating a fragment, do NOT split — vary the rhythm another way (reorder clauses within the sentence, change the opening, recast voice) instead.
Gate H (Phase 7) applies the universal completeness test to every period and is output-blocking.
Principle 9 — Grammatical correctness and no jarring meta-commentary
Reducing the AI score must never introduce grammar errors or out-of-place asides. Two failure modes are forbidden:
(a) Grammar errors. The output must be correct academic English. In particular:
Subject–verb agreement must hold (a singular subject takes a singular verb; a plural subject takes a plural verb). Rewriting that changes a subject from plural to singular (or splits a sentence) must update the verb to match.
Tense, articles, prepositions, and pluralisation must remain correct.
AI features must NEVER be reduced by deliberately inserting grammar mistakes or "non-native errors". Slight rhythmic plainness is fine; actual errors are not.
Gate I (Phase 7) checks grammar, with special attention to subject–verb agreement at every point where a sentence was split, recast, or had its subject changed.
(b) Jarring meta-commentary. Do not insert sentences that explain, justify, or comment on the writing or the research design from outside the argument, such as:
"This detail was included to improve measurement precision."
"This sentence is added to clarify the logic."
"The following paragraph explains the mechanism."
These read as abrupt logical jumps and look machine-inserted. Rules:
Every sentence must follow from the surrounding content and advance the thesis's own argument.
Researcher-trace sentences (T19) are permitted only when they express the author's genuine reasoning within the local argument and connect smoothly to the sentences before and after. They must never be generic justifications of methodology, measurement, or of the rewrite itself.
A researcher-trace or transition sentence that does not connect logically to both its neighbours is a defect — remove it or rewrite it so the paragraph reads as one continuous line of reasoning.
Gate J (Phase 7) checks for inserted meta-commentary and logic jumps.
Chapter Version Ledger (required before every round)
Before starting any rewrite round, output and maintain this ledger. If the user cannot supply the previous ledger on a resumed task, rebuild it from the latest detector report before rewriting anything.
| Chapter | Current measured score | Lowest-ever score | Source version of lowest | Current escalation rung | Tried techniques on this rung | Rounds done | Below target (<30%)? | This round: rewrite? |
|---------|------------------------|-------------------|--------------------------|-------------------------|-------------------------------|-------------|----------------------|----------------------|
| ... | ... | ... | ... | 1–6 | e.g. T17, T21 | int | Yes / No | Yes (target) / No |
Rules:
The "rewrite?" column should normally say Yes for exactly ONE chapter per round: the highest current measured chapter that is still at or above the target (default 30%). It may say Yes for two chapters only if the user explicitly requests a two-chapter batch and agrees to re-test each chapter separately.
Any chapter already below the target (default 30%) is marked done and is not rewritten further.
After a re-test, update the ledger: record the new score, update lowest-ever, update the escalation rung, and mark "Below target?" Yes/No. If a chapter regressed, restore the lowest-ever source and record the rollback.
The task is complete only when every chapter shows "Below target? = Yes". As long as any chapter is still at or above target, name the next round's target only as a post-retest candidate and do not present the work as finished; do not plan detailed rewrite actions for that candidate until the user provides the re-test result for the current round.
Never start a new round without an up-to-date ledger.
This skill is only for reducing AI-writing-risk patterns and AI detector scores.
It is not designed for plagiarism reduction, similarity-score reduction, citation rewriting, or Turnitin Similarity Index optimization.
If the user asks for similarity reduction or plagiarism reduction, treat it as a separate task and do not mix it with AI-rate reduction.
Task Routing Rule
Before any diagnosis or rewriting, classify the user request and route it:
Skill-Audit Mode — the user asks to inspect THIS skill or its reference files for errors, contradictions, omissions, or optimisation. Skill Audit Mode is fully separate from Thesis Rewrite Mode: when the input files are SKILL.md or the reference modules, do NOT score them as thesis paragraphs and do NOT apply D1–D17 rewriting; audit them for internal consistency, routing completeness, safety boundaries, contradictions, missing execution gates, stale terminology, broken cross-references, and agent usability. Do NOT run thesis D1–D17 scoring and do NOT rewrite thesis text. Output rule-level problems, severity, affected files, suggested edits, and reasons, using this format:
Issue ID:
File / Section:
Problem type: contradiction / omission / ambiguity / execution burden / unsafe wording / terminology drift
Original wording:
Recommended replacement:
Reason:
Priority: High / Medium / Low
When the user asks for “原文 + 修改后内容” (original + revised), a compact variant is acceptable: Issue ID / File-Section / Problem type / Original wording / Recommended replacement, adding Reason only where needed for clarity. If the user provides a custom audit loop or table format, follow the user's format while preserving the core fields (location, original wording, problem, suggested fix, reason/priority). Skill-Audit Mode still must not run thesis D1–D17 scoring or rewrite thesis text.
AI-Writing-Risk Mode — the user asks to reduce AI-writing risk / AI rate / AIGC traces / Turnitin-AI / CNKI-AIGC / GPTZero, etc. This is the main thesis workflow (Diagnosis-Only / Working / Quick / Single-Batch / Full Staged below).
Similarity / Plagiarism Mode (out of scope) — if the user asks for similarity reduction, plagiarism reduction, Turnitin Similarity Index, 查重, 相似度, or 降重 with NO AI-writing context, do not proceed under this skill. Ask whether they actually want AI-writing-risk reduction instead. This skill never optimises text-similarity / 查重 scores.
Assembly Mode — only after chapter-by-chapter accepted versions already exist and have been externally re-tested. Assembly means combining locked accepted chapter versions into a report or DOCX. It does NOT mean rewriting a whole thesis in one pass. The capability assemble_locked_rewritten_document refers ONLY to this assembly of already-accepted chapters (and single-chapter/batch output for the current round), never to one-pass whole-thesis rewriting.
Language Routing Rule
English thesis text: use D1–D17, the English cliché banks (Gate J), and the rewrite techniques.
Chinese thesis text: use the Chinese-text AI-risk module (references/chinese_text_ai_risk.md) plus the structure-level checks; do NOT apply the Chinese-student-English cliché rules (those are for English text written by Chinese authors, not for Chinese text).
Mixed Chinese–English thesis (e.g. English body + Chinese abstract/questionnaire): process by language segment, and protect bilingual term consistency (a term's Chinese and English forms must stay aligned).
Method routing: apply the qualitative module (references/qualitative_authorship_restoration.md) and T25–T28 only to qualitative/mixed passages; do NOT apply qualitative researcher-voice techniques to a quantitative passage.
Quotation-evidence protection (D21 and its Chinese-route equivalent): when a uniform-citation pattern is flagged, the default action is report-first. Before any rewrite planning, do NOT automatically change quotation count, quotation length, participant distribution, or theme coverage; only surrounding framing may be varied, and only where the existing analysis supports it (see detection_principles.md D21).
Mixed-language paragraph: if a single paragraph contains both English and Chinese thesis prose, split it by language span where possible and score each span under its own route; protect bilingual technical terms, citations, and translated construct names before scoring, and never translate one span into the other language to unify the route.
For Chinese thesis text, the visible evidence must use the Chinese-route fields below (not a full English D1–D17 table):
Mode routing summary (definitions below remain canonical; this table only consolidates them):
Task type
Trigger
Mode
Evidence depth
Stop point
Audit this skill
User asks to inspect skill/workflow/reference files
Skill-Audit
Issue-level audit format (or user's custom format)
After issue list; never scores thesis
Inspect thesis without rewriting
inspect/review/audit thesis text
Diagnosis-Only
Route-appropriate scoring, no rewrite
After diagnosis report
One quick paragraph
Explicit quick request, or single paragraph with no files/scores
Quick
Minimum evidence set
After single-paragraph output
≤10 selected paragraphs
Small selected batch, no full-document request
Single-Batch
Full evidence for those paragraphs
After batch output
Ordinary chapter revision
Default for normal thesis tasks
Working
Full evidence for target paragraphs; compact skip records otherwise
Stage 5 re-test stop
Long doc / DOCX / external report / >10 targets
Task Size Routing Rule
Full Staged
Staged full evidence
Stage 5 re-test stop per round
Full-evidence thesis audit
Explicit full-audit request
Thesis-Evidence Audit
Full tables for every included paragraph
After audit (no rewrite unless asked)
Combine accepted chapters
All chapters externally below target
Assembly
Assembly checks + DOCX gate
After assembled output
Before execution, identify the task mode.
Diagnosis-Only Mode
Use Diagnosis-Only Mode when the user asks to inspect, review, audit, identify risks, or list problems in thesis text without rewriting. If the user asks to inspect this skill, its workflow, or its reference files, use Skill-Audit Mode instead and do not run thesis D1–D17 scoring.
Rules:
Do not rewrite thesis text.
Output risk locations, reasons, severity, and suggested techniques only.
Do not create a rewritten version unless the user explicitly asks for rewriting.
Working Mode
Default mode for normal thesis revision.
Rules:
Show full execution evidence for rewritten high-risk (target) paragraphs. For each rewritten target paragraph, show the minimum evidence packet: Paragraph ID; route; hit dimensions or Chinese-route risk groups; selected techniques; protected elements before/after; exact Pass 1–3 actions; Gate A–J summary; original/revised word count; candidate status pending external re-test.
For low-risk or skipped paragraphs, give a compact skip record — paragraph ID, section type, final risk estimate, primary skip reason, and protected-element status — not a full D1–D17 table.
Include protected-element result and quality-gate summary.
Do not overload the user with full D1–D17 evidence for every paragraph unless necessary.
Thesis-Evidence Audit Mode
Use this mode only when the user explicitly asks for full evidence, full audit, complete paragraph-level diagnosis, or detailed execution proof for THESIS TEXT. If the user asks to audit the skill file, workflow, or reference modules themselves, use Skill-Audit Mode instead. This mode controls evidence depth, not task size: a long task in this mode still follows Full Staged execution.
Rules:
Show D1–D17 scoring.
Show dimension-to-technique mapping.
Show three-pass evidence.
Show protected elements before and after rewriting.
Show Gate A–J results for every rewritten paragraph or rewritten unit. Gates F–J are mandatory whenever text is rewritten, including quick single-paragraph mode.
Quick Mode
Use Quick Mode when EITHER (a) the user explicitly asks for a quick rewrite/check or says “just this paragraph”, OR (b) the user provides only one paragraph, no uploaded thesis/chapter/DOCX/PDF detector report or external-score report, and no external detector score. An optional same-author style sample, the single source paragraph file, or one short paragraph-level detector excerpt does NOT disqualify Quick Mode, but the uploaded file role must be stated explicitly. A thesis chapter, full thesis, or external detector report DOES disqualify it.
When Quick Mode is inferred rather than explicitly requested (case b), state: “Scope = Quick single-paragraph mode; no chapter-level or document-level score is produced,” so the user can redirect.
Quick Mode Anti-Misrouting Rule: do NOT use Quick Mode when the request mentions "chapter", "section", "thesis", "paper", "DOCX", "external report", "CNKI", "Turnitin", "full text", "整章", "全文", "论文", "检测报告", or includes any uploaded long document — even if the user also says "quickly" / "简单看一下". Route those to Full Staged Mode or Single-Batch Mode by paragraph count and evidence availability.
Quick Mode still requires minimum evidence: scope statement; hit dimensions (or Chinese-route risk groups); selected techniques; protected-elements check; a one-line Gate A–J summary for the rewritten paragraph; and the statement that no chapter-level or document-level score is produced.
Score Terminology Glossary
Use the following terms consistently.
external_detector_score: the score reported by CNKI, Turnitin, GPTZero, Originality.ai, or another external detector.
chapter_red_line: the lowest current measured external score for a chapter.
raw_paragraph_risk: the internal D1–D17 weighted paragraph score before floors.
paragraph_risk_index: the internal paragraph risk score after floors.
overall_risk_index: the internal document-level risk estimate, not an external detector result.
AI feature value: an external detector’s own reported value; record it as external evidence only.
internal risk estimate: any score generated by this Skill without an external detector re-test.
Mandatory rule:
Internal scores help locate risk. They must not be presented as proof that an external detector score has decreased.
Intent Confirmation Rule
Before starting Phase 1, check whether the user is asking for AI-writing-risk reduction or similarity/plagiarism reduction.
If the user mentions “Similarity Index,” “similarity,” “plagiarism,” “查重,” “相似度,” or “Turnitin Similarity,” respond with:
This skill only reduces AI-writing-risk patterns. It does not optimize plagiarism, similarity score, or Turnitin Similarity Index. Please confirm whether you want to continue with AI-writing-risk reduction.
If the user provides an AI detector report, AIGC report, Turnitin AI report, CNKI AIGC report, GPTZero report, or Originality.ai report, continue with AI-writing-risk reduction.
Triggers
"降AI" / "降低AI率" / "降低AIGC检测率"
"AI detection" / "reduce AI score" / "lower AI rate"
"改写降AI" / "去AI痕迹" / "AI痕迹检测"
Uploading an English academic paper with AIGC reduction intent
User reports a mismatch between internal AI score and Turnitin/GPTZero/Originality.ai score
These triggers route the task to academic-integrity-preserving risk-pattern revision — not detector evasion, fabricated humanisation, or plagiarism/similarity manipulation. The skill reduces shared AI-writing risk patterns by minimal edits to the author's own text; it never bypasses detectors, fabricates content, or routes text through external rewriting services.
Universal AI-Feature Reduction Rule
This skill aims to reduce AI-writing features that are commonly sensitive across different AI detection systems.
It does not optimize for one detector. External detector reports are used only as evidence for locating risk areas.
The core reduction targets are:
repeated academic templates;
repeated paragraph function paths;
mechanical methodology and empirical reporting;
predictable reporting sequences;
uniform sentence rhythm and low burstiness;
over-smooth reasoning chains;
continuous AI-like fragments in abstract/introduction;
repeated hypothesis-development routes;
repeated result → implication loops in discussion or conclusion;
lack of human research judgment, boundary, decision trace, or process narration.
Mandatory rule:
Convert detector-specific findings into shared risk categories before rewriting.
Select rewrite techniques according to risk category, not detector name.
Use section-level rewriting when the risk appears across paragraph groups.
Do not rely on synonym replacement, random short sentences, or general polishing.
Preserve all protected elements, including citations, variables, hypotheses, coefficients, p-values, model names, table numbers, and statistical conclusions.
Validated Researcher-Trace Rule
Validated finding:
In prior task testing, researcher-view judgment sentences and process narration appeared useful for some descriptive, overly smooth, abstract, or mechanically explanatory paragraphs. Treat this as a conditional strategy, not a universal fix.
Mandatory rule:
This strategy must be treated as a formal Phase 4 rewrite strategy.
T19 = source-extracted relocation ONLY: it may move, split, or lightly rephrase researcher-side judgment/process/boundary material that ALREADY EXISTS in the thesis. If a sentence is newly COMPOSED from existing thesis facts rather than relocated, classify it as T29 (evidence-based reconstruction), not T19. Either way a completed Source Trace block is required; if no source can be identified, do not write the sentence.
It should be marked as a High-Efficiency Strategy.
Use this strategy only when the added sentence can be directly grounded in existing thesis content. Do not insert researcher-trace sentences into statistical-result paragraphs unless the sentence is tied to the reported table, coefficient, sample, model, measurement choice, or stated finding.
The added sentence must be based on existing thesis content. It must not introduce new data, new theory, new references, or unsupported examples.
Project-Level Working Structure
For long thesis documents, use a two-level working structure:
Master overview
thesis title, chapter structure, total paragraph count
current external AI detector result if available, including detector name, score type, score value, and highlighted section evidence
document-level AI risk summary
high-risk sections and rewrite priority
chapter status matrix
Chapter task notes
section type
detected AI patterns
paragraph-level risk points
rewrite strategy
completion status
This structure is especially useful when the thesis has more than 50 pages or when any external AI detector score is above 30%.
Mandatory project-state rule:
If the task involves multiple chapters, update the Master Overview after each completed round's Stage 4 final output and before the Stage 5 mandatory re-test stop. Do not use "Stage 4" to mean "Phase 4": Stage 4 is the round-level final-output stage, while Phase 4 is target selection / prioritisation. Execution order is locked — the Phase workflow runs inside the round first, then the Stage output. A task may not jump from Phase 7 quality gates directly to Done; it must pass Stage 4 scope-aware output and then the Stage 5 external re-test stop, unless the user explicitly selected Quick Mode with no detector-score objective.
Terminology Rule: Phase denotes the executable workflow steps and is the ONLY control of execution order; Stage is a user-facing summary grouping and must never override, skip, or reorder Phase execution. Mapping: user-facing Stage 1 = Phase 1–3; Stage 2 = Phase 4–5.5; Stage 3 = Phase 7; Stage 4 = Phase 8–9; Stage 5 = the external re-test checkpoint.
The Master Overview must include chapter status, completed batches, remaining high-risk sections, baseline version, latest external score, and next recommended batch.
At the start of a resumed task, use the Master Overview as the recovery context.
Global D1–D17 Consistency Override Rule
This skill uses a formal D1–D17 core scoring system for general and quantitative AI-trace risk, plus the qualitative-only supplement D18–D21 for qualitative and mixed-methods papers.
All references to “15 dimensions,” “D1–D15 coverage,” or “42.0 total score” must be treated as outdated unless explicitly marked as historical notes.
Current scoring system:
For English-route thesis text, D1–D17 must be evaluated for every included body paragraph in the current target chapter or selected rewrite batch. For Chinese-route thesis text, do not force the English D1–D17 table; use the Chinese-route evidence template plus shared structure-level checks. For mixed-language documents, apply the required route separately by language segment. "Included body paragraph" does not mean every paragraph in the whole thesis unless the user explicitly requests full-document diagnosis.
Public evidence is incomplete if the Detection Report does not show the required route-specific scoring evidence: English-route paragraphs require D1–D17 scores; Chinese-route paragraphs require the Chinese-route evidence template plus shared structure checks; qualitative or mixed-methods passages require the applicable D18–D21 supplement or its Chinese-route adaptation.
D12, D13, D14, D15, D16, and D17 must always be checked manually or semi-manually.
If any rule conflicts with this 17-dimension system, the 17-dimension rule overrides the older 15-dimension wording.
Score Regression Guard
Before rewriting, identify the current lowest external AI-score version as the baseline version, using the Chapter Version Ledger (see Core Operating Architecture).
If multiple rewritten versions exist, do not assume the newest version is better. Use the version with the lower external detector score as the working baseline. This applies per chapter, not only to the whole document — keep the lowest-scoring version of EACH chapter.
For long thesis documents, do not rewrite the whole document before testing a small batch. Rewrite one chapter, re-test it, then continue (Principle 1).
Recommended process:
Build/refresh the Chapter Version Ledger and identify each chapter's lowest-ever version.
Target-lock the highest current measured chapter that is still at or above the target (default 30%); skip any chapter already below target.
Diagnose their D1–D17 risk dimensions.
Rewrite only those chapters by minimal edit (never regeneration).
Run protected elements check.
Run Phase 7 quality gate.
STOP and have the user re-test the rewritten chapter with the external detector.
After a comparable external re-test, handle the chapter by status:
If the score is below the target threshold: mark the chapter DONE and lock that version within the named detector stream and scope.
If the score decreased but remains at or above the target: record it as PROGRESS, set it as the new lowest-score baseline for that chapter, and plan the next escalation rung for the same chapter. A decrease that is still above target is progress, not completion.
If the score stayed the same or increased: mark the candidate rejected, roll back to the chapter's lowest-ever version, diagnose the failed rewrite direction, and redesign the next small-batch strategy.
Mandatory rule:
A chapter's current measured external score is a RED LINE. A rewrite must be treated as provisional until the user provides an external re-test result. If the re-test does not measurably lower the score, discard the rewrite and restore the chapter’s lowest-ever external-score version.
If Version A has a lower external AI score than Version B, continue from Version A unless there is a clear academic-quality reason not to.
Do not continue rewriting from a version that increased the external AI score.
If a sample rewrite increases AI risk, stop and redesign the rewrite strategy.
If the external AI score increases after a rewrite, return to the lower-score baseline version of that chapter.
Score increase triggers the same action path: roll back to the chapter's lowest-ever version → diagnose failed rewrite direction → redesign strategy → retest with a small batch.
Stalemate vs Rewrite Fatigue (two separate thresholds; Rewrite Fatigue Pause overrides Stalemate Warning): Stalemate Warning fires at <5 percentage points change across two consecutive comparable re-test rounds — mark the strategy stale and plan the next rung, but do NOT auto-pause. Rewrite Fatigue Pause fires at <3 percentage points change across two consecutive rounds, or once three complete rewrite+re-test rounds are done on the chapter — mark the unit Paused unless a clearly untried lower-risk technique remains. Stalemate handling: if a chapter changes by less than 5 percentage points across two consecutive comparable re-test rounds, mark the current strategy as stale, keep the lowest-score version, and plan the next round at the next escalation rung. If the next rung stays intra-paragraph and preserves all structural boundaries, user confirmation is not required beyond the normal external re-test checkpoint. If the next rung would require broader structural reorganisation beyond the current approved unit, ask for user confirmation before execution.
Reference Availability Check: before execution, confirm the four reference modules (references/detection_principles.md, references/rewrite_methods.md, references/qualitative_authorship_restoration.md, references/chinese_text_ai_risk.md) are readable. If any module is missing or unreadable, mark the run "Partial Execution — reference module unavailable", name the missing module, do not produce final scoring that depends on it, and continue only with the parts that remain fully supported.
Reference Path Rule: in packaged skill distribution, load reference files from references/. If the skill is instead being audited from uploaded standalone files, match by canonical basename first (detection_principles, rewrite_methods, qualitative_authorship_restoration, chinese_text_ai_risk) and ignore upload suffixes such as (15) or copy markers.
Score Terminology Glossary: external_detector_score = the score reported by CNKI, Turnitin, GPTZero, Originality.ai, or another external detector. chapter_red_line = the lowest current measured external score for a chapter. raw_paragraph_risk = the internal D1–D17 weighted score before floors. paragraph_risk_index = the internal paragraph risk score after floors. scope_risk_index = the internal risk estimate computed over whatever scope was diagnosed; it is reported as overall_risk_index only for a fully diagnosed full-document scope (otherwise as target_chapter_risk_index / batch_risk_index / fragment_risk_index), and is never an external detector result. AI feature value = an external detector’s own reported value and should be recorded as external evidence only. Priority notation rule: use either A/B/C/D or P0/P1/P2/P3 within one report, not both; if legacy notation appears, the mapping is exactly A=P0, B=P1, C=P2, D=P3.
Target Status State Machine
Every chapter/target-unit's status at the end of a round is reported as exactly ONE of these six labels: Done / Progress / Rejected / Paused / Blocked / Incomplete. Rejected means a comparable re-test regressed or failed to improve against the red line, so the candidate is discarded and the lowest-ever version remains the baseline. Partial Execution is NOT a seventh target-unit status: it is a run-level execution label used only when one or more required reference modules are unavailable. When it applies, the affected target-unit status is Incomplete (unless the missing module is irrelevant to the selected route), and the run must name the missing module and which scoring/rewriting functions were skipped. This is a reporting layer over the existing stop-logic (Principle 0 pause reasons, Rewrite Fatigue Detection, Score Regression Guard); it changes none of those rules, it only standardises how the outcome is named so a unit is never ambiguously "stuck".
Done — the unit's latest COMPARABLE external re-test is below target (default <30%). Only an externally-confirmed below-target unit may be Done. An internal estimate alone can never mark Done.
Progress — the latest comparable re-test decreased versus the chapter red line but is still ≥ target. Continue next round (move up the escalation ladder if <3pp gain).
Rejected — a comparable re-test regressed (higher than the red line) or did not improve against it. Discard the candidate, keep the lowest-ever comparable version as the baseline, diagnose the failed rewrite direction, and escalate one rung on the next round after recording the rollback. A regression is never reported as Progress.
Paused — work is intentionally halted for a legitimate Principle 0 reason (user asked to stop; Rewrite Fatigue triggered; full escalation ladder exhausted and the blocking constraint reported; continuing would risk protected content or readability). A Paused unit may be ≥ target — Paused is the correct label for "above target but should not keep grinding right now". Record the specific pause reason.
Blocked — cannot proceed because a required input is missing: no comparable external re-test available, external evidence incomplete, or detector streams not comparable. Record what is needed to unblock. Do NOT update chapter_red_line while Blocked.
Incomplete — a round was started but its quality gates (A–J) or protected-element checks did not pass, so no acceptable version was produced this round. Roll back to the lowest-ever version and report what failed.
Failure handling summary (condition → status → required action):
Failure condition
Status
Required action
Comparable re-test shows regression (higher than red line), or no improvement against the red line
Rejected / Rollback
Discard the candidate; keep the lowest-ever comparable version as baseline; diagnose the failed rewrite direction; escalate one rung only after the rollback is recorded. Do not mark this as Progress
Gate A–J or protected-element failure
Incomplete
Roll back to lowest-ever version; report which gate failed; rework before any new round
No comparable external evidence / detector streams not comparable
Blocked
Record what is needed to unblock; no red-line update; internal work only with explicit user acceptance
Integrity/readability risk, Rewrite Fatigue, ladder exhausted, or user stop
Paused
Record the specific reason; keep lowest-ever version; resume only on user instruction
Reference module unavailable
Partial Execution
Name the missing module; no final scoring that depends on it
Rule: a unit at or above target is NEVER reported as Done. It is Progress, Paused, or Blocked. This removes the old "can't stop above 30% but also can't continue" deadlock — above-target units that should stop are simply Paused or Blocked, with a reason.
Universal External-Risk Calibration Rule
This skill does not optimize for one specific AI detector.
When one or more external AI detector reports are provided, the reports must be used as risk-location evidence, not as detector-specific rewriting instructions.
The purpose is to reduce shared AI-writing features that may be detected across different AI detection systems.
Common cross-detector AI-risk features include:
long continuous AI-like fragments;
repeated chapter-level or section-level templates;
repeated result → implication loops in discussion or conclusion;
lack of human research judgment, boundary, decision trace, or process narration.
Mandatory rule:
Do not optimize for CNKI, Turnitin, GPTZero, Originality.ai, or any single detector.
Convert detector-specific findings into shared AI-risk categories before rewriting.
Select rewrite techniques according to risk category, not detector name.
If different detectors highlight different sections, treat them as complementary evidence of different AI-risk dimensions.
If any external detector reports a much higher AI risk than the internal score, raise the internal priority level and inspect section-level structure before rewriting.
Rewriting must target structure, rhythm, reporting sequence, and section architecture, not only vocabulary.
Default-Excluded Units
Unless the user explicitly asks otherwise, the following are NOT rewritten, NOT scored against D1–D17, NOT used for word-count compensation, NOT moved or reordered, and should be excluded when defining the external re-test scope so that before/after comparisons stay consistent:
references / bibliography
appendices
questionnaires and survey instruments
ethics statements / consent forms
title page and declaration page
table of contents
figure and table captions (unless an external report specifically flags one)
verbatim participant quotes (unless the task is qualitative quote-balance diagnosis)
equations, formula numbers, and table cell values
If the user asks to include any of these, record the change explicitly and apply the same inclusion in the external re-test scope.
Non-Comparable Detector Handling
External scores are comparable only when they come from the same detector, the same document version, and the same included scope. When detector streams are NOT comparable (different detector, different version, or different included/excluded sections):
Do not judge regression or improvement between them, and do not treat e.g. Turnitin 48% and CNKI 32% as an up/down relationship.
Build separate evidence streams, one per detector.
Use only overlapping highlighted sections for priority selection.
Label the output "External Comparison Not Available" and set affected units' external-comparison status to Blocked. Internal diagnosis or candidate rewriting may still proceed only if the user explicitly accepts that no external score-improvement claim can be made for this round.
Do NOT update chapter_red_line unless a comparable re-test exists.
External Test Scope Sheet
When an external detector result is used, record its scope so a later re-test is comparable. If a field is unknown, mark it Unknown rather than guessing:
external_test_scope:
detector_name: # e.g. Turnitin / CNKI / GPTZero
date:
detector_version: # or Unknown
included_sections: # e.g. ch1-ch5 body
excluded_sections: # e.g. references, appendices
references_included: # yes / no / Unknown
appendix_included: # yes / no / Unknown
file_format: # docx / pdf / pasted text
chapter_extraction_method: # how chapters were separated
A re-test counts as "comparable" only when detector_name, detector_version, and the included/excluded scope match the baseline. Otherwise treat it under Non-Comparable Detector Handling.
DOCX Output Gate
When output is a .docx (Assembly Mode or single-chapter document), in addition to Gates A–J:
Paragraph and heading styles are preserved; heading levels are unchanged.
Tables, figures, equations, footnotes, endnotes, headers/footers are untouched unless the user asked for them to be revised.
Reference list and in-text citation fields are locked (no reordering, reformatting, or renumbering).
Track-changes / comments handling is stated explicitly (kept, accepted, removed, or unsupported by the current output method) — never silently altered.
Format-preservation fallback: if the output method cannot safely preserve track changes, comments, citation fields, tables, footnotes, headers/footers, equations, or complex styles, do NOT mark the .docx as final. Default to delivering a text-only revised chapter for manual insertion. Produce a candidate .docx labelled format-not-verified only when the user explicitly requests a file despite the limitation — never a locked final version. In both cases attach the DOCX limitation note and keep the rewritten scope limited to the approved chapter or batch.
Default-Excluded Units above remain unchanged in the output file.
The rewrite covers only the current approved chapter/batch; a whole-thesis one-pass rewrite is not produced (see Task Routing — Assembly Mode).
Output hygiene (the delivered file must be clean, faithfully rendered prose — these checks are about the file, not the rewriting, and never license changing content):
No unresolved draft markers or placeholders survive in the delivered thesis body, headings, captions, footnotes, comments intended for removal, or visible fields: TODO, TBD, FIXME, ??, [[, ]], empty bracketed fields, [insert], [variable], lorem ipsum, or placeholder ellipses standing in for missing content.
No leaked raw markup or control tokens render as literal text: stray Markdown table pipes, unrendered Markdown/LaTeX commands (e.g. \textbf{...}, \cite{...}, \section{...}), unresolved citation markers like [@key], or a broken cross-reference shown as [?]. The visible text must read as finished prose.
Chinese encoding integrity: export as UTF-8 and confirm Chinese characters render correctly, with no mojibake or garbled byte runs (the classic failure is GBK text decoded as UTF-8). For a bilingual or Chinese thesis this check is mandatory before the file is treated as final.
File Naming Convention
When producing versioned files across rounds, name them so baselines, candidates, and locked re-tests are unambiguous:
<Unit>_v<NN>_baseline_<score-or-Unknown>_<scope>.docx e.g. Chapter3_v03_baseline_36pct_CNKI.docx or Chapter3_v03_baseline_Unknown_internal.docx (add detector/scope when external scores are used)
<Unit>_v<NN>_candidate_rung<N>.docx e.g. Chapter3_v04_candidate_rung2.docx
<Unit>_v<NN>_retest_<score>_locked_<detector-or-scope>.docx e.g. Chapter3_v04_retest_28pct_locked_CNKI.docx
The "_locked" suffix marks a version confirmed below target by a comparable external re-test within the NAMED detector stream and scope (status Done). A version locked under one detector stream is not automatically locked under another stream. Use "Unknown" in place of a score when no comparable external score exists yet.
External Highlight First Rule
When an external detector report is provided, the externally highlighted or high-risk sections must be reviewed before internal paragraph rewriting.
Workflow:
Extract high-risk sections from external detector reports.
Convert detector-specific findings into shared AI-risk categories.
Build the External Risk Convergence Map.
Select P0 and P1 sections.
Rewrite P0/P1 sections in batches.
Run internal D1–D17 scoring to explain and guide the rewrite, not to override external evidence.
If an external detector highlights or reports a long high-risk section, treat it as high-risk even if paragraph_risk_index is low.
The rewrite unit should be sentence, paragraph, paragraph group, subsection, or chapter segment depending on the risk pattern.
External Score Extraction Rule
When the user provides an external detector result in any informal format, extract and standardize the detector name and score before Phase 1.
Detector names are recorded for source tracking only. They must not create detector-specific rewrite strategies.
Detector-specific prioritisation vs detector-agnostic technique (general rule): it is allowed to use which detector reported the risk, and known detector tendencies (e.g. CNKI weighting the document opening, the small-sample observation that Chinese MBA conclusion chapters run higher), to decide WHERE to look first and WHAT to rewrite first. It is NOT allowed to change HOW a passage is rewritten based on the detector — the rewrite techniques (minimal edit, de-templating, term protection, no fabrication) are identical regardless of which detector is in play. Prioritisation may be detector-informed; technique stays detector-agnostic.
Accepted formats include:
“Turnitin says 48%”
“Turnitin AI = 48%”
“AI rate 0.48”
“知网AIGC 49.9%”
“CNKI AI feature value 49.9%”
uploaded detector PDF report
Standardize as:
external_detector:
external_score:
external_score_type:
report_available: Yes / No
Examples:
external_detector: Turnitin
external_score: 67%
external_score_type: AI Writing
report_available: Yes
external_detector: CNKI
external_score: 49.9%
external_score_type: AIGC AI feature value
report_available: Yes
Mandatory rule:
External detector scores must be extracted before internal scoring.
Informal user-provided detector scores must not be ignored.
External scores must be used in Score Regression Guard and Universal External-Risk Calibration Rule.
Comparable external re-test rule (required for any score comparison)
A "comparable external re-test" is a re-test run with the SAME detector, the SAME tested scope, the SAME inclusion/exclusion settings, and a materially comparable document version.
A regression/improvement judgment (red line, lowest-ever, "did it go down?") may ONLY be made against a comparable external re-test.
Scores from DIFFERENT detectors (e.g. Turnitin 48% vs CNKI 32%) are separate evidence streams. Report them side by side; never treat one as a rise or fall relative to the other.
Scope consistency: a chapter-level score may only be compared with a later chapter-level score from the same chapter scope; a whole-document score only with a later whole-document score under comparable settings. A chapter-only score is never evidence that the whole thesis improved.
If the detector cannot re-test a single chapter, fix one substitute scope before round 1 and keep it unchanged: either re-test the whole document after each accepted chapter revision, or re-test an identically extracted chapter file with unchanged formatting/inclusion settings.
The 70%-of-external calibration floor applies ONLY when diagnosing the same pre-rewrite version that produced that external score. For a revised candidate, report an internal risk estimate only and state that external improvement is unverified until a comparable re-test is run.
Scope-labelling rule (do not inflate a chapter score into a document score)
If all body paragraphs of the document are included, you may report overall_document_internal_risk_estimate.
If only a chapter, batch, or highlighted fragment is included, report target_unit_internal_risk_estimate and do NOT label it a document-level score.
Phase 8/9 must state Scope = Full document / Target chapter / Selected batch / Highlighted fragment. Only Scope = Full document may produce a document-level estimate.
No External Detector Score Rule
If no external detector score is available:
Do not create an exact external chapter-red-line ledger. An Internal Planning Ledger with scores marked Unknown / internal risk estimate only MAY be created, but it must never be treated as an external baseline or as proof of detector improvement.
Do not claim that the rewrite has lowered the external detector score.
Use internal D1–D17 scoring only as a risk-location estimate.
Mark all scores as “internal risk estimate only.”
Recommend external re-testing after rewriting.
Verbally-stated score, no report: if the user only mentions a number (e.g. "Turnitin says 48%") but uploads no actual detector report, treat that number as a calibration signal only (it may inform the 70% calibration floor and overall prioritisation). It does NOT establish any "externally highlighted section" — without a real report there are no highlighted ranges to apply External Highlight First to, so do not claim or invent highlighted sections, do not add External Risk Convergence Map entries based on invented ranges, and select targets by internal risk instead. It may trigger stricter internal prioritisation and an Internal Planning Ledger only. If the user later uploads the detector report, rebuild the External Risk Convergence Map from the report before rewriting.
No External-Result Claim Rule: if no comparable external re-test result is available for the revised version, never write "AI score reduced", "AI rate lowered", "detector score improved", "will pass Turnitin/CNKI", or similar. Use only "internal risk estimate reduced", "risk patterns addressed", or "candidate version prepared for external re-test".
If the user later provides an external detector score, rebuild the Chapter Version Ledger from that score before the next rewrite round.
Task Size Routing Rule
Before execution, decide whether the task should use Quick Mode, Single-Batch Mode, or Full Staged Mode.
Task Type
Criteria
Execution Mode
Quick Mode
User asks for (or single-paragraph input implies) a quick single-paragraph rewrite/check; no thesis chapter/full thesis/DOCX/PDF/report uploaded (an optional author-style sample, the single source paragraph, or one short paragraph-level detector excerpt does NOT disqualify); no external detector score/report; target text ≤1 paragraph
Simplified single-paragraph workflow
Single-Batch Mode
Selected rewrite paragraphs ≤10 and no full-document rewrite is requested
Diagnosis + rewrite + quality gate may be completed in one response for those ≤10 paragraphs, all evidence must still be shown, and it must NOT be described as a whole-thesis rewrite. If more than 10 paragraphs are provided, route to Full Staged Mode even if the first response processes only one batch
Full Staged Mode
Long document, DOCX/PDF, external detector report, more than 10 paragraphs, or external-detector-high task, including any external AI detector report with high-risk sections, highlighted fragments, or high overall AI-risk scores
Mandatory staged execution
Mandatory rule:
If more than 10 paragraphs are involved, use Full Staged Mode.
If an external detector report is provided, use Full Staged Mode unless the user explicitly asks to inspect only one paragraph.
Single-Batch Mode does not remove evidence requirements. Phase 4.5, Phase 5.5, and Phase 7 evidence must still be visible.
If no external detector score is available, do not create an exact chapter red-line ledger. Use internal D1–D17 scoring only as a risk-location estimate. Mark all scores as "internal risk estimate only." Recommend external re-testing, but do not claim that the rewrite has lowered the detector score.
Definition of included body paragraphs:
In Full Staged Mode, included body paragraphs are the paragraphs inside the current target chapter, selected external-highlighted section, or selected rewrite batch. Low-risk paragraphs outside the current batch may be recorded by section-level summary and do not require full visible D1–D17 evidence in that round.
Practical Long-Document Execution Rule
For documents with more than 80 body paragraphs, staged, batch-based execution is mandatory; do not attempt full-document paragraph-by-paragraph diagnosis or rewriting in one response. (For more than 50 body paragraphs, staged or batch output is recommended and compact skip records may be used for low-risk or non-target paragraphs.)
Stage 1 may use a full-document structural scan plus full D1-D17 scoring for the following priority units:
externally highlighted paragraphs or fragments;
the first 20% of the thesis;
methodology, empirical results, discussion, and conclusion sections with template-like reporting patterns;
repeated paragraph clusters detected across literature review, hypothesis development, methodology, or empirical reporting sections.
Low-risk paragraphs may be recorded through a section-level summary when they are not externally highlighted and do not belong to a repeated structure cluster.
However, any paragraph selected for rewriting must still receive:
full D1-D17 scoring;
paragraph_risk_index calculation;
priority classification;
selected rewrite techniques;
protected elements check;
paragraph-specific rewrite evidence;
Phase 7 quality-gate result.
This rule does not weaken the D1-D17 requirement for rewritten paragraphs. It only prevents impractical full-document evidence output for low-risk paragraphs in long thesis projects.
Batch Processing Rule
For long documents, process rewritten paragraphs in manageable batches.
Recommended batch size:
3–5 fragment clusters for externally highlighted severe-risk sections;
5–10 paragraphs for severe-risk sections;
10–15 paragraphs for standard high-risk sections.
Batch processing is allowed only after the task has been routed by the Task Size Routing Rule.
Do not claim full completion until all selected A/B priority paragraphs have been processed.
If the task is too large for one response, output:
