Douyin Copy Production Workflow Custom

Douyin Copy Production Workflow

Use this skill for the user's complete production loop from assistant-collected scripts to publishable long-form Word drafts.

4.0独立模式（优先路由）

用户指定 4.0、4.0批量换芯扩写 或 先批量换芯再用旧2.5 时，先读 references/4.0-frozen-legacy-session.md，按它执行完整流程。4.0采用3.5内容设计与知识支持，再以固定旧2.5提示词扩写；每篇从同一份固定旧2.5备份复制独立会话，只放入一篇换芯稿，生成后的会话永不传给下一篇。 用 scripts/prepare_40_session.py 校验并准备。4.0专属规则覆盖下文通用包装、强制案例、固定结尾和改写验收；不继承3.5生成/验收锁，不修改其他版本默认值。

3.6安全换新扩写

用户指定 3.6、3.6安全版、安全换新扩写 或 先按3.5换新再用2.8扩写 时，读 references/3.6-safe-transplant.md。3.6只继承3.5的换新设计与查重隔离机制，不继承3.5的旧2.5强硬扩写提示词、专用Gary声音会话、自然节奏锁或热门开头替换。冻结换新稿后，必须用 scripts/build_36_gemini_prompt.py 组装完整2.8安全版提示词与3.6母题/数量锁，并通过专用 --session 3.6 扩写。不得把3.6静默替代普通3.5或普通2.8。

Core Outcome

Produce final .docx files that contain:

1. 爆款心理学标题包装
2. 开头版本一：高阶认知课式开头
3. 开头版本二：身份点名式硬核学习开头
4. 开头版本三：保留原文开头（来自源文档）
5. 正文

This is the general/default package. For 3.5, the user's current rule overrides it: the Word contains only 热门开头匹配 and 正文. Do not include a title package, visible title page, multiple opening versions, the verbatim source opening, or an optimized-source-opening section in a 3.5 Word.

Do not add risk suggestions or [[RISKNOTE:...]] markers. For 3.1, preserve every Gemini-returned content unit, claim, example, CTA, and its original order. Do not delete its Doubao/AI-summary guidance, engagement prompts, fan-group conversion, account language, examples, or hard-edged judgments. During acceptance, remove only redundant empty intensifying adverbs when deleting them leaves the claim, force, cadence, syntax, and argument unchanged; record each deletion as an exact narrow diction repair. The only mandatory content replacement is the terminal ending, which must be normalized to 我是探花Gary，我们粉丝群里见，感谢观看。 Source/Gemini body text remains unhighlighted; by default highlight only the normalized fixed ending in yellow.

Gary 3.5情感账号归属锁

Gary的成长/心理线仍属于情感账号。隐藏标题后，核心论证必须依赖女人、吸引、男女互动或关系位置；拿掉情感关系仍成立的泛男性成长、事业或自律路线直接判定跑题。事业、金钱、自律只能解释它们如何改变吸引判断或男女关系中的选择与位置，不能成为独立中心。仅插入女人字眼或一个约会案例不能补救。 在三候选路线选择前和扩写后各审一次，记录语义证据，不用关键词数量代替判断。《一个男人真正翻身之前，必须经历的十八次现实改造》的旧测试已被用户否定，不可作为合格语感或路线样本。

Default Paths

