番茄小说 AI 创作工具调研
1. 介绍
1.1 平台背景与发布沿革
| 时间 | 事件 | 性质 |
|---|---|---|
| 2024-03 | 番茄作家助手推出 AI 续写功能 | 能力开放 |
| 2024-05 | 上线完整 AI 工具箱(取名、扩写、改写等) | 能力开放 |
| 2024-07 | "AI 训练补充协议"风波 | 治理冲突 |
| 2025-04-07 | 《番茄签约流程优化说明》发布,开始对签约作品开展实质性审核 | 治理收紧 |
| 2025-05 | 再度调整签约机制,提高签约门槛 | 治理收紧 |
| 2025-09-23 | 作者后台弹出"是否使用 AI"勾选项 | 合规落地 |
平台规模:
- 番茄小说 MAU 超 2.4 亿(QuestMobile,截至 2025 年 6 月底)。
- 番茄 AI 功能相比竞品"更成体系":涉及改写、扩写、续写、梗概大纲灵感、卡点续写;对比之下阅文"作家助手"内嵌 DeepSeek-R1/V3 侧重问答与推理,七猫"AI 小助理"仅 3 项功能。
番茄是本组中唯一同时具备"创作工具"与"分发 + 审核 + 签约平台"双重身份的对象。这一双重身份决定了它的 Harness 设计与所有纯工具型平台都不同:AI 工具的输出,最终要接受平台自己的审核。工具与裁判同属一个主体,这既是番茄的独特优势(规则同源、无需猜测标准),也是它的独特风险(作者缺乏独立第三方判断)。
1.2 官方定性
番茄小说官方公告《AI 写作工具功能上线通知》的定性原文:
"番茄 AI 写作工具是基于大语言模型的人工智能写作产品,在作者创作小说的过程中,为作者提供内容参考以及信息查询等方面的帮助。作者最终是否使用工具生成的内容、如何使用该内容由作者自行确定。"
三个关键词值得拆解:
| 关键词 | 含义 |
|---|---|
| "内容参考以及信息查询" | 把工具定位为辅助而非代笔 |
| "由作者自行确定" | 把使用责任明确归于作者 |
| "是否使用、如何使用" | 把申报义务前置提示 |
这一定性与其 L6 治理动作(强制申报、保底书禁用)是一致的:平台给你工具,但责任在你。
1.3 定价
| 项 | 内容 |
|---|---|
| 官方披露 | 无 |
| 第三方说法一 | "番茄小说 AI 助手价格与番茄会员绑定(19 元/月)" |
| 第三方说法二 | "完全免费" |
| 本组处理 | 两种说法互相矛盾,均不可采信,标 [待填写] |
撰写说明:官方公告未披露独立定价。第三方文章中的两种说法来源均为自媒体,且互相矛盾,本组不采信任一方,统一标注 [待填写]。
考虑到番茄的商业模式(免费阅读 + 广告变现,MAU 2.4 亿),AI 工具更可能是提升作者产能的免费投入而非收费项——但这是推断,非事实,不作为结论引用。
1.4 开放形态与入口
| 端 | 入口路径 |
|---|---|
| 电脑端 | 番茄小说网 → 作家专区 → 工作台 → 小说编辑器 |
| 手机端 | 最新版"番茄作家助手 App" → 小说编辑器 → "AI 工具箱" |
通用交互:"不满意还可以点击'换一换'重新生成"。
开放形态:仅限番茄官方 App / 工作台内使用,无 API、无外部集成、无第三方工具接入。这是本组封闭性最强的平台(与 NovelAI 相当),但原因不同——NovelAI 为隐私而封闭,番茄为治理可控而封闭。
2. 名词解释
| 术语 | 英文 / 缩写 | 释义 |
|---|---|---|
| AI 工具箱 | AI Toolbox | 番茄作家助手 App 内的 AI 功能集合入口 |
| 开书灵感 | — | 输入一个想法和小说分类,AI 生成 3 个灵感 |
| 生成大纲 | — | 基于选定灵感生成一部小说的大纲 |
| 卡文锦囊 | — | 选择小说类型并输入当前卡点,AI 生成 5 个后续情节 |
| AI 查询 / AI 助手 | — | 查询历史背景、人文资料、科学研究 |
| AI 起名 | — | 输入角色描述与特点,生成 10 个名字 |
| AI 扩写 | — | 根据原文扩充细节(仅限非保底书作者) |
| AI 改写 | — | 选择改写方向后按方向改写 |
| 自定义描写 | — | 选中原文后输入方向(如"添加更多心理描写") |
| AI 续写 | — | 紧接着上文续写生成下文(仅限非保底作者) |
| 换一换 | Regenerate | 对生成结果不满意时重新生成 |
| 保底书 | Guaranteed-income Work | 与平台签订保底合同的作品,作者有收入保障 |
| 非保底书 | Non-guaranteed Work | 无固定保底收入、按分成结算的作品 |
| 签约 | Contract | 与平台签订合同 |
| 首秀 | Debut / First Showcase | 新作品首次获得平台推荐展示 |
| 上架 / 入 V | VIP Chapters | 开始设 VIP 付费章节 |
| MAU | Monthly Active Users | 月活跃用户数 |
| 三次签约机会 | — | 宣称在字数节点可分别申请签约、三次失败则永久失去资格 |
| AIGC | AI Generated Content | 人工智能生成内容 |
| 网文 | Web Novel / Online Literature | 网络原创文学的简称 |
| 卡文 | Writer's Block | 写不出下文的创作停滞状态 |
| 大纲 | Outline / Synopsis | 小说的蓝图和骨架 |
| 爽点 | Satisfaction Beat | 让读者感到愉悦、解气、兴奋的情节 |
| 节奏 | Pacing | 情节发展的快慢 |
| 黄金三章 | First Three Chapters | 小说开头三章,决定读者去留 |
| 吃书 | Continuity Error / Retcon | 长篇连载中遗忘早期设定导致前后矛盾 |
| IAA | In-App Advertisement | 免费广告变现模式 |
| 长上下文遗忘 | Long-Context Forgetting / Coherence Drift | 模型在超长文本中丢失早期设定的现象 |
3. 功能说明
3.1 官方功能清单
来源:番茄小说官方公告《AI 写作工具功能上线通知》(高可信,来自官方公告页)
| 功能 | 说明 | 端 | 权限限制 |
|---|---|---|---|
| 开书灵感 | 输入一个简单想法和小说分类,点击"生成"灵感,AI 生成 3 个灵感;可在感兴趣处点"生成大纲"得到完整小说大纲 | 仅电脑端 | — |
| 生成大纲 | 基于选定灵感生成一部小说的大纲,作者可修改制作雏形 | 仅电脑端 | — |
| 卡文锦囊 | 选择小说类型并输入当前卡点,AI 生成 5 个后续小说情节供选择 | 双端 | — |
| AI 查询 / AI 助手 | 查询历史背景、人文资料、科学研究 | PC 端"资料查询" / 手机端"AI 助手" | — |
| AI 起名 | 输入角色描述与特点,生成 10 个名字;也支持地点、门派、法宝、技能等自定义命名 | 双端 | — |
| AI 扩写 | 根据原文扩充细节 | 双端 | 仅限非保底书作者 |
| AI 改写 | 选择改写方向后按方向改写 | 双端 | — |
| 自定义描写 | 选中原文后输入方向(如"添加更多心理描写");或不选中直接输入描写内容 | 双端 | — |
| AI 续写 | 紧接着上文续写生成下文 | 双端 | 仅限非保底作者 |
功能设计的三个特征:
- 数量可控:灵感 3 个、情节 5 个、名字 10 个——全部给出固定的候选数量。这与 Sudowrite 的 Wormhole(5 个方向)思路一致:给有限选项而非无限生成,降低选择成本。
- 双端分化的功能布局:开书灵感与生成大纲仅电脑端(重规划,适合大屏),卡文锦囊与起名双端(轻操作,适合移动)。
- 权限分级:扩写与续写仅限非保底书作者——这是本组唯一按合同类型做能力分级的案例。
3.2 按创作阶段的编排
| 创作阶段 | 可用工具 |
|---|---|
| 开书前 | 开书灵感 → 生成大纲 |
| 写作中 · 卡住时 | 卡文锦囊(5 个后续情节) |
| 写作中 · 需延伸 | AI 续写、AI 扩写 |
| 写作中 · 需修改 | AI 改写、自定义描写 |
| 写作中 · 需资料 | AI 查询 / AI 助手 |
| 写作中 · 需命名 | AI 起名 |
这是一条清晰的按创作阶段编排的流水线(L3)。与 Sudowrite 的 Story Engine 3.0(前提→梗概→大纲→Beats→散文稿)相比,番茄的流水线更贴近中文网文的实际节奏——以"卡文"为核心场景,而非以"结构"为核心场景。
3.3 官方未提供的能力
| 能力 | 状态 | 后果 |
|---|---|---|
| 持久化世界观 / 人设库 | 未检索到官方说明 [待填写] | 每次生成只以"当前小说内容"为上下文 |
| 伏笔台账 | 无 | 无法自动检查伏笔是否回收 |
| 时间线管理 | 无 | 无时序状态 |
| 全书一致性检查 | 无 | 跨章矛盾需作者自行发现 |
| 版本化快照 | 无 | 无法回退到某一章的状态 |
| 自动质量评估 | 无(仅"换一换"重生成) | 质量判断完全靠作者 |
| 外部工具 / API | 无 | 无法集成第三方脚本 |
这一节直接对应本组核心论断:番茄的 L4 是以"当前小说内容"为状态源的弱状态层,没有显式的持久化世界观库。这意味着在番茄体系内,长篇一致性问题完全由作者承担——平台既不提供 Bible,也不提供伏笔台账。
4. 平台架构
图 4-1|番茄小说平台架构:生成回路与审核回路同平台闭环
数据来源:基于本文分析绘制的示意图。
4.1 总体架构
[作者] --> [番茄作家助手 App / 小说编辑器] --> [AI 工具箱]
|
+---------------+---------------+
| |
[大语言模型] [当前小说正文]
| |
+---------------+---------------+
|
[生成结果]
|
+---------------+---------------+
| |
[换一换 重生成] [作者采纳/修改]
|
v
[作品提交] --> [签约审核]
|
[AI 低质内容识别]
|
[AI 申报校验] 架构的关键特征:生成回路与审核回路闭环在同一个平台内。作者用平台工具生成 → 平台审核工具生成的内容 → 平台按申报情况判断。这种闭环是番茄 L6 治理最强的原因。
4.2 上下文构成
| 工具 | 上下文来源 |
|---|---|
| 续写 | 当前小说正文(紧接着上文) |
| 改写 / 自定义描写 | 选中的原文(或作者直接输入的描写要求) |
| 扩写 | 原文 |
| 开书灵感 | 一个简单想法 + 小说分类(最小上下文) |
| 卡文锦囊 | 小说类型 + 当前卡点 |
| AI 起名 | 角色描述与特点 |
| AI 查询 / 助手 | 查询词(历史背景、人文资料、科学研究) |
上下文策略:番茄采用"最小充分上下文"策略——每个工具只取完成该任务所必需的最小信息。开书灵感以"想法 + 分类"为最小上下文,续写以"当前正文"为上下文。
这一策略的优点是token 成本极低、响应快;缺点是长程信息完全缺失——模型看不到 30 章前埋的伏笔,也看不到人设卡。
4.3 与审核系统的耦合
| 审核环节 | 机制 | 时间 |
|---|---|---|
| 签约审核 | 对签约作品开展实质性审核,由机器判断内容是否为 AI 生成的"低质内容" | 2025-04-07 起 |
| AI 申报校验 | 作者后台"是否使用 AI"勾选项;未如实申报可能无法通过审核 | 2025-09-23 起 |
| 首秀数量管控 | 上线后男频每日首秀作品数一度降至一千以下,长期稳定在 1000—1500 部 | 2025-04-07 后 |
| 三次签约机会 | 宣称作品在字数节点可分别申请签约,三次评估均失败则永久失去签约资格 |
5. Harness 设计
5.1 L1 上下文工程层
| 组件 | 内容 | 评价 |
|---|---|---|
| 当前正文 | 续写 / 改写 / 自定义描写均"根据作者小说的内容" | 中(滑动窗口,无长程) |
| 最小输入 | 开书灵感以"想法 + 分类"为最小上下文 | 强(成本极低) |
| 世界观 / 人设 | 无持久化条目库 [待填写] | 弱 |
| 前文摘要 | 未检索到滚动摘要机制 | 弱 |
番茄的 L1 是典型的"够用即止"策略:不做长程上下文工程,只保证当前操作的即时相关性。对于日更 6000 字、单章场景密集的网文生产节奏,这一策略在单章层面是有效的——写一章只需要知道上一章发生了什么。
但代价在长篇上暴露:写到 100 万字时,模型依然只"看见"当前段落。
5.2 L2 工具与执行层
| 工具 | 类型 | 评价 |
|---|---|---|
| 开书灵感 | 生成 | 中(3 个候选) |
| 生成大纲 | 生成 | 中 |
| 卡文锦囊 | 生成 | 中高(5 个后续情节,直击痛点) |
| AI 查询 / 助手 | 检索 | 中(资料查询) |
| AI 起名 | 生成 | 中(10 个候选,支持地点/门派/法宝/技能) |
| AI 扩写 | 改写 | 中(非保底书限定) |
| AI 改写 | 改写 | 中 |
| 自定义描写 | 改写 | 中高(可指定描写方向) |
| AI 续写 | 生成 | 中(非保底作者限定) |
| 换一换 | 控制 | 中(多候选重生成) |
工具层共 9 项(含换一换),数量上仅次于 Sudowrite。其中卡文锦囊是最贴合网文实际痛点的设计——直接对应行业术语"卡文"。
对比:Sudowrite 的 Wormhole 生成 5 个方向,番茄的卡文锦囊生成 5 个后续情节——同一数字、同一思路,说明"给 5 个选项"是创意辅助的经验最优解。
5.3 L3 编排与控制层
按创作阶段编排的流水线:
[开书前] 开书灵感 --> 生成大纲
|
v
[写作中] +--> 卡文锦囊(卡住时)
+--> AI 续写 / AI 扩写(需延伸)
+--> AI 改写 / 自定义描写(需修改)
+--> AI 查询 / AI 助手(需资料)
+--> AI 起名(需命名)
|
v
[提交前] 是否使用 AI 申报 --> 签约审核 | 编排能力 | 番茄 | 评价 |
|---|---|---|
| 阶段流水线 | 有(开书前 / 写作中) | 中 |
| 多智能体 | 无 | 弱 |
| 结构模板 | 无(对比 Sudowrite 的 4 套模板) | 弱 |
| 人工在环 | 强(每次生成由人工触发,可"换一换") | 中高 |
| 权限分级 | 有(保底书禁用扩写/续写) | 本组唯一 |
番茄的 L3 最独特之处不在流水线,而在权限分级:同一个工具,对不同合同类型的作者开放不同能力。这是把 L6 治理策略下沉到 L2 工具层的实现——治理不靠事后审核,而靠能力本身的开关。
5.4 L4 记忆与状态层
| 状态类别 | 番茄承载方式 | 评价 |
|---|---|---|
| 世界观规则 | 无 [待填写] | 弱 |
| 角色状态 | 以"当前小说内容"为状态源 | 弱 |
| 时间线 | 无 | 弱 |
| 伏笔台账 | 无 | 弱 |
| 主线 / 支线进度 | 无 | 弱 |
| 信息披露边界 | 无 | 弱 |
| 版本化快照 | 无 | 弱 |
番茄的 L4 在本组 8 个平台中最弱。这是一个必须如实指出的判断。
原因分析(推断,非官方说明):番茄的核心业务指标是日更产能与首秀数量,其 AI 工具的设计目标是"帮作者今天把这一章写出来",而不是"帮作者把这本书写完整"。L4 的缺失是这个目标函数下的合理结果,但对长篇作者而言是实质性短板。
对核心论断的呼应:番茄恰好是核心论断的反例证据——它把 L6 做到了本组最强,但 L4 最弱。结果是:平台能确保"内容合规、申报如实、低质受控",但无法确保"作品在 100 万字时不崩"。这两件事是独立的,治理强 ≠ 长篇能力强。
5.5 L5 评估与观测层
| 评估手段 | 层级 | 位置 |
|---|---|---|
| "换一换"多候选重生成 | 作者侧 | 工具内 |
| 签约审核 + AI 低质内容识别 | 平台侧 | 审核系统 |
| 文本指纹技术(宣称) | 平台侧 |
平台侧评估的信号(来源:今日头条自媒体 ,不可作为事实引用):宣称番茄内部接入多维度文本指纹技术,捕捉词频异常、句子结构单一、情感波动平滑等信号。
这三个信号值得单独说明——它们是AI 生成文本的典型统计特征:
| 信号 | 含义 | 与 AI Slope 的关系 |
|---|---|---|
| 词频异常 | 某些词出现频率偏离人类分布 | 相关 |
| 句子结构单一 | 句长与句式的方差过小 | 直接对应 |
| 情感波动平滑 | 情绪曲线缺乏人类写作的起伏 | 相关 |
这与 HackerNoon 提出的 AI Slope(输出滑向统计平均值)是同一现象的两个观察角度:创作者侧把它当作需要对抗的质量问题(用 Perplexity Gate),平台侧把它当作需要识别的合规信号(用文本指纹)。
必须强调:上述文本指纹的描述来自自媒体来源,标 ,番茄官方未公开确认。
5.6 L6 治理与安全层
番茄是本组 L6 治理最强的样本,也是全组最重要的合规参考。
5.6.1 治理时间线
| 时间 | 动作 | 归类 |
|---|---|---|
| 2024-03 | 推出 AI 续写 | 能力开放 |
| 2024-05 | 上线完整 AI 工具箱 | 能力开放 |
| 2024-07 | "AI 训练补充协议"风波 | 冲突 |
| 2025-04-07 | 《番茄签约流程优化说明》,实质性审核 | 收紧 |
| 2025-05 | 调整签约机制,提高门槛 | 收紧 |
| 2025-09-23 | 强制"是否使用 AI"申报 | 合规落地 |
5.6.2 三条治理红线
红线一:能力分级——保底书禁用 AI 扩写与 AI 续写
AI 续写、AI 扩写能力仅限非保底书作者使用(保底书禁用)。这是本组唯一按合同类型做能力分级的设计,把治理从"事后审核"前移到"能力开关"。
红线二:强制 AI 申报
2025 年 9 月 23 日,番茄作者后台弹出"是否使用 AI"勾选项,提示"如果你上传的作品采用人工智能相关的工具进行合成/生成,需如实勾选",未如实申报可能无法通过审核。
红线三:AI 低质内容长期治理
2025 年 4 月 7 日《番茄签约流程优化说明》发布,开始对签约作品开展实质性审核,打击"大篇幅使用 AI 生成的低质内容"。效果:上线后男频每日首秀作品数一度降至一千以下,长期稳定在 1000—1500 部。
5.6.3 合规依据
番茄的 AI 申报动作直接对应《人工智能生成合成内容标识办法》第六条第四款——平台必须提供标识功能并提醒用户主动声明。
| 项 | 内容 |
|---|---|
| 法规 | 《人工智能生成合成内容标识办法》 |
| 施行日期 | 2025-09-01 |
| 对应条款 | 第六条第四款(平台须提供标识功能并提醒用户主动声明) |
| 番茄落地日期 | 2025-09-23 |
| 时间差 | 22 天 |
行业对照:
| 平台 | AI 标注要求 |
|---|---|
| 纵横中文网、七猫 | 早于番茄已要求作者标注 AI 使用情况 |
| 番茄 | 2025-09-23 强制申报 |
| 晋江文学城 | 2025-02《关于 AI 辅助写作使用、判定的试运行公告》,仅允许文字校对、创意要素辅助、创意粗纲辅助三种场景 |
| 起点中文网 | 靠人工编辑审核,几乎未受冲击 |
5.6.4 治理冲突与让步:2024 年 AI 训练补充协议风波
| 项 | 内容 |
|---|---|
| 时间 | 2024 年 7 月 |
| 触发 | 协议要求作者同意平台用其小说训练 AI 模型 |
| 反应 | 作者集体声讨与停更 |
| 结果 | 番茄发声明称"可协助作者解除条款" |
| 官方澄清 | 称仅"笔名"用于 AI 训练 |
这一事件是中文网文行业 L6 治理的第一次大规模冲突,其结果是确立了一条行业默认规则:平台用作者作品训练 AI 需单独、可撤销的授权。此后阅文采用 DeepSeek-R1 独立部署,正是对这一风险的规避。
5.7 六层能力小结
| 层 | 评级 | 关键实现 | 主要缺口 |
|---|---|---|---|
| L1 上下文工程 | 中 | 以当前小说正文为上下文;最小充分上下文策略 | 无世界观/人设库、无滚动摘要 |
| L2 工具与执行 | 中 | 9 项工具(开书灵感/卡文锦囊/起名/扩写/改写/自定义描写/续写/查询/换一换) | 无外部集成、无 API |
| L3 编排与控制 | 中 | 按创作阶段编排;权限分级(保底书禁用) | 无多智能体、无结构模板 |
| L4 记忆与状态 | 弱 | 以"当前小说内容"为状态源 | 无持久化世界观库、无伏笔台账、无时间线、无快照 |
| L5 评估与观测 | 中 | "换一换"多候选;平台侧签约审核 + AI 低质识别 | 无作者侧自动质量评估 |
| L6 治理与安全 | 最强 | 保底书禁用扩写/续写 + 强制 AI 申报 + 低质治理 + 训练条款可解除 | — |
对核心论断的呼应(重要):番茄是本组核心论断的反例样本。它证明了"L6 最强"与"L4 最强"是相互独立的两件事——一个平台可以在治理上做到行业标杆,同时在长程状态管理上几乎空白。对于长篇作者,这意味着:在番茄写长篇,合规由平台负责,一致性由你自己负责。
6. 实际案例
6.1 案例一:2024 年 AI 训练补充协议风波
背景:2024 年 7 月,番茄要求作者签署"AI 训练补充协议",同意平台用其小说训练 AI 模型。
冲突:协议触及作者最核心的资产——作品的数据权益。协议公布后引发作者集体声讨与停更。
结果:
- 番茄发布声明,称"可协助作者解除条款";
- 官方澄清称仅"笔名"用于 AI 训练。
工程与治理解读:
| 维度 | 解读 |
|---|---|
| 故障层 | L6 治理——数据权属授权机制缺失 |
| 根因 | 把"能力开放"置于"权属协商"之前,治理后置 |
| 修复方式 | 可撤销授权 + 缩小训练数据范围 |
| 行业影响 | 确立"训练需单独可撤销授权"的默认规则;此后阅文选择独立部署以规避同类风险 |
这是本组唯一记录完整"治理冲突—让步—规则确立"全过程的案例,对任何需要采集用户数据做模型训练的 AI 产品都有直接参考价值。
6.2 案例二:2025-04-07 签约流程优化与首秀数量变化
背景:AI 工具箱上线近一年后,平台面临"大篇幅使用 AI 生成的低质内容"涌入的问题。
方案:2025 年 4 月 7 日发布《番茄签约流程优化说明》,开始对签约作品开展实质性审核,由机器判断内容是否为 AI 生成的"低质内容";2025 年 5 月再度调整签约机制,提高签约门槛。
效果:
| 指标 | 变化 |
|---|---|
| 男频每日首秀作品数 | 上线后一度降至一千以下 |
| 长期稳定区间 | 1000—1500 部 |
解读:这是一个可观测的治理效果指标——首秀数量的下降直接反映了低质内容被拦截的规模。以"长期稳定在 1000—1500 部"反推,治理前该数字应显著高于 1500(具体数值未披露 [待填写])。
同时需注意:这一审核是机器判定,存在误判风险。对作者而言,这意味着"写得像 AI"本身已成为一种风险——这与 Sudowrite 用 Muse 对抗 AI Slope 是同一问题的两个面向:平台在惩罚 AI Slope,工具在对抗 AI Slope。
6.3 案例三:2025-09-23 强制 AI 申报与合规落地
背景:《人工智能生成合成内容标识办法》2025 年 9 月 1 日施行,其第六条第四款要求平台必须提供标识功能并提醒用户主动声明。
方案:2025 年 9 月 23 日,番茄作者后台弹出"是否使用 AI"勾选项,提示原文为"如果你上传的作品采用人工智能相关的工具进行合成/生成,需如实勾选"。
效果:未如实申报可能无法通过审核。
合规链条:
《人工智能生成合成内容标识办法》
| 2025-09-01 施行
| 第六条第四款:平台须提供标识功能并提醒用户主动声明
v
番茄作者后台"是否使用 AI"勾选项
| 2025-09-23 上线(法规施行后 22 天)
v
未如实申报 --> 可能无法通过审核 这是本组最重要的合规样本,也是中文网文行业从"平台自律"转向"法定义务"的标志性事件。横向对照:纵横中文网、七猫早于番茄已要求作者标注 AI 使用情况,说明行业领先者的合规动作早于法规强制。
6.4 案例四:能力分级——保底书禁用扩写与续写
背景:保底书与非保底书在合同性质上不同——保底书作者有收入保障,平台承担更大的商业风险。
方案:AI 续写、AI 扩写能力仅限非保底书作者使用(保底书禁用)。
设计解读:
| 维度 | 解读 |
|---|---|
| 分级依据 | 合同类型(保底 / 非保底) |
| 禁用范围 | 仅 AI 扩写与 AI 续写——即"直接产出正文"的两项能力 |
| 未禁用 | 灵感、大纲、起名、查询、改写、自定义描写 |
| 设计逻辑 | 风险与生成量正相关:直接产出正文的 AI 能力风险最高,故对高商业价值作品禁用 |
这是本组最精细的治理设计之一。它没有一刀切地"禁止 AI",而是按"该能力对最终文本的贡献度"做分级:灵感与大纲是辅助(低风险,全开放),续写与扩写是代笔(高风险,按合同类型限制)。
这一分级思路对其他场景的 AI 治理有直接借鉴价值:治理颗粒度应细化到"具体能力 × 具体风险等级",而非"用了 AI / 没用 AI"的二元判断。
7. 总结
7.1 优势
- L6 治理本组最强、也是行业标杆:保底书禁用扩写/续写 + 强制 AI 申报 + 低质内容长期治理 + 训练条款可解除,四层治理完整。
- 合规响应最快:《人工智能生成合成内容标识办法》2025-09-01 施行,番茄 2025-09-23 即上线申报功能,仅 22 天。
- 能力分级颗粒度最细:按合同类型(保底 / 非保底)× 能力风险(生成正文 vs 辅助)二维分级。
- 官方功能说明可信度高:功能清单来自官方公告页,非第三方演绎。
- 工具箱体系化程度高:9 项工具覆盖创作全流程,对比七猫"AI 小助理"仅 3 项功能。
- 卡文锦囊直击中文网文核心痛点(对应"卡文"这一行业术语)。
- 工具与审核同属一个平台,规则同源,作者无需猜测审核标准。
7.2 局限与已知短板
- L4 记忆与状态层本组最弱:无持久化世界观库、无伏笔台账、无时间线、无版本化快照。长篇一致性完全由作者承担。
- 定价完全不透明:两种第三方说法互相矛盾,均不可采信。
- 审核为机器判定,存在误判风险;"写得像 AI"本身成为风险。
- 无外部集成能力:仅限官方 App / 工作台,无 API。
- 治理历史上有重大冲突:2024 年"AI 训练补充协议"风波导致作者集体停更。
- 签约门槛持续提高:2025-04 与 2025-05 两次收紧,作者生存空间压缩。
- 无结构模板:对比 Sudowrite 的 4 套大纲模板,番茄仅有"生成大纲"单一能力。
7.3 适用边界
| 适用 | 不适用 |
|---|---|
| 番茄平台内的中文网文创作与投稿 | 其他平台投稿(工具不通用) |
| 日更节奏下的单章产能提升 | 需要长程一致性的百万字长篇(L4 不足) |
| 卡文时的情节突破 | 需要世界观/人设持久化的设定密集型作品 |
| 开书阶段的灵感与大纲 | 需要外部工具集成的工程化工作流 |
| 非保底书作者的扩写/续写需求 | 保底书作者的扩写/续写(被禁用) |
7.4 选型建议
- 必选场景:你在番茄平台投稿。此时官方 AI 工具箱是唯一与审核标准同源的选择,且必须使用其申报流程。
- 能力组合建议:番茄的 L4 是空白,长篇作者应自行建立外部状态层——可参考
05-claude-fiction.md的 Bible/State/Timeline 四目录,或07-chinese-webnovel-ai.md所述灵蟹创作的项目宪法,在番茄之外维护世界观与伏笔台账。 - 合规强制提示:自 2025-09-01 起,AI 标识是法定义务。使用任何第三方 AI 工具(NovelAI、Sudowrite、Claude 等)生成的内容在番茄发布时,均须如实勾选"是否使用 AI"。这些工具本身不提供 AIGC 标识能力,义务完全由作者承担。
- 保底书作者特别提示:AI 扩写与 AI 续写对保底书禁用。若你的作品是保底合同,应避免在官方工具之外的任何平台使用同类能力,以免与合同条款冲突。
信息缺口声明
- 番茄 AI 写作工具的定价:官方公告未披露独立定价;第三方"19 元/月绑定会员"与"完全免费"两种说法互相矛盾,均不可采信,标
[待填写]。 - 持久化世界观 / 人设库:未检索到官方说明,按"无"处理并标
[待填写]。 - 文本指纹技术的三个信号(词频异常、句子结构单一、情感波动平滑):来自今日头条自媒体来源,官方未确认,标 ,仅作现象描述不作事实引用。
- "三次签约机会"制度:仅见于自媒体来源,标 。
- 治理前的首秀作品数量:未披露,无法计算降幅,标
[待填写]。 - "4 种规则框架内安全的用法"(AI 搭框架自己填血肉 / AI 起名查资料扩灵感 / AI 预审查漏洞优化节奏 / 勾选"使用 AI"如实声明):来自自媒体来源,标 ,未作事实引用。
- 第三方关于"节奏提示""爽点建议"的描述:检索报告明确判定为演绎,不得当事实引用,本文未采用。
- AI 申报是否写入 AIGC 元数据字段:未检索到技术实现说明,标
[待填写]。 - 番茄 AI 底层模型:官方仅表述为"基于大语言模型",未披露具体模型,标
[待填写]。
8. 参考资料
- 番茄小说官方公告《AI 写作工具功能上线通知》 — 番茄小说,2024。https://fanqienovel.com/writer/zone/article/7327136545129906238
- 海克财经《番茄小说的 AI 难题》(新浪财经) — 海克财经,2025。https://finance.sina.com.cn/search/2025-10-09/doc-infthsqh9655363.shtml
- 搜狐文化《2024—2025 双年榜 序言一:AI 时代、"大文学观"与世界暗面的温柔》 — 搜狐文化,2025。https://cul.sohu.com/a/1058758339_121124749
- 中新经纬《创作心血变 AI 养料?网文作者"揭竿而起",番茄小说忙澄清》 — 中新经纬,2025。https://www.jwview.com/jingwei/html/07-26/601732.shtml
- 今日头条《番茄 2026 年 AI 新政:纯 AI 生成永久封号,但这样用 AI 反而加分》 — 今日头条,2026。 https://m.toutiao.com/article/7626281118299357747
- 今日头条《2026 年适合番茄小说作者的 AI 工具推荐》 — 今日头条,2026。 https://www.toutiao.com/article/7654053329475043846
- 中国青年报《"妙笔通鉴""漫剧助手"发布,AI 赋能网文创作和 IP 改编》(腾讯网) — 中国青年报,2025。https://new.qq.com/rain/a/20251017A08J6J00
- 百度百科《作家助手妙笔版》 — 百度百科。https://baike.baidu.com/item/%E4%BD%9C%E5%AE%B6%E5%8A%A9%E6%89%8B%E5%A6%99%E7%AC%94%E7%89%88/63227250
- HackerNoon《Claude Book: A Multi-Agent Framework for Writing Novels with Claude Code》 — HackerNoon。https://hackernoon.com/claude-book-a-multi-agent-framework-for-writing-novels-with-claude-code
- Sudowrite 官方博客《How Sudowrite Works: Story Bible, Muse, and the Tools》 — Sudowrite。https://sudowrite.com/blog/how-sudowrite-works
- 美篇《新手如何开始网文写作》 — 美篇。https://www.meipian.cn/5gn73n9w
- 今日头条《小说写作技巧笔记:从入门到进阶》 — 今日头条。https://m.toutiao.com/article/7666250379276927531
- 极客公园《AI 能不能写出〈庆余年〉?》 — 极客公园。https://so.html5.qq.com/page/real/search_news?docid=70000021_10168f9fb6122152
Fanqie Novel AI Creation Tool Research
1. Introduction
1.1 Platform Background and Release History
| Time | Event | Nature |
|---|---|---|
| 2024-03 | Fanqie Writer Assistant launches the AI Continuation feature | Capability rollout |
| 2024-05 | Launches a full AI toolbox (naming, expansion, rewriting, etc.) | Capability rollout |
| 2024-07 | "AI Training Supplementary Agreement" controversy | Governance conflict |
| 2025-04-07 | "Fanqie Contract Process Optimization Notice" published; substantive review of contracted works begins | Governance tightening |
| 2025-05 | Contract mechanism adjusted again, raising the bar for contracting | Governance tightening |
| 2025-09-23 | A "Use AI?" checkbox pops up in the author dashboard | Compliance implementation |
Platform scale:
- Fanqie Novel MAU exceeds 240 million (QuestMobile, as of end of June 2025).
- Compared with competitors, Fanqie's AI features are "more systematic": covering rewriting, expansion, continuation, synopsis/outline/idea generation, and continuation at plot hold-points; by contrast, Yuewen's "Writer Assistant" embeds DeepSeek-R1/V3, which focuses on Q&A and reasoning, while Qimao's "AI Assistant" has only 3 features.
Fanqie is the only subject in this group that simultaneously holds the dual identity of "creation tool" and "distribution + review + contract platform". This dual identity makes its Harness design fundamentally different from all pure-tool platforms: the output of the AI tools must ultimately pass the platform's own review. The tool and the umpire belong to the same entity, which is both Fanqie's unique strength (rules come from a single source, with no need to guess the standards) and its unique risk (authors lack an independent third-party assessment).
1.2 Official Positioning
The official phrasing from Fanqie Novel's announcement "AI Writing Tool Feature Launch Notice":
"Fanqie's AI writing tool is an AI writing product built on large language models. During the author's process of creating a novel, it provides the author with assistance such as content reference and information lookup. Whether the author ultimately uses the content generated by the tool, and how they use it, is decided by the author themselves."
Three keywords are worth unpacking:
| Keyword | Meaning |
|---|---|
| "Content reference and information lookup" | Positions the tool as an aid rather than a ghostwriter |
| "Decided by the author themselves" | Clearly assigns responsibility for use to the author |
| "Whether to use, and how to use" | Front-loads the disclosure obligation reminder |
This positioning is consistent with its L6 governance actions (mandatory disclosure, disabling for guaranteed-income works): the platform gives you the tool, but the responsibility is yours.
1.3 Pricing
| Item | Content |
|---|---|
| Official disclosure | None |
| Third-party claim 1 | "Fanqie AI assistant pricing is bundled with Fanqie membership (19 CNY/month)" |
| Third-party claim 2 | "Completely free" |
| This group's handling | The two claims contradict each other and neither can be trusted; marked [To be filled] |
Editorial note: The official announcement did not disclose a standalone price. Both claims in the third-party articles come from self-media sources and contradict each other, so this group does not trust either and uniformly marks them [To be filled].
Given Fanqie's business model (free reading + ad monetization, 240 million MAU), the AI tool is more likely a free investment to boost author output rather than a paid item — but this is inference, not fact, and is not cited as a conclusion.
1.4 Open Form and Entry Points
| Endpoint | Entry Path |
|---|---|
| Desktop | Fanqie Novel website → Writer Zone → Workbench → Novel Editor |
| Mobile | Latest "Fanqie Writer Assistant App" → Novel Editor → "AI Toolbox" |
General interaction: "If you're not satisfied, you can click 'Regenerate' to generate again".
Open form: usable only within the official Fanqie App / Workbench; no API, no external integration, and no third-party tool access. This is the most closed platform in this group (comparable to NovelAI), but for a different reason — NovelAI is closed for privacy, while Fanqie is closed for governance control.
2. Glossary
| Term | English / Abbreviation | Definition |
|---|---|---|
| AI Toolbox | AI Toolbox | Entry point for the AI feature collection in the Fanqie Writer Assistant App |
| Opening-book inspiration | — | Input an idea and a novel category; AI generates 3 ideas |
| Generate outline | — | Based on a selected idea, generate the outline of a novel |
| Writer's-block help | — | Select a novel type and input the current sticking point; AI generates 5 follow-up plot developments |
| AI query / AI assistant | — | Look up historical background, humanities materials, and scientific research |
| AI naming | — | Input a character description and traits; generate 10 names |
| AI expansion | — | Expand details based on the original text (only for authors of non-guaranteed-income works) |
| AI rewriting | — | Select a rewriting direction, then rewrite accordingly |
| Custom description | — | Select original text and input a direction (e.g., "add more psychological description") |
| AI continuation | — | Continue and generate the following text based on the preceding text (only for non-guaranteed-income authors) |
| Regenerate | Regenerate | Regenerate when you are unsatisfied with the generated result |
| Guaranteed-income work | Guaranteed-income Work | A work signed with a guaranteed-income contract; the author has income security |
| Non-guaranteed work | Non-guaranteed Work | A work without fixed guaranteed income, settled by revenue sharing |
| Contract | Contract | Signing a contract with the platform |
| First showcase | Debut / First Showcase | The first time a new work receives a recommended showcase on the platform |
| VIP chapters / Enter V | VIP Chapters | Start offering VIP paid chapters |
| MAU | Monthly Active Users | Monthly active users |
| Three contract opportunities | — | Claimed that one can apply for a contract at certain word-count milestones; three failures permanently lose eligibility |
| AIGC | AI Generated Content | Artificial intelligence-generated content |
| Web novel | Web Novel / Online Literature | Abbreviation for online original literature |
| Writer's block | Writer's Block | A state of stalled creation in which the author cannot write the next part |
| Outline | Outline / Synopsis | The blueprint and skeleton of a novel |
| Satisfaction beat | Satisfaction Beat | Plot points that give readers pleasure, catharsis, and excitement |
| Pacing | Pacing | How fast or slow the plot develops |
| First three chapters | First Three Chapters | The opening three chapters of a novel, which decide whether readers stay |
| Continuity error | Continuity Error / Retcon | Forgetting early settings over a long serialization, causing internal contradictions |
| IAA | In-App Advertisement | The free ad-monetization model |
| Long-context forgetting | Long-Context Forgetting / Coherence Drift | The phenomenon in which a model loses early settings in very long texts |
3. Feature Description
3.1 Official Feature List
Source: Fanqie Novel's official announcement "AI Writing Tool Feature Launch Notice" (high credibility, from the official announcement page)
| Feature | Description | Endpoint | Permission Restrictions |
|---|---|---|---|
| Opening-book inspiration | Input a simple idea and a novel category, click "Generate" for ideas, and the AI generates 3 ideas; at a point of interest you can click "Generate Outline" to get a complete novel outline | Desktop only | — |
| Generate outline | Based on a selected idea, generate the outline of a novel; the author can modify it into a draft | Desktop only | — |
| Writer's-block help | Select a novel type and input the current sticking point; the AI generates 5 follow-up plot developments to choose from | Both ends | — |
| AI query / AI assistant | Look up historical background, humanities materials, and scientific research | "Material query" on PC / "AI assistant" on mobile | — |
| AI naming | Input a character description and traits; generate 10 names; also supports custom naming for places, sects, artifacts, skills, etc. | Both ends | — |
| AI expansion | Expand details based on the original text | Both ends | Only for authors of non-guaranteed-income works |
| AI rewriting | Select a rewriting direction, then rewrite accordingly | Both ends | — |
| Custom description | Select original text and input a direction (e.g., "add more psychological description"); or directly input description content without selecting | Both ends | — |
| AI continuation | Continue and generate the following text based on the preceding text | Both ends | Only for non-guaranteed-income authors |
Three characteristics of the feature design:
- Controlled quantities: 3 ideas, 5 plot developments, 10 names — all give fixed candidate counts. This aligns with Sudowrite's Wormhole (5 directions): give finite options rather than unlimited generation, to lower the cost of choosing.
- Split feature layout across the two ends: Opening-book inspiration and outline generation are desktop-only (heavier planning, suited to large screens), while writer's-block help and naming are on both ends (light operations, suited to mobile).
- Permission tiering: Expansion and continuation are only for authors of non-guaranteed-income works — the only case in this group where capability is tiered by contract type.
3.2 Orchestration by Creation Stage
| Creation Stage | Available Tools |
|---|---|
| Before opening the book | Opening-book inspiration → Generate outline |
| While writing · stuck | Writer's-block help (5 follow-up plot developments) |
| While writing · need to extend | AI continuation, AI expansion |
| While writing · need to revise | AI rewriting, custom description |
| While writing · need materials | AI query / AI assistant |
| While writing · need naming | AI naming |
This is a clear pipeline orchestrated by creation stage (L3). Compared with Sudowrite's Story Engine 3.0 (premise → synopsis → outline → Beats → prose draft), Fanqie's pipeline is closer to the actual rhythm of Chinese web novels — with "writer's block" as the core scenario rather than "structure".
3.3 Capabilities Not Officially Provided
| Capability | Status | Consequence |
|---|---|---|
| Persistent worldview / character library | No official description found [To be filled] | Each generation uses only the "current novel content" as context |
| Foreshadowing ledger | None | Cannot automatically check whether foreshadowing is resolved |
| Timeline management | None | No temporal state |
| Whole-book consistency check | None | Cross-chapter contradictions must be found by the author |
| Versioned snapshots | None | Cannot roll back to the state of a given chapter |
| Automatic quality assessment | None (only "Regenerate" re-generation) | Quality judgment relies entirely on the author |
| External tools / API | None | Cannot integrate third-party scripts |
This section directly corresponds to this group's core assertion: Fanqie's L4 is a weak state layer that uses "current novel content" as its state source, with no explicit persistent worldview library. This means that within the Fanqie system, long-form consistency problems rest entirely on the author — the platform provides neither a Bible nor a foreshadowing ledger.
4. Platform Architecture
图 4-1|番茄小说平台架构:生成回路与审核回路同平台闭环
数据来源:基于本文分析绘制的示意图。
4.1 Overall Architecture
[作者] --> [番茄作家助手 App / 小说编辑器] --> [AI 工具箱]
|
+---------------+---------------+
| |
[大语言模型] [当前小说正文]
| |
+---------------+---------------+
|
[生成结果]
|
+---------------+---------------+
| |
[换一换 重生成] [作者采纳/修改]
|
v
[作品提交] --> [签约审核]
|
[AI 低质内容识别]
|
[AI 申报校验] The key characteristic of the architecture: the generation loop and the review loop are closed inside the same platform. The author generates with the platform's tool → the platform reviews the content the tool generated → the platform judges based on the declaration. This closed loop is why Fanqie has the strongest L6 governance.
4.2 Context Composition
| Tool | Context Source |
|---|---|
| Continuation | Current novel body text (right after the preceding text) |
| Rewriting / custom description | Selected original text (or description requirements directly input by the author) |
| Expansion | Original text |
| Opening-book inspiration | A simple idea + novel category (minimal context) |
| Writer's-block help | Novel type + current sticking point |
| AI naming | Character description and traits |
| AI query / assistant | Query terms (historical background, humanities materials, scientific research) |
Context strategy: Fanqie adopts a "minimal sufficient context" strategy — each tool takes only the minimum information needed to complete its task. Opening-book inspiration uses "idea + category" as minimal context, and continuation uses the "current body text" as context.
The advantage of this strategy is extremely low token cost and fast responses; the drawback is complete absence of long-range information — the model cannot see foreshadowing planted 30 chapters earlier, nor the character cards.
4.3 Coupling with the Review System
| Review Link | Mechanism | Time |
|---|---|---|
| Contract review | Substantive review of contracted works; a machine judges whether the content is AI-generated "low-quality content" | From 2025-04-07 |
| AI declaration check | "Use AI?" checkbox in the author dashboard; failure to declare truthfully may prevent passing review | From 2025-09-23 |
| First-showcase quantity control | After launch, the daily number of male-channel first-showcase works once fell below one thousand, and has long stayed stable at 1000–1500 | After 2025-04-07 |
| Three contract opportunities | Claimed that a work can apply for a contract separately at word-count milestones; failing all three evaluations permanently loses contract eligibility |
5. Harness Design
5.1 L1 Context Engineering Layer
| Component | Content | Rating |
|---|---|---|
| Current body text | Continuation / rewriting / custom description are all "based on the author's novel content" | Medium (sliding window, no long range) |
| Minimal input | Opening-book inspiration uses "idea + category" as minimal context | Strong (extremely low cost) |
| Worldview / characters | No persistent entry library [To be filled] | Weak |
| Previous-text summary | No rolling-summary mechanism found | Weak |
Fanqie's L1 is a typical "enough to get by" strategy: it does no long-range context engineering)Skip, only ensuring immediate relevance for the operation at hand. For a web-novel production rhythm of daily 6,000 characters with dense single-chapter scenes, this strategy is effective at the single-chapter level — writing a chapter only requires knowing what happened in the previous one.
But the cost emerges in long-form works: when a work reaches one million characters, the model still only "sees" the current paragraph.
5.2 L2 Tools and Execution Layer
| Tool | Type | Rating |
|---|---|---|
| Opening-book inspiration | Generate | Medium (3 candidates) |
| Generate outline | Generate | Medium |
| Writer's-block help | Generate | Medium-High (5 follow-up plots, hitting the pain point directly) |
| AI query / assistant | Retrieve | Medium (material query) |
| AI naming | Generate | Medium (10 candidates, supports locations/sects/artifacts/skills) |
| AI expansion | Rewrite | Medium (limited to non-guaranteed-income works) |
| AI rewriting | Rewrite | Medium |
| Custom description | Rewrite | Medium-High (can specify the description direction) |
| AI continuation | Generate | Medium (limited to non-guaranteed-income authors) |
| Regenerate | Control | Medium (multi-candidate re-generation) |
The tool layer has 9 items in total (including Regenerate), second only to Sudowrite in quantity. Among them, writer's-block help is the design that best matches the real pain point of web novels — it corresponds directly to the industry term "writer's block".
Comparison: Sudowrite's Wormhole generates 5 directions, while Fanqie's writer's-block help generates 5 follow-up plot developments — the same number, the same idea, showing that "giving 5 options" is the empirically optimal solution for creative assistance.
5.3 L3 Orchestration and Control Layer
A pipeline orchestrated by creation stage:
[开书前] 开书灵感 --> 生成大纲
|
v
[写作中] +--> 卡文锦囊(卡住时)
+--> AI 续写 / AI 扩写(需延伸)
+--> AI 改写 / 自定义描写(需修改)
+--> AI 查询 / AI 助手(需资料)
+--> AI 起名(需命名)
|
v
[提交前] 是否使用 AI 申报 --> 签约审核 | Orchestration Capability | Fanqie | Rating |
|---|---|---|
| Stage pipeline | Yes (before opening the book / while writing) | Medium |
| Multi-agent | None | Weak |
| Structure templates | None (vs. Sudowrite's 4 templates) | Weak |
| Human in the loop | Strong (every generation is triggered by a human; can "Regenerate") | Medium-High |
| Permission tiering | Yes (expansion/continuation disabled for guaranteed-income works) | Only one in this group |
The most distinctive part of Fanqie's L3 is not the pipeline but permission tiering: the same tool opens different capabilities to authors of different contract types. This is an implementation that pushes the L6 governance strategy down to the L2 tool layer — governance relies not on post-hoc review but on the capability switch itself.
5.4 L4 Memory and State Layer
| State Category | How Fanqie Carries It | Rating |
|---|---|---|
| Worldview rules | None [To be filled] | Weak |
| Character state | Uses the "current novel content" as the state source | Weak |
| Timeline | None | Weak |
| Foreshadowing ledger | None | Weak |
| Main / subplot progress | None | Weak |
| Information-disclosure boundary | None | Weak |
| Versioned snapshots | None | Weak |
Fanqie's L4 is the weakest among the 8 platforms in this group. This is a judgment that must be stated honestly.
Reason analysis (inference, not official description): Fanqie's core business metrics are daily-update output and first-showcase quantity, and its AI tools are designed to "help the author write today's chapter" rather than "help the author complete the whole book". The absence of L4 is a reasonable result under this objective function, but it is a substantial shortcoming for long-form authors.
Echo of the core assertion: Fanqie happens to be the counter-example evidence for the core assertion — it achieves the strongest L6 in this group, yet the weakest L4. The result: the platform can ensure "compliant content, truthful declaration, and controlled low quality", but cannot ensure "the work does not collapse at one million characters". These two things are independent — strong governance ≠ strong long-form capability.
5.5 L5 Evaluation and Observation Layer
| Evaluation Method | Level | Location |
|---|---|---|
| "Regenerate" multi-candidate re-generation | Author side | Inside the tool |
| Contract review + AI low-quality content detection | Platform side | Review system |
| Text-fingerprint technology (claimed) | Platform side |
Signals for platform-side evaluation (source: Toutiao self-media, must not be cited as fact): it is claimed that Fanqie has internally integrated multi-dimensional text-fingerprint technology that captures signals such as abnormal word frequency, monotonous sentence structure, and flat emotional fluctuation.
These three signals deserve separate mention — they are typical statistical features of AI-generated text:
| Signal | Meaning | Relationship to AI Slope |
|---|---|---|
| Abnormal word frequency | Certain words appear at a frequency deviating from human distribution | Related |
| Monotonous sentence structure | The variance of sentence length and sentence patterns is too small | Directly corresponds |
| Flat emotional fluctuation | The emotion curve lacks the ups and downs of human writing | Related |
This is the same phenomenon as the AI Slope proposed by HackerNoon (output sliding toward statistical averages), seen from two angles: creators treat it as a quality problem to fight against (using the Perplexity Gate), while platforms treat it as a compliance signal to detect (using text fingerprints).
Must emphasize: the above description of text fingerprints comes from a self-media source, is marked [To be verified], and has not been publicly confirmed by Fanqie.
5.6 L6 Governance and Security Layer
Fanqie is the sample with the strongest L6 governance in this group, and the most important compliance reference for the whole group.
5.6.1 Governance Timeline
| Time | Action | Category |
|---|---|---|
| 2024-03 | Launch AI continuation | Capability rollout |
| 2024-05 | Launch the full AI toolbox | Capability rollout |
| 2024-07 | "AI Training Supplementary Agreement" controversy | Conflict |
| 2025-04-07 | "Fanqie Contract Process Optimization Notice"; substantive review | Tightening |
| 2025-05 | Adjust the contract mechanism, raising the bar | Tightening |
| 2025-09-23 | Mandatory "Use AI?" declaration | Compliance implementation |
5.6.2 Three Governance Red Lines
Red line 1: Capability tiering — AI expansion and AI continuation disabled for guaranteed-income works
The AI continuation and AI expansion capabilities are only available to authors of non-guaranteed-income works (disabled for guaranteed-income works). This is the only design in this group that tiers capability by contract type, moving governance forward from "post-hoc review" to a "capability switch".
Red line 2: Mandatory AI declaration
On September 23, 2025, a "Use AI?" checkbox popped up in the Fanqie author dashboard, prompting: "If the work you upload was synthesized/generated with AI-related tools, you must check the box truthfully"; a failure to declare truthfully may prevent passing review.
Red line 3: Long-term governance of AI low-quality content
On April 7, 2025, the "Fanqie Contract Process Optimization Notice" was published, starting substantive review of contracted works to crack down on "low-quality content generated with large amounts of AI". Effect: after launch, the daily number of male-channel first-showcase works once fell below one thousand, and has long stayed stable at 1000–1500.
5.6.3 Compliance Basis
Fanqie's AI declaration action directly corresponds to Article 6, Paragraph 4 of the "Measures for Identifying AI-Generated Synthetic Content" — platforms must provide a labeling function and remind users to proactively declare.
| Item | Content |
|---|---|
| Regulation | "Measures for Identifying AI-Generated Synthetic Content" |
| Effective date | 2025-09-01 |
| Corresponding clause | Article 6, Paragraph 4 (platforms must provide a labeling function and remind users to proactively declare) |
| Fanqie implementation date | 2025-09-23 |
| Time gap | 22 days |
Industry comparison:
| Platform | AI Labeling Requirement |
|---|---|
| Zongheng, Qimao | Ahead of Fanqie, already required authors to mark their AI usage |
| Fanqie | Mandatory declaration from 2025-09-23 |
| Jinjiang Literature City | 2025-02 "Trial Announcement on the Use and Determination of AI-Assisted Writing", allowing only three scenarios: text proofreading, creative-element assistance, and creative rough-outline assistance |
| Qidian Chinese | Relies on human editor review; almost unaffected |
5.6.4 Governance Conflict and Concession: The 2024 AI Training Supplementary Agreement Incident
| Item | Content |
|---|---|
| Time | July 2024 |
| Trigger | The agreement required authors to consent to the platform training AI models on their novels |
| Reaction | Collective condemnation and (chapters) halted by authors |
| Result | Fanqie issued a statement saying it could "help authors rescind the clause" |
| Official clarification | Says that only "pen names" are used for AI training |
This event was the first large-scale conflict over L6 governance in the Chinese web-novel industry; its outcome established an industry default rule: using authors' works to train AI requires separate, revocable authorization. Yuewen's subsequent independent deployment of DeepSeek-R1 is precisely an avoidance of this risk.
5.7 Six-Layer Capability Summary
| Layer | Rating | Key Implementation | Main Gaps |
|---|---|---|---|
| L1 Context engineering | Medium | Uses the current novel body text as context; minimal-sufficient-context strategy | No worldview/character library, no rolling summary |
| L2 Tools and execution | Medium | 9 tools (opening-book inspiration / writer's-block help / naming / expansion / rewriting / custom description / continuation / query / regenerate) | No external integration, no API |
| L3 Orchestration and control | Medium | Orchestrated by creation stage; permission tiering (disabled for guaranteed-income works) | No multi-agent, no structure templates |
| L4 Memory and state | Weak | Uses the "current novel content" as the state source | No persistent worldview library, no foreshadowing ledger, no timeline, no snapshots |
| L5 Evaluation and observation | Medium | "Regenerate" multi-candidate; platform-side contract review + AI low-quality detection | No author-side automatic quality assessment |
| L6 Governance and security | Strongest | Expansion/continuation disabled for guaranteed-income works + mandatory AI declaration + low-quality governance + revocable training clause | — |
Echo of the core assertion (important): Fanqie is the counter-example specimen for this group's core assertion. It proves that "strongest L6" and "strongest L4" are mutually independent — a platform can be an industry benchmark in governance while being nearly blank in long-range state management. For long-form authors, this means: when writing long-form on Fanqie, compliance is the platform's responsibility; consistency is your own.
6. Practical Case Studies
6.1 Case One: The 2024 AI Training Supplementary Agreement Incident
Background: In July 2024, Fanqie required authors to sign an "AI Training Supplementary Agreement", consenting to the platform training AI models on their novels.
Conflict: The agreement touched authors' most core asset — the data rights of their works. Its publication triggered collective condemnation and halted updates by authors.
Result:
- Fanqie issued a statement saying it could "help authors rescind the clause";
- Official clarification said that only "pen names" are used for AI training.
Engineering and governance interpretation:
| Dimension | Interpretation |
|---|---|
| Failure layer | L6 governance — the data-ownership authorization mechanism is absent |
| Root cause | Placing "capability rollout" before "ownership negotiation", with governance lagging behind |
| Fix | Revocable authorization + narrowing the training data scope |
| Industry impact | Established the default rule of "training requires separate revocable authorization"; Yuewen later chose independent deployment to avoid the same risk |
This is the only case in this group that documents the complete "governance conflict — concession — rule establishment" process, and it has direct reference value for any AI product that collects user data for model training.
6.2 Case Two: 2025-04-07 Contract Process Optimization and First-Showcase Quantity Change
Background: Nearly a year after the AI toolbox launched, the platform faced an influx of "low-quality content generated with large amounts of AI".
Plan: On April 7, 2025, the "Fanqie Contract Process Optimization Notice" was published, starting substantive review of contracted works, with a machine judging whether content is AI-generated "low-quality content"; in May 2025 the contract mechanism was again adjusted, raising the bar for contracting.
Effect:
| Indicator | Change |
|---|---|
| Daily number of male-channel first-showcase works | Once fell to below one thousand after launch |
| Long-term stable range | 1000–1500 works |
Interpretation: This is an observable governance-effect indicator — the decline in first-showcase quantity directly reflects the scale of low-quality content being blocked. Working back from "long-term stable at 1000–1500 works", this figure should have been significantly above 1500 before governance (the exact number was not disclosed [To be filled]).
Also note: this review is a machine judgment and carries a risk of misjudgment. For authors, this means that "writing like AI" has itself become a risk — this is the same problem as Sudowrite using Muse to counter the AI Slope, from two sides: the platform is penalizing the AI Slope, while the tool is fighting the AI Slope.
6.3 Case Three: 2025-09-23 Mandatory AI Declaration and Compliance Implementation
Background: The "Measures for Identifying AI-Generated Synthetic Content" came into effect on September 1, 2025; its Article 6, Paragraph 4 requires platforms to provide a labeling function and remind users to proactively declare.
Plan: On September 23, 2025, a "Use AI?" checkbox popped up in the Fanqie author dashboard, with the prompt text: "If the work you upload was synthesized/generated with AI-related tools, you must check the box truthfully".
Effect: A failure to declare truthfully may prevent passing review.
Compliance chain:
《人工智能生成合成内容标识办法》
| 2025-09-01 施行
| 第六条第四款:平台须提供标识功能并提醒用户主动声明
v
番茄作者后台"是否使用 AI"勾选项
| 2025-09-23 上线(法规施行后 22 天)
v
未如实申报 --> 可能无法通过审核 This is the most important compliance specimen in this group, and a landmark event in which the Chinese web-novel industry moved from "platform self-discipline" to "legal obligation". Cross-checking: Zongheng and Qimao ahead of Fanqie had already required authors to mark their AI usage, showing that leading platforms' compliance actions preceded legal compulsion.
6.4 Case Four: Capability Tiering — Disabling Expansion and Continuation for Guaranteed-income Works
Background: Guaranteed-income and non-guaranteed works differ in contract nature — authors of guaranteed-income works have income security, and the platform bears greater commercial risk.
Plan: AI continuation and AI expansion are only available to authors of non-guaranteed-income works (disabled for guaranteed-income works).
Design interpretation:
| Dimension | Interpretation |
|---|---|
| Tiering basis | Contract type (guaranteed / non-guaranteed) |
| Disabled scope | Only AI expansion and AI continuation — the two capabilities that "directly produce body text" |
| Not disabled | Inspiration, outline, naming, query, rewriting, custom description |
| Design logic | Risk is positively correlated with generation volume: the AI capabilities that directly produce body text carry the highest risk, so they are disabled for high-commercial-value works |
This is one of the most refined governance designs in this group. It does not impose a one-size-fits-all "ban on AI", but instead tiers by "how much each capability contributes to the final text": inspiration and outline are aids (low risk, fully open), while continuation and expansion are ghostwriting (high risk, restricted by contract type).
This tiering approach has direct reference value for AI governance in other scenarios: governance granularity should be refined to "specific capability × specific risk level", rather than a binary "used AI / did not use AI" judgment.
7. Summary
7.1 Strengths
- L6 governance is the strongest in this group and an industry benchmark: expansion/continuation disabled for guaranteed-income works + mandatory AI declaration + long-term governance of low-quality content + revocable training clause — four layers of governance in place.
- Fastest compliance response: the "Measures for Identifying AI-Generated Synthetic Content" took effect on 2025-09-01, and Fanqie launched its declaration feature on 2025-09-23, just 22 days later.
- Finest granularity of capability tiering: a two-dimensional tiering by contract type (guaranteed / non-guaranteed) × capability risk (producing body text vs. aiding).
- High credibility of official feature descriptions: the feature list comes from the official announcement page, not third-party elaboration.
- Highly systematic toolbox: 9 tools cover the entire creation process, compared with Qimao's "AI Assistant" with only 3 features.
- Writer's-block help hits the core pain point of Chinese web novels (corresponding to the industry term "writer's block").
- Tool and review belong to the same platform, rules come from a single source, and authors do not need to guess the review standards.
7.2 Limitations and Known Shortcomings
- L4 Memory and state layer is the weakest in this group: no persistent worldview library, no foreshadowing ledger, no timeline, no versioned snapshots. Long-form consistency rests entirely on the author.
- Pricing is completely opaque: the two third-party claims contradict each other, and neither can be trusted.
- Review is a machine judgment, carrying a risk of misjudgment; "writing like AI" itself becomes a risk.
- No external integration capability: limited to the official App / Workbench, with no API.
- Major governance conflicts in history: the 2024 "AI Training Supplementary Agreement" incident led to collective halts in updates by authors.
- Contracting bar keeps rising: tightened twice in 2025-04 and 2025-05, squeezing authors' room to survive.
- No structure templates: compared with Sudowrite's 4 outline templates, Fanqie offers only the single "Generate outline" capability.
7.3 Applicable Boundaries
| Applicable | Not Applicable |
|---|---|
| Chinese web-novel creation and submission within the Fanqie platform | Submitting to other platforms (the tools are not portable) |
| Single-chapter output improvement on a daily-update rhythm | Million-character long-form works needing long-range consistency (L4 insufficient) |
| Plot breakthroughs when stuck on writer's block | Setting-intensive works that need worldview/character persistence |
| Inspiration and outlines in the book-opening stage | Engineering workflows requiring external tool integration |
| Expansion/continuation needs of authors of non-guaranteed-income works | Expansion/continuation by authors of guaranteed-income works (disabled) |
7.4 Selection Recommendations
- Must-choose scenario: you submit your work on the Fanqie platform. In this case the official AI toolbox is the only choice with the same source as the review standards, and you must use its declaration process.
- Capability combination recommendation: Fanqie's L4 is blank, so long-form authors should build their own external state layer — you can refer to the Bible/State/Timeline four-directory structure of
05-claude-fiction.md, or the project constitution of Lingxie Creation described in07-chinese-webnovel-ai.md, maintaining worldview and foreshadowing ledger outside Fanqie. - Compliance mandate reminder: since 2025-09-01, AI labeling is a legal obligation. When content generated by any third-party AI tool (NovelAI, Sudowrite, Claude, etc.) is published on Fanqie, you must truthfully check the "Use AI?" box. These tools themselves do not provide AIGC labeling capability; the obligation rests entirely on the author.
- Special note for authors of guaranteed-income works: AI expansion and AI continuation are disabled for guaranteed-income works. If your work is under a guaranteed-income contract, avoid using equivalent capabilities on any platform beyond the official tools, so as not to conflict with the contract terms.
Information Gap Declaration
- The pricing of Fanqie's AI writing tool: the official announcement did not disclose a standalone price; the third-party claims of "19 CNY/month bundled with membership" and "completely free" contradict each other, neither can be trusted, and both are marked
[To be filled]. - Persistent worldview / character library: no official description found; treated as "none" and marked
[To be filled]. - The three signals of text-fingerprint technology (abnormal word frequency, monotonous sentence structure, flat emotional fluctuation): from a Toutiao self-media source, not confirmed by the official side, marked
[To be verified], described only as a phenomenon and never cited as fact. - The "three contract opportunities" rule: found only in self-media sources, marked
[To be verified]. - The number of first-showcase works before governance: not disclosed, so the decrease cannot be computed, marked
[To be filled]. - "Four usages safe within the rule framework" (AI builds the framework and the author fills in the flesh / AI names, looks up materials, and expands inspiration / AI pre-reviews plot holes and optimizes pacing / checking "Use AI" to declare truthfully): from self-media sources, marked
[To be verified], not cited as fact. - Third-party descriptions of "pacing tips" and "satisfaction-beat advice": the research report explicitly determined these to be elaboration, not to be cited as fact, and this article does not adopt them.
- Whether the AI declaration is written into the AIGC metadata fields: no technical-implementation description found, marked
[To be filled]. - Fanqie's underlying AI model: the official side only states "based on large language models" without disclosing the specific model, marked
[To be filled].
8. References
- Fanqie Novel official announcement "AI Writing Tool Feature Launch Notice" — Fanqie Novel, 2024. https://fanqienovel.com/writer/zone/article/7327136545129906238
- Haike Caijing "Fanqie Novel's AI Problem" (Sina Finance) — Haike Caijing, 2025. https://finance.sina.com.cn/search/2025-10-09/doc-infthsqh9655363.shtml
- Sohu Culture "2024-2025 Biennial List, Preface One: The AI Era, the 'Greater Literary View', and the Gentleness of the World's Dark Side" — Sohu Culture, 2025. https://cul.sohu.com/a/1058758339_121124749
- Zhongxin Jingwei "Creative Effort Becomes AI Nourishment? Web-novel authors 'rise up', Fanqie Novel rushes to clarify" — Zhongxin Jingwei, 2025. https://www.jwview.com/jingwei/html/07-26/601732.shtml
- Toutiao "Fanqie's 2026 AI New Policy: Pure AI generation results in a permanent ban, but using AI this way actually earns extra points" — Toutiao, 2026. https://m.toutiao.com/article/7626281118299357747
- Toutiao "2026 AI Tool Recommendations Suited to Fanqie Novel Authors" — Toutiao, 2026. https://www.toutiao.com/article/7654053329475043846
- China Youth Daily "'Miaobi Tongjian' and 'Manju Assistant' Released, AI Empowers Web-novel Creation and IP Adaptation" (Tencent News) — China Youth Daily, 2025. https://new.qq.com/rain/a/20251017A08J6J00
- Baidu Baike "Writer Assistant Miaobi Edition" — Baidu Baike. https://baike.baidu.com/item/%E4%BD%9C%E5%AE%B6%E5%8A%A9%E6%89%8B%E5%A6%99%E7%AC%94%E7%89%88/63227250
- HackerNoon "Claude Book: A Multi-Agent Framework for Writing Novels with Claude Code" — HackerNoon. https://hackernoon.com/claude-book-a-multi-agent-framework-for-writing-novels-with-claude-code
- Sudowrite official blog "How Sudowrite Works: Story Bible, Muse, and the Tools" — Sudowrite. https://sudowrite.com/blog/how-sudowrite-works
- Meipian "How Beginners Start Writing Web Novels" — Meipian. https://www.meipian.cn/5gn73n9w
- Toutiao "Notes on Novel-Writing Techniques: From Beginner to Advanced" — Toutiao. https://m.toutiao.com/article/7666250379276927531
- Geek Park "Can AI Write 'Joy of Life'?" — Geek Park. https://so.html5.qq.com/page/real/search_news?docid=70000021_10168f9fb6122152