署名：角色声明，不排座次

传统学术用第一作者和通讯作者分权责。本博客不沿袭这套——不是因为传统不对，是因为我们的协作方式用不着那套分类。这里选一套更细粒度的写法。

当一篇文章的作者包括人类和 AI 时，写清楚每个人做了什么就够了。比如 TF-001：人类提供方向定义、术语校正、架构立场校准；AI 提供初稿撰写、代码引用、文献检索。不需要区分"谁排第一"——只需要知道谁承担了什么。

Attribution: Roles, Not Rankings

Traditional academic publishing uses first author and corresponding author to divide credit and responsibility. This blog doesn’t follow that convention — not because it’s wrong, but because our collaboration model doesn’t need it. We chose a more granular approach.

When an article’s authors include both a human and an AI, it’s enough to state what each did. Example from TF-001: the human provided direction, terminology correction, and architecture stance calibration; the AI provided first-draft writing, code references, and literature search. No need to distinguish “who is first” — just know who bore what.

2. Markdown 头部元数据

在每篇文章的 Front Matter 中声明两个字段：

author: nio (Houming818) & opencode
role: >-
  nio: 方向定义、内容审查、术语校正；
  opencode: 初稿撰写、代码引用、编辑执行
review: >-
  由 nio 于 2026-05-17 至 05-19 多轮审阅。

role 替代"第一作者/通讯作者"——不排座次，只声明贡献类型。review 记录审阅链条。

2. Front Matter Metadata

Two fields in every article’s YAML header:

author: nio (Houming818) & opencode
role: >-
  nio: direction, review, terminology correction;
  opencode: draft, code references, editorial
review: >-
  Reviewed by nio across multiple rounds (2026-05-17 to 05-19).

role replaces “first author / corresponding author” — no ranking, just a statement of contribution type. review records the review chain.

3. Git 内容溯源

git log --follow -- <file> 可以还原全文的修改历史：谁、什么时候、改了哪一行。传统同行评审做不到这个粒度。

3. Git-Based Traceability

git log --follow -- <file> reconstructs the full revision history: who, when, which line. Traditional peer review cannot achieve this granularity.

4. RSS 扩展命名空间

在 RSS 2.0 基础上定义 ap 命名空间（xmlns:ap="https://www.grepcode.cn/ns/ai-papers"），每个 <item> 增加两个子元素：

<ap:role>nio: 方向定义、内容审查; opencode: 初稿撰写、编辑执行</ap:role>
<ap:review>由 nio 于 2026-05-17 至 05-19 多轮审阅...</ap:review>

外加 ShowFullTextinRSS = true，全文送达而非摘要——学术内容必须完整可读。

4. RSS Extension Namespace

An ap namespace (xmlns:ap="https://www.grepcode.cn/ns/ai-papers") is defined on top of RSS 2.0. Each <item> gains two child elements:

<ap:role>nio: direction, review; opencode: draft, editorial</ap:role>
<ap:review>Reviewed by nio, 2026-05-17 to 05-19...</ap:review>

Additionally, ShowFullTextinRSS = true — full text delivery, not just summaries.

5. 署名

署名即声明版权归属和许可条件。不隐含任何担保或责任——与 GPLv3 的 NO WARRANTY 一致。

5. Attribution

Attribution declares copyright ownership and license terms. It implies no warranty or liability — consistent with GPLv3’s NO WARRANTY clause.