• Assistant source folders are often under /Users/kin/工作用（同步）/素材文稿/助理采集文案/ on Mac or D:\工作用（同步）\素材文稿\助理采集文案\ on Windows; old E:\工作用\素材文稿\助理采集文案\ is legacy-only.
• Male manuscript root for the current Mac workflow: /Users/kin/工作用（同步）/探花Gary
• New production Word drafts pending user confirmation: /Users/kin/工作用（同步）/探花Gary/01_正文待确认/<版本>/<批次>
• New test/comparison Word drafts: /Users/kin/工作用（同步）/探花Gary/02_测试稿/<版本>/<批次>
• User-confirmed final Word drafts: /Users/kin/工作用（同步）/探花Gary/07_成品/<版本>/<批次>
• Intermediate run packages may use /Users/kin/工作用（同步）/探花Gary/06_以后新输出/<版本>/<批次>, but user-facing Word drafts must still be filed by status above.
• Windows uses the synchronized mirror under D:\工作用（同步）\探花Gary\...; Mac remains the primary workflow state.
• Legacy Windows final Word output folder: E:\工作用\素材文稿\codex工作流长文稿
• Expansion tests/comparison runs must be exported as .docx files into the corresponding folder under the male manuscript root; do not deliver .txt unless the user explicitly asks for txt.
• Gemini execution choice: default to the Mac local runner unless the user explicitly asks to use Windows or the task depends on Windows-only files, old Windows Codex projects, or Windows-only tooling.
• Current Mac Gemini expansion command directory: active Codex workspace when it contains scripts/run_gemini_chat.sh; current tested workspace is /Users/kin/Documents/Codex/2026-07-02/gemini.
• Current Mac Gemini expansion command: ./scripts/run_gemini_chat.sh --prompt-file <prompt.txt> --output-file <expanded.txt>. For routine 2.5 and 3.2, use the current 2026-06-05 early B direct-draft block from references/gemini-expansion.md; for 3.1, use that complete block plus the fixed mother-topic exact-lock block built by scripts/build_31_gemini_prompt.py; for 3.5, use that complete block plus the fixed exact-topic and natural-rhythm locks built automatically by scripts/build_35_gemini_prompt.py, and always supply the validated old_25_engine_plan.json through --engine-plan; for 3.6, use the complete 2.8 Safe Draft block plus the fixed 3.6 mother-topic/content-line/selected-count lock built by scripts/build_36_gemini_prompt.py, also supplying the validated old_25_engine_plan.json; for 3.3, use the complete 2.5 block plus the separate 3.3 exact-lock block built by scripts/build_33_gemini_prompt.py. Add --isolated for routine 2.5, 3.1, 3.2, and 3.3. Formal 3.5 uses its staged dedicated Gary voice candidate. Formal 3.6 uses --session 3.6, never the 3.5 voice session, the generic 2.8 saved session, or the mixed default session. Use --session 2.5 only when the user explicitly asks to continue that saved conversation. Keep 2.5-transplant, 2.8, 2.9, and 3.6 in separate dedicated sessions unless their rules call for isolation.
• TeamRouter network gate: before the first manuscript request in a task, run ./scripts/run_gemini_chat.sh --print-config --isolated and verify that TEAMO_CHAT_COMPLETIONS_URL is exactly under https://api.teamorouter.com/v1/. In restricted Codex sandboxes, run the actual manuscript request with the approved escalated network permission and the reusable prefix ./scripts/run_gemini_chat.sh; a plain sandbox request can fail DNS with Errno 8 even while TeamRouter, the API key, and the model are healthy. If this happens, rerun the identical isolated request with authorized network access. Do not change the prompt, model, or source merely because the sandbox transport was blocked. Never send the manuscript if the printed endpoint is a different host.
• Current formal 2.9 active prompt for the Gary project: /Users/kin/Documents/Codex/2026-07-10/qu/work/ACTIVE_2.9_PROMPT_强结论正式版.txt. The earlier stable rollback baseline remains /Users/kin/Documents/Codex/2026-07-10/qu/work/ACTIVE_2.9_PROMPT_昨晚12个男性成长版.txt; do not delete or silently overwrite it.
• Windows fallback Gemini expansion command directory: C:\Users\Administrator\Documents\Codex\2026-06-04\gemini3-1pro-api.
• Windows fallback Gemini expansion command: .\outputs\run_gemini_chat.cmd --prompt-file C:\path\to\prompt.txt --isolated.
• Other-copy Gemini isolation rule: for non-male-relationship copy or unrelated tests, use --prompt-file <prompt> --isolated on the selected host so saved male relationship expansion conversation state is preserved; do not use /new for this.
• Opening source of truth: invoke baokuan-kaitou-sheding / $爆款开头设定; do not hand-write openings from memory.
• When a Gary manuscript comes from huanxin, select and freeze the one formal opening immediately after the transplant body is frozen. Show it above the transplant preview, store it separately as opening_lock.txt and opening_lock.json, and keep it out of the Gemini input. After expansion, verify only that the locked topic, count, mechanism, and result still match; when they match, insert the exact locked opening before the first 另外说一下. Do not create a second opening during acceptance. For a source that did not pass through huanxin, retain the normal post-expansion opening-selection fallback.

Reference Files

Load only the reference files needed for the current step:

