织文NovelWeave长篇与短篇工作台long & short form studio
写到第四十章，还能知道谁在第几章断了左臂。 A long-form studio that still knows who lost an arm back in chapter five.
把设定变成可校验的结构化状态，用机器规则查前后矛盾 —— 而不是靠你记住自己写过什么。 Settings become verifiable structured state, and machine rules catch the contradictions — instead of relying on your memory.
它解决什么What it fixes
长篇写崩，很少是因为没灵感，多半是因为前后对不上：死人又开口说话、伏笔埋了没收、上章断了臂的主角这章挥拳。人脑记不住两百章的设定；把全文一股脑塞给模型也不行 —— 上下文有上限，而且塞得越满越钝。 Long fiction rarely fails for lack of ideas; it fails because the text stops agreeing with itself — the dead speak again, a planted thread is never paid off, the protagonist who lost an arm throws a punch. Nobody remembers two hundred chapters of settings, and dumping the whole manuscript into a model doesn't work either: context is finite, and the more you cram, the duller it gets.
织文的做法是把设定落成可校验的结构化状态：角色卡、世界规则、伏笔登记表、时间线、每章的状态矩阵。写作时不喂原文，只喂一份有字节预算的派生上下文；超出预算裁掉了哪一节，会如实报出来，绝不静默丢。检查由 13 条机器规则完成，带稳定指纹、严重度与退出码，能直接进 CI。 NovelWeave turns settings into verifiable structured state: character cards, world rules, a promise ledger, a timeline, and a per-chapter state matrix. When writing, it feeds the model a derived context with a byte budget rather than raw prose — and if a section has to be dropped, it says so instead of silently vanishing. The checks run as 13 machine rules with stable fingerprints, severities and exit codes, so they belong in CI.
一次检查长什么样What a check looks like
每条诊断都带原文引证与位置，点一下跳到那一章那一句。误报有控制：「明长老的旧伤」这种领属提及不算本人在行动；不同叙事线的时间永不互相比。 Every diagnostic carries a quote and an offset you can jump to. False positives are deliberately bounded: a possessive mention ("Elder Ming's old wound") doesn't count as the man acting, and timelines on different threads are never compared against each other.
能力Capabilities
.novelweave/ 目录存在：正文是 Markdown，状态是 JSON，可进 git。网页与命令行 agent 改同一份，导入时逐条三方比较，两边都改过的不自动覆盖。The web app and CLI agents edit the same tree; a three-way merge never auto-overwrites a record both sides touched.写作的循环The writing loop
- 起书 —— 新建作品，或用
adopt把已有散稿一键建档。设定落成角色卡、世界条目、伏笔登记表、状态矩阵，不再散落在几百个文档里。Start a book — create one, oradoptexisting drafts. Settings become character cards, world entries, a promise ledger and a state matrix. - 配 Key（可选，但推荐） —— 设置页选服务商，免费档就能跑：智谱 GLM-Flash、硅基流动免费模型、火山豆包日更额度（yu.ai/key.html 收录了各家免费额度）。Key 只存本机。Bring a key (optional) — free tiers are enough; the key never leaves your browser.
- 逐章写作 —— 续写自动注入：出场角色、状态快照、未结线索、前情摘要、触发的世界设定、硬禁令（死者名单 / 到期伏笔）、以及你自己定稿的文风样例。生成完先过机器规则自检一轮，修订稿与诊断一起交给你。Write chapter by chapter — continuation injects cast, state, open promises, recap, world lore, hard bans and your own style samples; the draft passes a machine self-check before reaching you.
- 落账 —— 「总结本章」一键写回摘要（不写回就等于录了没人读的事实）；谁受了伤、谁知道了什么，走提案确认进状态矩阵与伏笔表。Settle the ledger — chapter summaries feed future context; state changes go through proposals into the matrix and ledger.
- 校验与带走 —— 连续性面板随时体检，诊断带引证可跳转；导出
.novelweave/目录，命令行 agent 与网页读写同一本书。Verify & take it with you — the continuity panel audits on demand; export the tree and CLI agents share the same book.
它不做什么What it won't do
- 不判断文笔，不承诺"去 AI 痕迹"。它会主动把这一项交接给文体类工具并记录结论，但不自己评价文字好坏 —— 那是另一类专业能力，混在一起做必然两头都做浅。No prose judging, no "de-AI" promise. It hands that off to a style tool and records the outcome, but never rates the writing itself.
- 不从零批量生成整本书。没有"一键 50 章"。No one-click 50-chapter book.
- 不替你决定设定。任何状态变更先提案，作者点头才写入；AI 可以建议，不能静默改写既定事实。No silent edits to your canon. State changes are proposed first and applied only on your say-so.
- 不发明第二套格式。只认
.novelweave/，字段有 schema，非法结构先停。Only one file format. Schema-validated; invalid structure halts the run.
这一节是刻意写的。同类工具最常见的失败方式，是声称自己什么都能做。 This section is deliberate. The most common failure in this category of tool is claiming it does everything.
上手Getting started
- 网页直接用 —— 点上面「进入织文」，创建作品即可写作。不配 API Key 也有一半功能是可用的：结构化状态、状态矩阵、连续性检查全在本地浏览器里跑；配了 Key（任意 OpenAI 兼容接口）才有续写、润色与总结。Just open it. Half of it works with no API key at all — the state matrix and the continuity checks run entirely in your browser.
- 已有几十章稿子 —— 用
adopt建档：草稿目录只读，章号不会被平移，判不出的章号它会拒绝而不是猜。Already have drafts?adoptthem: your files stay read-only, existing chapter numbers never shift, and anything unrecognisable is refused rather than guessed. - 让命令行 agent 帮你写 —— 仓库自带两个技能（写作编排 + 只读连续性检查），一条安装脚本分发到 Claude Code · Codex · Cursor · Qoder · OpenClaw · Hermes · WorkBuddy。Drive it from an agent. Two bundled skills, one installer, seven agent runtimes.
- 定期导出备份 —— 数据在浏览器里，清站点数据会一起丢。设置页有单文件快照与
.novelweave/目录两种导出。Back up regularly. Browser storage is the only store; export a snapshot or a directory tree.
浏览器要求：需要支持 IndexedDB 与现代 ES 的浏览器；.novelweave/ 目录读写依赖 File System Access API，不支持时用单文件 JSON 备份走同一套合并逻辑。
Requires IndexedDB and modern ES; directory read/write uses the File System Access API, with a single-file JSON fallback that runs the same merge logic.
终态形态The endgame
从一句话的想法，到百万字的长篇 —— 每一层设定可校验，每一段生成有安全网，每一次覆盖可回退。作者只做决定，织文负责不忘。 From a one-line idea to a million-word novel — every layer of settings verifiable, every generation netted, every overwrite reversible. You decide; NovelWeave remembers.
conflicts/，但要人手工合）、版本历史的并排 diff、文体台账进 Web 界面。A conflict-resolution UI for dual writes — records changed on both sides already land in conflicts/, but merging them is still manual — plus side-by-side diff for revision history, and the prose ledger surfacing in the web app.终态里没有"一键生成五十万字"这一项。织文认定：写作工具的责任不是替你产出字数，而是保证你产出的每一章，和第一章仍然站在同一个世界里。 The endgame deliberately excludes "one-click 500k words". A writing tool's job is not to produce word count — it is to keep chapter fifty living in the same world as chapter one.