# AI 原生研究物迭代與可驗證升版方法論系列

Series status: 8-paper v0.1 closure package
Date: 2026-09-16

## Papers

### 01 — 當生成變得廉價：AI 原生學術照護、研究物生命週期與隱性整合債

- File: `AI_Native_Scholarly_Stewardship_Series_01_v0.1_2026-09-16.md`
- SHA-256: `3d17a79bcf8f66877dd57512835901440725331d7bddd8361fbb719fa83f1dd6`

### 02 — 研究物不是版本號：Research Object Identity、Version、Edition 與 Lineage 的分離

- File: `AI_Native_Research_Object_Revision_Series_02_v0.1_2026-09-16.md`
- SHA-256: `8dcc7bf1cbc21f30e49df941c4a502003aab4f0bba439e9c5c0868b4740e2c8f`

### 03 — 證據不是權威印章：Claim、Evidence、Validation、Truth 與 Confidence 的型別分離

- File: `AI_Native_Research_Object_Revision_Series_03_v0.1_2026-09-16.md`
- SHA-256: `c9323d28b3eb0626a599d3453ef04a02d26b64f22bab81ad75f5bf38261c7418`

### 04 — 從證據清單到證據關係圖：Evidence–Claim Matching、Scope Binding 與認識論權威替代防護

- File: `AI_Native_Research_Object_Revision_Series_04_v0.1_2026-09-16.md`
- SHA-256: `dac1d4019ce8cc6dc0c386f40e496e970ba723a497b82c74b2d7f3f9307616df`

### 05 — 理論不只用來判真：從 Capability Extraction 到 Artifact 與 Observed Behavior 的操作化鏈

- File: `AI_Native_Research_Object_Revision_Series_05_v0.1_2026-09-16.md`
- SHA-256: `83fb7e63e984c9037716f7166e9040dfab28e53fde422c8201140f2d72251a1c`

### 06 — 發布時間不是生成時間：Temporal Provenance、Batch Ingest 與研究形成時間的分離

- File: `AI_Native_Research_Object_Revision_Series_06_v0.1_2026-09-16.md`
- SHA-256: `5f909dd72e5b50a8bc138fbc58ac63e6c6891effb5c8ed2345e70ada4b044129`

### 07 — 我們為什麼這樣理解它：Epistemic Provenance、Assessment Revision 與研究物理解路徑

- File: `AI_Native_Research_Object_Revision_Series_07_v0.1_2026-09-16.md`
- SHA-256: `ce77a19ff73fca6c08adc5dee8042feebed8524b3f06574b2f080f9596e50423`

### 08 — 從論文集合到可治理研究空間：Global Scholarly Closure、Corpus Governance 與 AI 原生研究基礎設施

- File: `AI_Native_Research_Object_Revision_Series_08_v0.1_2026-09-16.md`
- SHA-256: `52c2c10021bacc32f6d162171e0ed00ce0a9edc941547ec6058400e2009bfddd`

## Series closure

$$
\boxed{
\text{Global Mapping}
\rightarrow
\text{Local Revision}
\rightarrow
\text{Boundary Reconciliation}
\rightarrow
\text{Global Scholarly Closure}
}
$$

All formal source files are UTF-8 canonical Markdown and were validated before packaging.