• references/mother-topic-exact-lock.md: read for every male Gary rewrite, expansion, 2.5成稿换芯, 3.1, 3.2, 3.3, fixed-topic cycle, or knowledge-base-assisted rewrite. The source body's public mother topic is an exact lock; only content underneath it may change. Knowledge-pack titles and abstract summaries never rename the public topic.
• references/transplant-mechanism-novelty-gate.md: read for every Gary transplant mode. Apply its six-field causal-route comparison plus the shared title-hidden, direct-answer, no-new-umbrella, causal-mapping, and expansion-capacity gates before freezing; repeat the mother-topic-native audit after Gemini. In 3.5, scope mechanism exclusion to the complete same-mother-topic lineage across all statuses, allow rebuilt cross-topic mechanism reuse, and keep the separate whole-library final-text similarity gate. Write the current route back immediately so the next version of that mother topic cannot reuse it. In Codex-designed 3.3/3.5, create three local candidate routes before selection; do not call Gemini for the alternatives. This is a Codex selection gate and must never be appended to or replace the complete 2.5 Gemini prompt.
• references/gemini-expansion.md: read before sending source text to Gemini, creating prompt files, retrying failures, or checking generated drafts.
• references/3.1-knowledge-base-transplant.md: read in full for every 3.1, 3.1换芯, 2.5预换芯, or 原稿预换芯 task. This is the canonical default: Codex selects, excludes, polishes, and transplants only traceable B/X knowledge without inventing content; Gemini then freely expands the frozen source through the complete standard 2.5 prompt with --isolated and no knowledge-closure supplement. Its Word export uses the 3.1-specific four-opening package: two generated openings, the verbatim source opening, and a separate source-opening optimized version aligned to the accepted body.
• references/3.5-codex-first-knowledge-supported.md: read in full when the user asks for 3.5, 3.5混合换芯, Codex先设计知识库辅助, 知识库只补充弹药, or explicitly approves the September 3 hybrid test logic. First classify the internal content line as short_term or growth_psychology: short-term intent is expressed through immediate behavior and scenes without repeated category labels; growth/psychology covers male growth, female psychology, human nature, frame, career, and choice power rather than defaulting to couple maintenance. For an unspecific sequence, alternate the two lines and separate adjacent mechanisms and scenes. Codex then creates three topic-native local route candidates, selects the strongest passing article-level causal spine and same-level point hierarchy, and records the discarded same-lineage routes; the knowledge base supports mechanisms, evidence, phrasing, and compact student/composite cases without determining the public skeleton. The frozen transplant source is a lean route skeleton, not a near-finished manuscript: keep only the article thesis, point boundaries, causal bridges, essential scene constraints, and case placement, and leave prose, transitions, examples, case details, and rhetorical development to expansion. Its adaptive lean limit does not lower final-body length: final 3.5 text has a hard 3000-CJK minimum and a preferred 3000-3800 range, while naturally longer complete drafts may be retained. Do not pad a structurally complete draft merely to approach 4000. Acceptance-fixable defects do not go back to Gemini: locally normalize the transition/ending, add names or one compact background sentence to an already complete case, and remove backstage labels or redundant 极其. Rerun only for a body below 3000 CJK, missing promised points or acts, truncation, topic/mechanism drift, absent case causality, or any repair that would redesign the article. Gemini may add familiar foundational concepts as secondary explanation. If a case is included, both the male student/brother and the woman must have names; the case must show Gary's guidance, coaching, or consultation before a concrete successful result. Place the exact transition sentence 我给兄弟看一个咨询案例。 immediately before the case and highlight only that sentence in yellow in the Word package. Exclude mechanisms across earlier versions of the same mother topic, allow rebuilt reuse under unrelated topics, and still run conservative whole-library final-text duplication review. Gemini expands the frozen source through the old 2.5 surface after the builder normalizes its conflicting length wording, plus the builder-owned 3.5-natural-rhythm-lock.txt, against the staged dedicated Gary voice candidate session; never use --isolated, --new-session, or the mixed default session for formal 3.5, and never append a second hand-written naturalness layer. During acceptance, remove redundant uses of 极其 when deletion leaves the meaning, cadence, and syntax intact; record this as a permitted narrow diction repair rather than a semantic rewrite. A case must convey Gary intervention -> adjusted action -> observable result through the story itself; reject explicit QA-style attribution such as 这就是Gary咨询后调整带来的明确结果.
• references/3.6-safe-transplant.md: read in full for 3.6, 3.6安全版, 安全换新扩写, or 3.5换新后送2.8. It reuses the complete 3.5 pre-expansion design, same-topic lineage exclusion, three-candidate route selection, adjustable count, old-2.5 structure-engine plan, knowledge support, lean frozen source, and final whole-document similarity audit. Its expansion surface is the complete 2.8 Safe Draft block, assembled only by scripts/build_36_gemini_prompt.py and run in the dedicated 3.6 session. It must remain distinct from both 3.5 and ordinary 2.8.
• references/3.5-codex-first-knowledge-supported.md: read in full when the user asks for 3.5, 3.5混合换芯, Codex先设计知识库辅助, 知识库只补充弹药, or explicitly approves the September 3 hybrid test logic. First classify the internal content line as short_term or growth_psychology: short-term intent is expressed through immediate behavior and scenes without repeated category labels; growth/psychology covers male growth, female psychology, human nature, frame, career, and choice power rather than defaulting to couple maintenance. For an unspecific sequence, alternate the two lines and separate adjacent mechanisms and scenes. Codex then creates three topic-native local route candidates, selects the strongest passing article-level causal spine and same-level point hierarchy, and records the discarded same-lineage routes. Before knowledge retrieval, translate the winner through references/3.5-old-2.5-structure-engine.md: create one topic-native master memory spine, two to four causal acts when the count is at least four, one governing judgment per point, rotated proof carriers, act-level escalation, and one identity or position shift. Save this as old_25_engine_plan.json; the builder must validate it through --engine-plan. This inherits old-2.5 structure without copying repeated openings, CTA boilerplate, unsupported authority, or merely adding harsher adjectives. The knowledge base supports mechanisms, evidence, phrasing, and compact student/composite cases without determining the public skeleton. The frozen transplant source is a lean route skeleton, not a near-finished manuscript: keep only the article thesis, point judgments and boundaries, causal-act transitions, master-spine anchor, essential scene constraints, and case placement, and leave prose, most examples, case details, and rhetorical development to expansion. Its adaptive lean limit does not lower final-body length: final 3.5 text has a hard 3000-CJK minimum and a preferred 3000-3800 range, while naturally longer complete drafts may be retained. Do not pad a structurally complete draft merely to approach 4000. Acceptance-fixable defects do not go back to Gemini: locally normalize the transition/ending, add names or one compact background sentence to an already complete case, and remove backstage labels or redundant 极其. Rerun only for a body below 3000 CJK, missing promised points or acts, truncation, topic/mechanism drift, absent case causality, or any repair that would redesign the article. Gemini may add familiar foundational concepts as secondary explanation. If a case is included, both the male student/brother and the woman must have names; the case must show Gary's guidance, coaching, or consultation before a concrete successful result. Place the exact transition sentence 我给兄弟看一个咨询案例。 immediately before the case and highlight only that sentence in yellow in the Word package. Exclude mechanisms across earlier versions of the same mother topic, allow rebuilt reuse under unrelated topics, and still run conservative whole-library final-text duplication review. Gemini expands the frozen source through the old 2.5 surface after the builder normalizes its conflicting length wording, plus the builder-owned 3.5-natural-rhythm-lock.txt, against the staged dedicated Gary voice candidate session; never use --isolated, --new-session, or the mixed default session for formal 3.5, and never append a second hand-written naturalness layer. During acceptance, remove redundant uses of 极其 when deletion leaves the meaning, cadence, and syntax intact; record this as a permitted narrow diction repair rather than a semantic rewrite. A case must convey Gary intervention -> adjusted action -> observable result through the story itself; reject explicit QA-style attribution such as 这就是Gary咨询后调整带来的明确结果.
• references/3.5-gary-voice-session.md: read before every formal 3.5 Gemini call. Stage the stable early-B-seeded Gary session into the current work package, run against the candidate with --session-file, restore the pre-attempt snapshot after a rejected response, and promote the candidate only after the user explicitly approves its writing quality. The saved session controls voice only; the builder and frozen source remain authoritative for topic, count, route, cases, and content line.
• references/3.5-user-popular-opening-library.json and references/3.5-user-popular-opening-library.md: read after every 3.5 body passes and before Word export. The JSON contains the user's 16 deduplicated popular openings, duplicate map, family labels, fit tags, and scoring weights; the Markdown contains the eight opening families and exact matching/Word-insertion rules. Match directly when possible and otherwise adapt the nearest family. The matched opening replaces only Gemini text before the first 另外说一下; preserve 另外说一下 and everything after it.
• references/3.5-experience-anchor-library.md: read during 3.5 frozen-source design when using Gary experience anchors. Approved wording is exact and optional; select and fill only a topic-matched anchor inside the frozen source, and never append the whole library or its IDs to the Gemini request.
• references/3.3-codex-designed-pretransplant.md: read in full for every 3.3, 3.3独立换芯, 旧版3.1, or 让Codex设计新观点 task. This is the former pre-knowledge-base 3.1 workflow under a new formal version number. It uses no knowledge base: Codex independently rebuilds the short source and topic-native conversion route, then Gemini expands it through the complete old 2.5 prompt in an isolated run. Keep its prompt, ledger, validation, Word package, and status separate from 3.1 and 3.2.
• references/knowledge-lifecycle-feedback.md: read after any Gary knowledge-base-assisted draft and whenever publication data or opening performance must feed later retrieval. It binds knowledge, route, opening, account, lifecycle state, and data snapshots through one stable work ID.
• references/3.1-cta-layer.md: read after every 3.1 Gemini body is accepted and before Word export. It is the Gemini full-retention and terminal-ending-normalization rule: preserve every Gemini content unit in its original order, add no Codex CTA, remove only contextually empty tracked intensifiers as exact recorded narrow diction repairs, and normalize the terminal ending to 我是探花Gary，我们粉丝群里见，感谢观看。; narrow grammar/TTS repairs are also allowed only when recorded exactly.
• references/2.5-finished-draft-transplant.md: read when the user asks for 2.5成稿换芯, provides an already-expanded approved 2.5 draft as the style parent, or asks to preserve the mother topic while replacing its internal arguments and examples.
• references/3.2-conversion-transplant.md: read when the user asks for 3.2, 3.2换芯, or 3.2换芯扩写. This mode keeps its own controlled-inheritance rules and does not automatically inherit 3.1's new Codex closed-set knowledge restriction unless the user explicitly asks to merge them. It preserves 60%-80% of the source's content functions, overlays the approved monetization sequence, and places compact Gary student-case proof after selected theory explanations. It uses one ending fan-group CTA, then runs the frozen source through the same complete 2.5 prompt with --isolated.
• references/gemini-expansion.md: also read when the user asks for 3.1, 2.5预换芯, 原稿预换芯, or wants to first rebuild the short source manuscript while keeping the exact public topic, then run routine 2.5 expansion.
• references/2.9-strong-conclusion-layer.md: approved formal 2.9 enhancement source of truth for strong conclusions, human-nature games, interest judgments, dark insight retention, and the three-topic validation record. Its prompt text is also embedded inside the formal 2.9 block in references/gemini-expansion.md so routine prompt builders cannot omit it.
• references/source-learning-and-style.md: read when processing a batch, learning source viral logic, classifying source styles, or preserving source openings.
• references/openings-and-titles.md: read after expansion passes checks and before Word export to generate openings, score them, and build title packages.
• references/export-and-hard-rules.md: read before optional scoring, Word export, final delivery, and post-run workflow updates.
• references/3.0-qianchuan-tts.md: read when the user asks for 3.0千川素材、保头压中自然转化、热门原稿植入CTA、1500字内成稿、自然过桥或直接TTS Word交付。

