Trigger
ERP, OA, PLM, MES, WMS, finance, BI, collaboration platforms, databases or local files produce an event requiring cross-system reading, judgment and governed action.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Business trigger: ERP, OA, PLM, MES, WMS, finance, BI, collaboration platforms, databases or local files produce an event requiring cross-system reading, judgment and governed action.
REFERENCE_ARCHITECTURE · READBACK_VERIFY

DECISION RECORD / C.32
Source-traceable reference · pp.68–69
ERP, OA, PLM, MES, WMS, finance, BI, collaboration platforms, databases or local files produce an event requiring cross-system reading, judgment and governed action.
Support every scenario with a common task contract, adapters, permissions, human gates, action gateway and observable trace.
Reuse the original task for duplicate events. Stale data, denied access, rule conflicts, tool timeout and unknown writeback must enter explicit states—never bypass authority, lose a task or report false completion.
The event is traceable; context has sources and versions; A2A routing has boundaries; human gates hold; actions are idempotent; formal state is read back; audit data is complete.
Choose one cross-system event and define its task contract, least privilege, human gates, idempotency and formal readback.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Source-traceable reference
Compare the same operating fields before choosing a direction.
Confirm the owner, authority, human gate, and readback rule.
Define a baseline, target, owner, and observation window before claiming impact.