43 lines
3.1 KiB
Markdown
43 lines
3.1 KiB
Markdown
# System Overview
|
|
|
|
## Current Architecture
|
|
|
|
Manual or AgentBus input is routed through task-scoped AI/Shadow/Auto/Program orchestration into one validated operation contract. The control plane owns task/session/confirmation/audit state, and the Chrome extension resolves the unique ERP object, enforces page and write gates, performs native actions, and returns action-specific evidence.
|
|
|
|
## Main Components
|
|
|
|
| Component | Responsibility | Notes |
|
|
|---|---|---|
|
|
| `agent设计规范/` | Agent Prompt, five parsing Skills, business templates, business registry, and stable fixtures | Editable source for business semantics; not runtime evidence |
|
|
| `schemas/` and `mappings/` | Parse-state, execution-state, ERP form, field, and lifecycle contracts | Current contracts only |
|
|
| `control-plane/` | Task/session persistence, parser orchestration, confirmation, audit, AgentBus, attachments, receipts, and structured diagnostics | TypeScript source; build output goes to `.build/` |
|
|
| `LianSyn-platform/` | Operator workbench and external parser adapter | Source and UI, not local task output |
|
|
| `chrome-extension/ltjt-order-assistant/` | Logged-in ERP resolution, preflight, native execution, response handling, and requery | Any code change requires synchronized versioned release updates |
|
|
| `dist/` | Versioned current deliverables and machine-readable release manifest | Not a compilation directory |
|
|
| `.project-docs/` | Task-isolated project memory and integrated canonical context | No runtime dependency |
|
|
| `archive/` | Date-scoped immutable history and evidence | Never defines current behavior |
|
|
|
|
## Important Boundaries
|
|
|
|
- AI/Program parsing and ERP resolution/execution share the final operation contract but do not share authority.
|
|
- Platform envelope fields such as task ID, session, parser decision, confirmation, transport, and audit never enter the business operation.
|
|
- Unknown, ambiguous, unverified, or post-write-uncertain states fail closed; automatic retries must not create duplicate writes.
|
|
- PostgreSQL is the sole required durable database/state middleware, and the production artifact provider is OSS. Redis, message queues, MongoDB, and search services are not runtime dependencies.
|
|
- Migrations must complete before the application starts. The current ACK topology starts with one application replica because AgentBus listeners and SSE emission are process-local; horizontal scale requires explicit coordination first.
|
|
- Operational diagnostics are privacy-safe structured JSON on stdout/stderr. Docker owns bounded rotation; repository files and a second mutable log database are not log sinks.
|
|
- In the trusted internal deployment, AgentBus roster attachment downloads may resolve to private/reserved addresses. Credential-free HTTPS, DNS resolution/pinning, redirect revalidation, size, timeout, and digest checks remain mandatory, and trusted channels/bridges own the network-input boundary.
|
|
- Canonical project memory is updated only under Integration Gate; feature tasks write only their task-scoped records.
|
|
|
|
## Related Decisions
|
|
|
|
- DOC-001
|
|
- ARCH-001
|
|
- ROUTE-001
|
|
- RELEASE-001
|
|
- SAFETY-001
|
|
- NETWORK-001
|
|
|
|
## Last Updated
|
|
|
|
2026-08-31
|