Workflow

1. Queue Every Provided Source By Default

When the user provides a batch of .docx scripts, do not run pre-expansion scoring, ranking, filtering, or top-N selection unless explicitly asked. Preserve stable filename order unless the user gives another order.

Read references/source-learning-and-style.md and create a concise batch learning note in the current workspace outputs folder.

2. Expand With Local Gemini

Read references/gemini-expansion.md.

Before selecting a route or knowledge, read references/mother-topic-exact-lock.md, copy one exact public mother-topic anchor from the source body, and record it. The frozen source, expanded body, Word title, and filename must continue to use that source-derived mother topic. Never replace it with a knowledge-pack title, card summary, course label, safer abstraction, or newly invented umbrella concept. Only the content beneath the locked mother topic may be replaced.

Use the Mac local Gemini runner by default:

cd /Users/kin/Documents/Codex/2026-07-02/gemini
./scripts/run_gemini_chat.sh --prompt-file work/prompt.txt --isolated --output-file work/expanded.txt

Use Windows only when the user explicitly asks for Windows or the task depends on Windows-only files, old Windows projects, or Windows-only tooling:

cd C:\Users\Administrator\Documents\Codex\2026-06-04\gemini3-1pro-api
.\outputs\run_gemini_chat.cmd --prompt-file C:\path\to\prompt.txt --isolated

