2.0 KiB
2.0 KiB
Glossary
| Term | Meaning | Notes |
|---|---|---|
| operation | Unified validated business instruction exchanged between parser, control plane, and executor | Platform/task envelope metadata is excluded |
| parse state | Business-semantic operation before ERP resolution | Must not claim execution success |
| execution state | ERP-enriched operation after unique resolution and strict gates | Contains exact internal refs needed by the executor |
| shared plan / 母团 | Parent shared-tour plan | Whole-visitor export uses tid only |
| shared child / 子单 | Concrete customer order under a shared plan | Visitor list uses did+tid |
| Program-only | Route must use the deterministic parser and may not fall back to AI | Applies to both passenger-list routes and shared-child batch creation |
| Webhook accepted | The external gateway returned HTTP 200 with code=0 and data=true |
Does not prove downstream WeChat/group delivery and must not be described as delivered |
| fresh requery | Read-only ERP verification performed after an action | Required except where an action-specific explicit-success credential is accepted |
| no ERP write | Evidence-backed result that the write boundary was not crossed | Must not be inferred from an unknown post-submit failure |
| management plane | Account, channel, parser-routing, automation-setting, and audit administration available to admin |
Excludes every business-task API, dashboard, browser worker, and task principal |
| task data plane | Business-task creation, reads, inputs, lifecycle mutations, events, browser execution, results, artifacts, and deletion | Available only to team_lead/user; normal operations require immutable ownership |
| immutable assignee | The durable assigned_user_id that owns task execution and employee attribution |
Drives owner-only operations, per-account FIFO, and the cross-source team-lead dashboard |
| Promotion Candidate | Task-scoped proposal for durable canonical memory | Accepted only through Integration Gate |