docs: migrate project memory governance
This commit is contained in:
1 parent
7b5d855b09
commit
e7aa58a203
37 files changed
+942
-34
No files matched your search
@@ -0,0 +1,13 @@
|
||||
# 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 |
|
||||
| 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 |
|
||||
| Promotion Candidate | Task-scoped proposal for durable canonical memory | Accepted only through Integration Gate |
|
||||
Reference in new issue
Block a user