Tianyi Cui
ba3125234a
The folder is becoming the home of one-doc-per-subsystem pages (intro + data structures + cordis services/events), so the name must describe the whole contract, not just the type-vocabulary third of it. Mechanical rename rebuilt on current master: every inbound Markdown link, generator constant, website route, type-equiv manifest path, and spec expectation moves together; the zh sides of the notes whose prose names the folder are aligned (子系统) in the same change; touched bilingual pairs re-recorded; translation-prompt snapshot re-recorded (its example embeds development.md). Historical Agent Note slugs keep their dated filenames.
1.6 KiB
1.6 KiB
Documentation Graph Index
These diagrams are the relationship layer above the generated catalogs. Use them to navigate package topology, capability seams, event flow, model-facing tools, app composition, and runtime lifecycle paths. Exact signatures and type shapes still live in the generated events / services catalogs, tool-catalog.md, and subsystems/.
The process decision behind this index is recorded in the documentation graph Agent Note.
| Graph | Mode |
|---|---|
| module dependency graph | generated |
| tool schema catalog and package map | generated |
| capability seams and core services | hybrid generated |
| dsh shared base composition | hybrid generated |
| headless-agent app composition | hybrid generated |
| acp-agent app composition | hybrid generated |
| event producer/consumer matrix | hybrid generated |
| agent turn and step lifecycle | curated |
| tool execution pipeline | curated |
Regenerate with pnpm run gen-doc-graphs; verify freshness with pnpm run verify-doc-graphs.
Maintenance mode: mixed: each linked page declares generated, hybrid, or curated mode.