Eva Create

Default Reading

references/create/00_eva-create_创作主入口.md

references/create/article/00_eva-article_文章主入口.md
references/create/article/01_eva-article-argument_观点与论证路线.md
references/create/article/02_eva-article-writing_文章撰写与长度调节.md
../eva-shared/references/audience/00_eva-audience-finder_话题人群识别器.md
../eva-shared/references/benchmark/00_eva-benchmark-copy_对标文案拆解.md
../eva-shared/references/quality/00_eva-ai-check_表达真实性审查.md
references/create/shortvideo/00_eva-shortvideo_主入口.md
references/create/shortvideo/title/00_eva-title_标题即选题.md
references/create/shortvideo/opening/00_eva-opening_开头针对性优化.md
references/create/shortvideo/opening/01_eva-opening-diagnosis_开头承接与兑现诊断.md
references/create/shortvideo/opening/02_eva-opening-generation_开头方案生成与推荐.md
references/create/shortvideo/script/00_eva-script_思维流爆款内容创作.md
references/create/shortvideo/script/03_eva-script-runtime_普通正文简版路线.md
../eva-shared/references/commerce/00_eva-commerce_商单主入口.md
../eva-shared/references/shared/00_handoff-cards_交接卡字段真源.md
../eva-shared/references/shared/02_low-confidence_低置信度授权协议.md
../eva-shared/references/shared/03_commercial-constraint-card_商单约束卡真源.md
../eva-shared/references/shared/04_light-interaction_轻交互协议.md
../eva-shared/references/shared/05_expression-asset-preload_表达资产轻量预加载协议.md
../eva-shared/references/shared/06_external-material-safety_外部材料安全边界.md
../eva-shared/references/shared/07_next-step-navigation_动态选路与下一步推荐.md
../eva-shared/schemas/asset-types.json
../eva-shared/references/asset/00_eva-asset_资产卡协议.md

Boundaries

• Ordinary requests like "write a Moments post / write a Weibo post / write Xiaohongshu short graphics" do not fall under Eva Create; stop this entry and let the basic model complete it directly without automatically triggering Link. Enter Article only when the user clearly requests to write an official account article, self-media article, or long opinion piece.
• Requests like "extract the tone of my Moments posts / adjust the style / write in this style in the future / this is a sample of my previous Moments posts" are not creation intentions; transfer to user style extraction in shared Memory.
• Requests like "Moments Link / use my Moments Link" are not ordinary Create tasks; transfer to

  eva-link

  .
• Only when the current creation truly reads user files, pasted third-party content, screenshots, tables, Briefs, or benchmark samples should the external material safety boundary be read; do not load it for creation without materials.
• Only when entering personalized title, opening, roadmap, or final draft, and the current task truly requires persona, real experience, or writing style should the expression asset preload protocol be read.
• Before Short Video enters the complete draft, check the specific audience, cognitive gaps, and user questions using shared Audience Finder; if any item fails, directly read shared Audience Finder, then return to Create without going back to Think. Article judges based on its own reader tasks, core judgments, and material adequacy.
• In the link relying on cover or title clicks, when the user first requests "write a draft first / write the script directly" but there are no verification clues for the title, still enter the title search solution and do not bypass the title hard gate even if information is complete.
• When the user clearly requests to create a complete voiceover for platforms like Douyin or Video Account that do not require cover clicks, do not force platform title search; form the content entry according to the first sentence link, then enter the simplified or complete route. Only enter the title link when the user simultaneously requests cover title, body title, or title optimization.
• Only when Eva has clearly requested to search for a title first, and the user then explicitly states "I know the title hasn't been verified, but I still want to see the draft first / try the structure first" should it be regarded as accepting the unverified draft boundary. Output a low-confidence draft at this time and stop blocking repeatedly; the draft cannot be packaged as a final draft ready for direct release. Commercial forbidden zones, fictional experiences, fictional data, and safety boundaries cannot be bypassed through repeated requests.
• If there are no verification clues in the Short Video title link, do not enter the high-confidence body text; Article title is placed at the back and does not inherit this gate.
• For Short Video commercial orders, first disassemble the Brief or Commerce constraints, then enter the title or first sentence link. The first version of an official brand-sponsored article only handles Brief/constraint handover and does not directly enter the Article final draft.
• Do not revise the complete draft while only conducting AI-style detection.
• Benchmark disassembly can only migrate structures, not copy them directly.
• When finding platform benchmarks for Short Video topics or titles, only output manual search terms, search paths, observation indicators, and requirements for pasting back; do not call web searches, external search Skills, browsers, or platform APIs to browse benchmarks for the user. Verification of public sources for key time-sensitive facts in Article does not count as "browsing platform benchmarks on behalf of users".
• Do not predict the playback, likes, completion rate, or conversion range of the next piece of content. You can organize the reference range of account history, evaluate the strength of verification evidence, and specify post-release observation indicators, but do not package the historical range as a prediction.
• When involving medical, financial, tax, or legal content, do not write unverified expressions as personalized professional conclusions; prompt the user to confirm with qualified professionals for specific high-risk consultations.
• Before generating handoff cards, asset cards, saving, or cross-module handover, must read

  asset-types.json

  and the Asset protocol for verification; light launch does not mean canceling the asset gate.
• When the user requests to check the current topic/manuscript from the perspective of readers, opponents, real industries, or creators, transfer to

  eva-lens

  , and continue Create after Lens returns a modification point.
• Create can conduct self-inspection of the final draft internally, but do not output the three-level conclusion of release readiness. When the user provides a basically formed, unpublished manuscript and explicitly requests "pre-release inspection / can this be published / final draft inspection", transfer to

  eva-preflight

  ; when the user explicitly requests to rewrite or continue completing the manuscript, stay in Create.
• When the user provides published content and result data, and the goal is to review what to modify for the next piece, transfer to

  eva-review

  ; Create does not explain publication performance.
• Only when the user explicitly asks about the next step, requests entry sorting or workflow, or the original request includes post-final-draft review should the dynamic routing source be read. After Create delivers the final draft, it defaults to only recommending Preflight and waiting; only when the user explicitly requests "review after writing" in advance should it be handed over to Preflight in the same round.