2.3 KiB
2.3 KiB
Module Map
Source Layout
| Path | Responsibility | Owner Notes |
|---|---|---|
agent设计规范/ |
Business prompt, Skills, templates, registry, business pages, fixtures | Update business entry and Skill before downstream contracts when user fields change |
schemas/ |
Current parse, execution, and ERP schemas | Historical schemas belong in archive/ |
mappings/ |
Current ERP fields, lifecycle, and extension-version mapping | Must stay synchronized with execution code |
control-plane/ |
TypeScript control plane, migrations, 19-route parser registry, external Webhook client, and tests | Never hand-edit .build/ output |
LianSyn-platform/ |
Operator UI and external Agent parsing adapter | No task output or release packages |
chrome-extension/ |
Current ERP extension source | Version bump and release synchronization required for code changes |
tools/ |
Reusable builders, tests, diagnostics, and controlled write helpers | Tool outputs do not stay here |
infra/ |
Deployment, backup, restore, and gateway configuration | No local secrets or database backups |
.project-docs/ |
Durable task and canonical project memory | Governed by worktree ownership and Integration Gate |
dist/ |
Current versioned delivery artifacts | Defined by release-manifest.json |
archive/ |
Immutable dated history and evidence | Read-only authority boundary |
Dependency Direction
- Business input/AgentBus → route orchestration → AI or Program parser → unified operation → control plane → Chrome extension → ERP.
- Business source documentation → Schema/mapping/implementation/tests → versioned artifacts; generated artifacts never become editable sources.
- Task-scoped
.project-docsrecords propose durable changes; canonical documents consume them only through Integration Gate.
Risky Or Sensitive Areas
- ERP write boundaries and reconciliation after uncertain responses.
- Multi-parent shared-child enumeration and sequential write-stop boundaries.
- External Webhook secrecy, one-attempt delivery uncertainty, and privacy projection.
- Attachment encryption, OSS network validation, and passenger workbook normalization.
- Cross-file release version and hash synchronization.
- Concurrent worktree ownership and canonical document integration.
Last Updated
2026-09-09