Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 17 additions & 12 deletions docs/development/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,38 +16,42 @@ not need these documents to start LoopX.
3. Follow the [Developer Book](/loopx/docs/book/) for the curated external
learning path from control-plane foundations to project onboarding and
developer contributions.
4. Follow the [control-plane developer course](control-plane-course/README.md)
4. Read the [LoopX project code tour](project-code-tour.zh-CN.md) for a Chinese,
code-linked overview of the architecture and one complete execution path.
5. Follow the [control-plane developer course](control-plane-course/README.md)
for an eleven-lecture, code-led path through the real CLI, state machine, and
layered quality gates.
5. Read [Testing and quality](testing-and-quality.md) before changing agent-facing
6. Read [Testing and quality](testing-and-quality.md) before changing agent-facing
output, scheduler decisions, todo/gate semantics, onboarding, or release
promotion.
6. Use [What counts as a good smoke](good-smokes.md) before adding, retaining,
7. Use [What counts as a good smoke](good-smokes.md) before adding, retaining,
or consolidating a public smoke.
7. Use [Architecture](../architecture.md) and the
8. Use [Architecture](../architecture.md) and the
[core control-plane graphs](../product/core-control-plane/README.md) to find
the bounded context that owns the behavior.
8. Check [Public/private boundaries](../public-private-boundary.md) before adding
9. Check [Public/private boundaries](../public-private-boundary.md) before adding
fixtures, examples, evidence, or provider-backed evaluation.
9. Follow the [documentation layout policy](documentation-layout.md) before
10. Follow the [documentation layout policy](documentation-layout.md) before
adding or moving public documentation.

1. 先阅读[贡献指南](https://github.com/huangruiteng/loopx/blob/main/CONTRIBUTING.md),了解仓库边界和 PR 检查项。
2. 阅读[当前技术方向](../project/technical-directions.zh-CN.md),选择活跃计划、了解
成熟度并找到对应 tracker。
3. 按顺序阅读[开发者手册](/loopx/docs/book/),从控制面基础到项目接入和开发者贡献。
4. 按顺序学习[控制面开发者 11 讲](control-plane-course/README.md),沿真实 CLI、
4. 先阅读[LoopX 项目代码导读](project-code-tour.zh-CN.md),通过源码链接了解架构和
一次完整执行链路。
5. 按顺序学习[控制面开发者 11 讲](control-plane-course/README.md),沿真实 CLI、
状态机、核心函数和分层质量门禁建立代码心智模型。
5. 修改 agent-facing 输出、调度决策、todo/gate 语义、新用户接入或发布流程前,
6. 修改 agent-facing 输出、调度决策、todo/gate 语义、新用户接入或发布流程前,
阅读[测试与质量体系](testing-and-quality.md)。
6. 新增、保留或合并公开 smoke 前,阅读
7. 新增、保留或合并公开 smoke 前,阅读
[什么是好的 Smoke](good-smokes.md)。
7. 通过[架构文档](../architecture.md)和
8. 通过[架构文档](../architecture.md)和
[控制面核心图](../product/core-control-plane/README.md)定位真正拥有该行为的
bounded context。
8. 添加 fixture、示例、证据或模型测试前,检查
9. 添加 fixture、示例、证据或模型测试前,检查
[公开/私有边界](../public-private-boundary.md)。
9. 新增或移动公开文档前,遵循
10. 新增或移动公开文档前,遵循
[文档布局规则](documentation-layout.md)。

## Core References / 核心参考
Expand All @@ -56,6 +60,7 @@ not need these documents to start LoopX.
| --- | --- |
| Current strategic programs / 当前战略方向 | [Technical directions](../project/technical-directions.md) · [中文](../project/technical-directions.zh-CN.md) |
| Curated learning path / 开发者学习路径 | [Developer Book](/loopx/docs/book/) |
| Project architecture tour / 项目架构导读 | [LoopX project code tour](project-code-tour.zh-CN.md) |
| Control-plane code reading / 控制面代码领读 | [Eleven-lecture developer course](control-plane-course/README.md) |
| Quality layers and commands / 质量分层与命令 | [Testing and quality](testing-and-quality.md) |
| Durable smoke design and cleanup / 稳定 Smoke 的设计与清理 | [What counts as a good smoke](good-smokes.md) |
Expand Down
Loading