Build each UTF-8 prompt file with the selected full Gemini instruction block from references/gemini-expansion.md, followed by any required direction-specific injection and the original source text wrapped as 【原文开始】...【原文结束】. For routine 2.5, the official baseline is the complete 2026-06-05 early B direct-draft block + source, with each source run using --isolated. Do not append the old 旧2.5风格参照 injection in routine 2.5 runs unless the user explicitly asks for a separate style-calibration test. If the user asks for 单案例、一案到底、一个案例贯穿全文, use the 2.6 Single Case direction.

If the user asks for 2.5成稿换芯, 用扩写好的2.5改内容, 保留母题替换内容, or says to keep the method approved by the August 1 fixed-mother-topic batch, use the current canonical fixed-mother-topic limited-inheritance mode in references/2.5-finished-draft-transplant.md; do not use routine source expansion, the retired layer-only prompt, or the older full-exclusion transplant mode. For every transplant mode, infer the mother topic, audience promise, central claim, and promised count from the manuscript body only. Never use the filename, folder name, Word title/core properties, document heading, stale metadata, or an earlier output title to choose the route or invent a structure; those fields are for file identification only. If any of them conflict with the body, the body wins. Prompt assembly must begin with the complete 2026-06-05 early B 2.5 instruction block from references/gemini-expansion.md; append the transplant/strong-attack task layer, an unused article-specific route, a limited-inheritance card, cumulative route exclusions, and the approved 2.5 finished draft. Never use the transplant layer by itself. Retain one central source mechanism and at most two short signature sentences (about 20%-30% of the content role), rebuild the remaining 70%-80% with new scenes, interest changes, consequences, and proof, and run every article through the dedicated copied old conversation with --session-file work/gemini_session_25_transplant_legacy.json or the local --session 2.5-transplant shortcut. For batches larger than three, work in groups of three and update the cumulative route, similarity, and retry ledgers after each accepted group.

