文档结构与命名规范(Docs Structure & Naming)#
本文档定义当前版本的文档集结构与命名规范,并说明分类原则、状态规则与未来扩展预留目录。
1. 分类原则#
按 Intent(功能)分层:Guides / Reference / Architecture / Decisions(ADR) / Reports / Policy / Governance / Plans / Archive / Templates / Assets
按 Cadence(更新频率)治理:
高频:Guides(接口/目录结构变更必须同步)
中频:Reference(字段/校验变更必须同步)
低频:Architecture/Decisions/Reports(多为追加或小修)
单一权威来源:字段字典与校验规则仅在
/docs/reference/*维护;其他文档只引用不复制。多入口策略:同一主题只保留一个主文档,避免多入口导致内容分叉。
现行与归档边界:active 内容仅在非 archive 目录维护,
archive/*只保留历史快照。规格落点策略:当前执行型规格统一在
/docs/plans/*;/docs/archive/specs/*仅历史归档。
2. Sphinx 索引映射 (Index Mapping)#
本项目使用 Sphinx + MyST Parser 构建文档,物理文件 (.md) 与逻辑索引 (.rst) 存在严格映射关系:
物理层: 文档实际存储在
docs/根目录下(如docs/guides/cli.md)。逻辑层: 构建配置位于
docs/source/,其中.rst文件定义目录树 (toctree)。更新规则:
新增文档: 必须在
docs/source/index.rst或对应子索引(如docs/source/guides/index.rst)中添加文件名(不含扩展名)。移动/归档: 必须从原
.rst中移除引用,若归档目录有索引文件,需同步更新。删除文档: 必须从所有引用它的
.rst文件中移除条目,防止构建报错。
3. 命名规范#
目录名:全小写,短语用
-连接(如guides/testing)。主文档:语义清晰、稳定(如
quickstart.md、config.rst)。审计/计划类报告:使用
YYYY-MM-DD-<topic>.md(例如2026-02-19-doc-accuracy-audit.md)。禁止在仓库内保留旧入口跳转页;旧路径兼容性应通过站点侧 301 或发布说明解决。
3. 状态规则#
每篇 active 文档包含
Status/Audience/Last-Updated元信息。Status使用:active(现行)、draft(草稿)、archived(历史/仅供参考)。
4. 文档结构树#
树状图 PNG:/docs/img/docs-structure-tree.png
/docs
├── README.md
├── _templates
│ ├── page.md
│ ├── adr.md
│ └── report.md
├── guides
│ ├── README.md
│ ├── installation.md
│ ├── quickstart.md
│ ├── cli.md
│ ├── configuration.md
│ ├── slurm.md
│ ├── troubleshooting.md
│ ├── developer-guide.md
│ └── testing
│ ├── README.md
│ ├── integration-slurm.md
│ └── multi-datapool-artifacts.md
├── reference
│ ├── README.md
│ └── validation.md
├── architecture
│ ├── README.md
│ ├── design-report.md
│ └── decisions
│ └── 2026-02-04-deepmd-dependency.md
├── reports
│ └── README.md
├── policy
│ ├── README.md
│ ├── maintenance.md
│ ├── quality.md
│ ├── contributing.md
│ └── docs-structure.md
├── governance
│ ├── README.md
│ ├── reviews
│ │ ├── README.md
│ │ └── DocReview_20260309_v1.0.md
│ ├── plans
│ │ ├── 2026-02-18-doc-system-planning.md
│ │ ├── 2026-03-03-codebase-remediation-breakdown.md
│ │ └── 2026-03-09-doc-system-maintenance-execution-detail.md
│ ├── audits (Archived to docs/archive/governance/audits)
│ ├── traceability
│ │ ├── feature-doc-matrix.md
│ │ └── workflow-contract-test-matrix.md
│ ├── inventory
│ │ └── docs-catalog.md
│ └── tools
│ └── link-normalization.json
├── plans
│ ├── README.md
│ ├── iteration_plan_v0.6.md
│ ├── integration-slurm-plan.md
│ ├── release_note_v0.6.0.md
│ ├── v0.6.0-doc-governance-execution.md
│ ├── v0.6-acceptance-record.md
│ ├── v0.6-phase0-contract-and-risk.md
│ ├── labeling_test_plan.md
│ └── labeling_unit_test_design.md
└── archive
├── README.md
├── Code_Review_Report_v2.7.1.md
├── Variable_Review_Report.md
├── governance
│ ├── audits
│ │ ├── 2026-02-18-docs-selfcheck.md
│ │ ├── 2026-02-19-link-check.md
│ │ ├── 2026-02-19-doc-accuracy-audit.md
│ │ └── 2026-02-19-docs-review-report.md
│ ├── 2026-02-18-docs-completion-list.md
│ └── 2026-02-19-readme-coverage.md
├── specs
│ ├── v0.2
│ │ └── visualization_decoupling_plan.md
│ └── v0.5.3
│ ├── tasks.md
│ └── checklist.md
├── refactoring
│ └── ... (Historical plans)
├── reports
│ ├── README.md
│ ├── 2026-02-22-integration-test-optimization.md
│ ├── 2026-02-22-integration-test-output-verification.md
│ ├── 2026-02-22-integration-test-review.md
│ ├── 2026-02-22-unit-test-report.md
│ ├── 2026-02-27-Code-Audit_Report.md
│ └── modulo-hypothesis.md
└── v0.6.0
└── plans
├── integration-slurm-plan.md
├── labeling_test_plan.md
├── release_note_v0.6.0.md
├── v0.6-acceptance-record.md
├── iteration_plan_v0.6.md
├── labeling_unit_test_design.md
├── v0.6.0-doc-governance-execution.md
└── v0.6-phase0-contract-and-risk.md
5. 未来扩展预留目录#
/docs/glossary/:术语表(DataPool/System/Descriptor 等)/docs/migrations/:迁移指南(字段重命名、弃用策略、破坏性变更)/docs/changelog/:release notes 与兼容性说明