Trigger
An employee asks through group chat, bot, form or meeting action item to retrieve data, replenish stock, revise a plan, create a record, follow up or process a file.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Feishu or WeCom Request to Governed System Action
Business trigger: An employee asks through group chat, bot, form or meeting action item to retrieve data, replenish stock, revise a plan, create a record, follow up or process a file.
REFERENCE_ARCHITECTURE · READBACK_VERIFY
DECISION RECORD / C.20
What this route helps you decide
Source-traceable reference · pp.44–45
Goal
Turn a chat request into a durable task with identity, permission, context, approval, system receipt and closing evidence.
Risk / exception
Stop and explain the gap if access is denied, intent is unclear or an attachment contains sensitive data. Hand RPA page changes or writeback timeouts to a person; do not repeat the operation.
Close condition
Every chat action binds identity and a business key; permission and approval are traceable; the system receipt returns to the original thread; failures and human takeover are recorded.
Next safe action
Choose one frequent collaboration request and bound identity, permitted action, approval and the system-receipt format.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
Evidence stays attached to the decision.
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Knowledge
Source-traceable reference
Comparison
Compare the same operating fields before choosing a direction.
Direction
Confirm the owner, authority, human gate, and readback rule.
Optimization
Define a baseline, target, owner, and observation window before claiming impact.