For every Gary transplant mode, apply this case rule whenever the manuscript includes a student/brother case: give the male and the woman names; begin the case with one natural background sentence that says when the man came to Gary, what stage he and the woman had reached, and at least one relevant personal detail such as occupation, city, age band, or how they met; show Gary's guidance, coaching, or consultation as the causal turning point; and end with a concrete successful result. Before freezing, compare the case with recent case records and change at least three substantive dimensions when the skeleton collides: relationship stage, scene, original failure, Gary intervention, student's action, woman's observable response, result shape, or narrative order. Changing only names, objects, or dialogue does not count. A case missing either name, the background sentence, the Gary intervention, the result, or the diversity check is incomplete and must be rebuilt before expansion. Insert the exact transition sentence 我给兄弟看一个咨询案例。 immediately before the case and highlight only that transition sentence in yellow in the Word package; do not add a second disclosure label or another production-status sentence around the case.

For every Gary 3.5 frozen transplant source, use a light route skeleton rather than a short finished manuscript. For ordinary counts, target about 500-1000 Chinese characters; fifteen- or twenty-point inventories may use the builder's larger adaptive allowance, but every source must remain below 1600. Preserve the locked thesis, promised count, concise point boundaries, short causal-act anchors, the identity shift, and case placement. Only two or three selected points may carry an essential proof direction; leave the other points' scenes, mechanisms, examples, transitions, rhetorical development, and case elaboration to Gemini. Do not pre-write one complete explanation for every point.

For every Gary transplant mode, keep editorial instructions, rejected examples, QA vocabulary, backstage explanations, and outline labels such as 总判断：, 收束：, 开头逻辑：, 核心总结：, 写作说明：, or 段落任务： out of the frozen source and public body. State the judgment or conclusion as natural narration without announcing its structural role. A sentence that comments on whether a result is empty, explains why the author avoided another wording, or exposes a validation rule must be rejected rather than polished into place. The exact 此处植入案例。 marker is allowed only inside a frozen source when the case is delegated to Gemini; Gemini must replace it with 我给兄弟看一个咨询案例。 and the complete case, so the marker may never appear in public copy.

For every Gary transplant mode, apply references/transplant-mechanism-novelty-gate.md before the rebuilt source is frozen. A different title, term set, example, point order, or knowledge-ID combination does not count as a new route when the dominant causal machinery repeats. Register each generated / 正文待确认 route before selecting the next article; do not wait for user acceptance or publication.

