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,22 @@
|
||||
# Business Rules
|
||||
|
||||
## Durable Rules
|
||||
|
||||
- `agent设计规范/business-adaptation-registry.md` is the cross-session business entry; each business maps user input, Skill/action, ERP flow, contracts, implementation, fixtures, and verification status.
|
||||
- Manual and AgentBus tasks share the same 18 machine routes, task-scoped parser mode snapshot, and organization automation rules.
|
||||
- The two passenger-list import routes are Program-only and wait for exactly one `.xls` or `.xlsx` attachment before deterministic normalization.
|
||||
- Passenger overwrite requires confirmation when target ERP rows are occupied; after `full_replace + confirmed=true`, every attachment-specified sequence is written even when values are unchanged.
|
||||
- A single strict `领队` row supplies leader contact; ambiguous, incomplete, duplicate, or structurally inconsistent leader data fails closed.
|
||||
- Shared-mother-plan `整团游客信息` export is only `shared_plan + visitor-list + tid-only`; independent and concrete shared-child visitor lists remain `did+tid`.
|
||||
- Real writes require unique resolution, exact page identity, ownership, write projection, explicit server response, and action-specific completion evidence.
|
||||
- Current business capability and verification status come from active source/contracts and the lifecycle release gate, never from archive wording.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Fresh authorized runtime read verification remains for the shared-mother-plan whole-visitor export branch.
|
||||
- Authorized current-version ERP write verification remains for SGL/TWN and four independent-order headcount categories.
|
||||
- AgentBus OSS DNS fallback must preserve private/reserved-network SSRF blocking.
|
||||
|
||||
## Last Reviewed
|
||||
|
||||
2026-08-28
|
||||
@@ -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