nature-paper-to-patent

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Paper to Chinese Patent

论文转中国发明专利

Use this file as the router for the patent-drafting workflow. Do not draft the application directly from the paper abstract or contribution list.

将本文件用作专利起草工作流的路由工具。请勿直接根据论文摘要或贡献列表起草申请文件。

1. Load the workflow

1. 加载工作流

Read

manifest.yaml

, then read every file under

always_load

Detect these axes from the user's files and request:

```
source_format
```
: selectable PDF, scanned PDF, pasted text, or mixed project;
```
task_mode
```
: full draft, claim set, disclosure analysis, or paper-patent audit;
```
invention_type
```
: algorithm/software, apparatus/system, process/material, or mixed.

State the detected values in one short line. Load only the matching fragments declared in the manifest. Load detailed references only when their condition applies.

读取

manifest.yaml

，然后读取

always_load

下的所有文件。

从用户的文件和请求中检测以下维度：

```
source_format
```
：可选值为PDF、扫描版PDF、粘贴文本或混合项目；
```
task_mode
```
：完整草稿、权利要求集、披露分析或论文-专利审核；
```
invention_type
```
：算法/软件、装置/系统、工艺/材料或混合类型。

用简短的一句话说明检测到的取值。仅加载清单中声明的匹配片段。仅在条件适用时加载详细参考资料。

2. Preserve source grounding

2. 保留来源溯源

Create stable source IDs before drafting:

```
P001...
```
for paper text blocks;
```
E001...
```
for equations;
```
F001...
```
for source figures;
```
C001...
```
for source-code or supplementary evidence.

Every material feature in a formal claim must map to one or more source IDs. Use only

explicit

inherent

needs-confirmation

, or

unsupported

as support states. Exclude

unsupported

features from formal claims.

Never infer inventorship, ownership, unpublished implementation details, publication dates, prior-art conclusions, or legal sufficiency. Use

[TO CONFIRM: specific question]

outside formal claims when facts are missing.

在起草前创建稳定的来源ID：

```
P001...
```
用于论文文本块；
```
E001...
```
用于公式；
```
F001...
```
用于来源图表；
```
C001...
```
用于源代码或补充证据。

正式权利要求中的每个实质性特征必须映射到一个或多个来源ID。仅使用

explicit

（明确支撑）、

inherent

（固有支撑）、

needs-confirmation

（需确认）或

unsupported

（无支撑）作为支撑状态。将

unsupported

特征排除在正式权利要求之外。

切勿推断发明人身份、所有权、未公开的实现细节、发布日期、现有技术结论或法律充分性。当事实缺失时，在正式权利要求外使用

[待确认：具体问题]

标注。

3. Draft through stage gates

3. 通过阶段门完成起草

Complete the stages in

static/core/workflow.md

in order. Persist the intermediate artifacts specified there. Do not move to formal claims until the source map, terminology ledger, inventories, evidence ledger, and invention concept pass their gates.

For a full application, draft claims first, then align the specification, figures, embodiments, and abstract to the claim terminology and step order.

按

static/core/workflow.md

中的顺序完成各个阶段。保留其中指定的中间产物。在来源映射表、术语台账、清单、证据台账和发明概念通过阶段门审核前，不得进入正式权利要求的起草环节。

对于完整申请，先起草权利要求书，再使说明书、图表、实施例和摘要与权利要求的术语和步骤顺序保持一致。

4. Produce Chinese formal documents

4. 生成中文正式文件

Agent-facing analysis may use the user's preferred language. Produce formal Chinese patent deliverables in Chinese:

权利要求书;
说明书;
说明书摘要;
摘要附图;
figure labels and descriptions.

For algorithmic inventions, retain source-supported core formulas, define every symbol, explain each formula's technical operation, and render formulas as native editable Office Math in DOCX. Do not use plain LaTeX strings as the visible formula.

Generate the main flowchart from the ordered steps of the principal method claim. Its final node must name the concrete domain output, such as a defect detection result, target pose, state estimate, or control instruction. Reuse the same main figure as the abstract figure and a specification figure.

面向Agent的分析可使用用户偏好的语言。生成正式的中文专利交付文件：

权利要求书；
说明书；
说明书摘要；
摘要附图；
图表标签及说明。

对于算法类发明，保留有来源支撑的核心公式，定义每个符号，解释每个公式的技术操作，并在DOCX中以原生可编辑的Office Math格式呈现公式。不得将纯LaTeX字符串作为可见公式。

根据主要方法权利要求的有序步骤生成主流程图。其最终节点必须命名具体的领域输出，例如缺陷检测结果、目标姿态、状态估计或控制指令。将同一主图表复用为摘要附图和说明书图表。

5. Validate before delivery

5. 交付前验证

Populate the structured draft described in

references/draft-schema.md

, then run:

bash

python scripts/validate_patent_draft.py draft.json
python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patent

Resolve all validation

ERROR

findings. Review every

WARNING

against the source. Label the result

incomplete draft

when a required quality threshold in

static/core/output-contract.md

is not met.

The generated package is a drafting aid for inventor and patent-professional review, not a patentability opinion, infringement opinion, or filing guarantee.

填充

references/draft-schema.md

中描述的结构化草稿，然后运行：

bash

python scripts/validate_patent_draft.py draft.json
python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patent

解决所有验证发现的

ERROR

问题。对照来源审核每个

WARNING

。当未达到

static/core/output-contract.md

中的要求质量阈值时，将结果标记为“未完成草稿”。

生成的包仅作为供发明人和专利专业人员审核的起草辅助工具，不构成专利性意见、侵权意见或提交担保。