If the user asks for 3.5, 3.5混合换芯, Codex先设计知识库辅助, 知识库只补充弹药, or the fixed September 3 hybrid logic, follow references/3.5-codex-first-knowledge-supported.md, references/3.5-old-2.5-structure-engine.md, and references/3.5-gary-voice-session.md. Keep this mode separate from default 3.1. Before route design, classify the private content line as short_term or growth_psychology; never expose the line label as public copy. A short-term manuscript uses immediate time, setting, distance, choice, and observable feedback instead of repeatedly saying 短期关系. A growth/psychology manuscript centers male growth, female psychology, human nature, frame, career, or choice power and must not automatically become a cohabitation, conflict-repair, responsibility, or future-planning article. For an unspecific batch, alternate the two lines from the last registered line and keep adjacent mechanisms, scenes, evidence operations, and conclusions distinct. Codex may independently design the article-level thesis, causal spine, point hierarchy, transitions, and final public point count; the source count is only a reference and may be reduced or increased when the new structure is stronger. Before design, compare the proposed public points and dominant causal route against the source body and every earlier route in the same mother-topic lineage, regardless of status or production stage. Do not globally ban a mechanism because another mother topic used it; cross-topic reuse is allowed only after the entry angle, scenes, proof, causal order, and wording are rebuilt. Preserve the locked public mother topic, audience promise, result, attack direction, and force band. Newness never authorizes topic drift: every replacement point must be a direct, topic-native answer to the exact source mother topic and its promised result. After selecting the route, save old_25_engine_plan.json: one topic-native master memory spine, two to four causal acts for four or more points, one governing judgment per point, rotated proof carriers, natural escalation transitions, and one identity or position shift. The plan inherits old-2.5 structure rather than its repeated wording and must pass the builder's --engine-plan validation. Retrieved knowledge is supporting material rather than the source of public point headings. Freeze a light route skeleton rather than a polished short article: use one master-spine anchor, very short act-transition anchors, concise point judgments, the identity shift, and case placement. Give essential proof directions only to two or three emphasis points; keep point-to-point causal links in the backstage engine plan instead of spelling all of them out in public frozen prose. Do not pre-write every paragraph, example, mechanism, and conclusion before Gemini. When a new case is delegated to Gemini, put only the exact marker 此处植入案例。 at the intended location; do not pre-write names, background, scene, process, dialogue, or result in the frozen source. Gemini must replace the marker with the exact transition 我给兄弟看一个咨询案例。 and a complete case. Final acceptance still requires both names, a natural background sentence, Gary's concrete guidance, the student's changed behavior, the woman's observable response, and a bounded successful result. Highlight only the transition sentence in yellow in the Word package; do not add the retired reconstruction disclosure or another production-status line around the case. When an experience anchor is useful, read references/3.5-experience-anchor-library.md, select one approved expression during frozen-source design, and record its ID; do not send the whole library to Gemini. Build the Gemini request only with scripts/build_35_gemini_prompt.py; it combines the complete old 2.5 block, exact mother-topic lock, required content-line lock, selected-count contract, fixed natural-rhythm lock, and validated engine plan. Stage the dedicated Gary voice session into the work package and run the candidate through --session-file; do not use --isolated, --new-session, or the mixed default session for formal 3.5. Preserve the old-2.5 hard surface. Before Word export, normalize mandatory defects, delete surplus 极其 only where the sentence keeps the same meaning and cadence, and run conservative whole-document duplication checks against all discoverable historical Gary full texts. Psychology terms, concrete relationship-practice terms commonly associated with PUA, and biology or neuroscience terms may be used when they explain an actual action or causal change. Public copy must never use the label PUA or the phrase PUA里这叫; do not stack terms, and do not use biological certainty or fabricated science. Then accept on topic fidelity, same-lineage route novelty, final-document similarity, and old-2.5 structure-engine fidelity. Once the body passes the mandatory repair boundary, do not add a separate Codex semantic-polish stage. Do not append another naturalness prompt and do not silently route a plain 3.1 request into 3.5.

3.1H is the retired name of 3.5. Historical files, work IDs, and paths may retain 3.1H for traceability. If the user uses the old name in a new request, execute the 3.5 workflow and use 3.5 in all new prompts, ledgers, filenames, and delivery labels.

If the user asks for 3.2, 3.2换芯, 3.2换芯扩写, or 带小案例的预换芯, use references/3.2-conversion-transplant.md. The canonical 3.2 starts from the complete 3.1 pre-transplant knowledge workflow but keeps its own conversion and Gemini prompt rules; do not inherit 3.1's mother-topic prompt injection, raw-conversion cleanup, or yellow-highlight default unless the user explicitly asks. Before choosing the route, load both ledgers and build a cross-version exclusion pack. Preserve 60%-80% of viewpoint/mechanism functions, replace the majority of concrete operations, use theory-first compact cases, and keep the separate 3.2 monetization ledger. After freezing, follow the 3.2 reference's current Gemini and CTA instructions rather than saying “exactly like 3.1”.

For 3.2 knowledge retrieval, the standard call pack must include page-anchored external_atomic_knowledge and GCOMP-* Gary anonymized composite case candidates. A GCOMP-* result is not a ready-made case: open its card, use one continuous source scene, and complete the four proof fields before adapting it into Gary narration. If either type is adopted, keep its ID and source status in the internal ledger; an external composite may not be relabelled internally as a verified Gary student record.

