Project Overview
This page expands the homepage into a concise narrative: why the project matters, how the system is organized, and how to start without getting lost in the catalog.
Why adopt this structure
The long-term value is not "132+ .cursorrules files" by itself. It is the ability to turn repeated engineering judgment into a shared system that teams can review and reuse.
How the site is organized
| Layer | Main area | Purpose |
|---|---|---|
| Whitepaper | docs/en/reference/* | Explain the investment case and reading order |
| Architecture | docs/en/architecture/* | Explain structure, boundaries, and information flow |
| Playbook | docs/en/guides/* | Translate the shell into phased action |
| Evidence | rules/ and docs/en/rules/* | Provide rule samples, composition guidance, and proof |
The English surface stays shorter than Chinese, but it follows the same IA so readers can move between them without relearning the structure.
How to begin
- Read the Decision Brief to validate the value case.
- Continue to the Site Blueprint and Information Graph.
- Use the Adoption Path and Role Paths to decide rollout steps.
- Enter the Rules Evidence Library only after that framing is clear.