For 3.1, 3.5, 3.2, and 3.3, novelty must stay inside the source's original attack direction. Do not obtain novelty by renaming a direct, provocative promise into neutral abstractions such as 关系权限逐级开放, 阶段识别, 边界管理, 关系治理, 健康沟通, or 风险识别. Preserve the source's force band, target result, conflict object, male desire, and hard-edged framing; replace the internal arguments and operations without converting 推进到暧昧/进入男女框架/让她投入/拿回主动权 into a safer educational meta-topic. If deleting the new abstract label restores the original article's sharper promise, the label is a drift defect and the rebuilt source must be rewritten before Gemini.

This lock also forbids non-neutral renaming. A provocative source topic such as 女人最想要男人的四样东西 / 四个致命需求 may not become 四种心理待遇, 四种心理营养, or another newly unified label even when the new wording remains aggressive. Preserve the public mother topic itself; knowledge retrieval may only replace the items, mechanisms, operations, cases, and proof beneath it as allowed by the selected mode.

If the user asks for 3.1, 3.1换芯, 2.5预换芯, 原稿预换芯, or 原稿先换芯再2.5, read and follow references/3.1-knowledge-base-transplant.md as the canonical default. Infer and preserve the mother topic from the body, but treat the source's numeric promise as a reference rather than a lock. Codex may choose a different final count—such as changing twelve points to ten—according to distinct traceable material, article length, rhythm, and point quality. Record both the source count and selected count; once the rebuilt source is frozen, the selected count becomes the exact contract for Gemini, openings, titles, and validation. Retrieve traceable knowledge, exclude accepted routes, and bind every replacement point to exact IDs. Codex may select, merge compatible knowledge, adapt perspective, polish, order, and write transitions, but it may not invent substantive content. Save point-level provenance and freeze a conversion-free source with codex_content_invention: false. Build the Gemini request with scripts/build_31_gemini_prompt.py: the complete standard 2.5 block remains intact, the fixed public-mother-topic exact-lock block is inserted immediately before the frozen source, and every source runs through --isolated. Do not send vault paths, knowledge IDs, provenance, exclusions, or another supplement. Preserve every Gemini-returned content unit; allow only recorded narrow grammar/TTS repairs, tracked redundant-adverb deletions that preserve meaning and force, and terminal-ending normalization. If the first retrieval set cannot support the selected count, reduce or redesign the selected count before freeze, or broaden retrieval and replace weak slots with other traceable B/X/external-atomic modules; never fill a slot from general model knowledge or silently switch modes.

For 3.1, preserve the complete old 2.5 prompt and preserve every content unit Gemini returns, including Doubao/AI-summary guidance, engagement prompts, fan-group conversion, account language, examples, hard-edged language, and repeated conversion mentions. The fixed opening guidance must end exactly with 好，我们直接进入正题。; if it is missing, duplicated, or paraphrased, rerun the unchanged isolated request rather than inserting it after generation. Save the raw output unchanged. Do not run scripts/clean_31_gemini_conversion.py or scripts/validate_31_gemini_no_cta.py in the current 3.1 workflow; they are legacy audit tools only. After topic/selected-count/force/length validation, apply references/3.1-cta-layer.md: add no Codex CTA and delete no Gemini content unit. The sole mandatory content replacement is the terminal ending, normalized to exactly 我是探花Gary，我们粉丝群里见，感谢观看。 Narrow grammar, punctuation, obvious broken-word, TTS, and redundant-adverb repairs are allowed only when they preserve every content claim and are recorded as exact before/after pairs. For redundant-adverb repairs, delete only high-confidence empty intensifiers whose removal leaves the same judgment, force, cadence, syntax, and causal meaning; do not replace force with mild wording or rewrite the sentence. Before Word export, the unified validator must pass the built-in redundant-adverb density gate. In the default 3.1 Word, highlight only the normalized fixed ending in yellow; do not highlight source/Gemini text.

After final provenance and the actual opening choice are known, read references/knowledge-lifecycle-feedback.md and register the draft under one stable work ID. Record only knowledge and openings actually adopted. When publication data later becomes available, append snapshots under the same ID; never infer confirmation, publication, or data review from file existence.

For 3.1, route diversity must come from selecting different traceable knowledge modules, not from Codex inventing a new thesis, and it must never be purchased by lowering the force band. Every selected replacement point must preserve a memorable Gary judgment and show at least one concrete interest shift, relationship-position change, subconscious revaluation, selection con

…(truncated)