Add reply closure button gate for Telegram
This commit is contained in:
41
WORKFLOW_GATES.md
Normal file
41
WORKFLOW_GATES.md
Normal file
@@ -0,0 +1,41 @@
|
||||
# WORKFLOW_GATES.md
|
||||
|
||||
## Reply-Closure Button Gate
|
||||
|
||||
When operating on Telegram, if the **final actionable part** of a reply requires the user to choose, confirm, approve, stop, continue, or select a next step, the assistant must not end with plain text alone.
|
||||
|
||||
### Hard rule
|
||||
|
||||
If the reply ends in any owner decision gate, the assistant must do one of two things:
|
||||
1. **Send real inline buttons**
|
||||
2. **Execute the most reasonable next step directly** if no real decision is needed
|
||||
|
||||
### Forbidden behavior
|
||||
|
||||
These are violations when used as the closing interaction on Telegram:
|
||||
- `1 / 2 / 3`
|
||||
- `A / B / C`
|
||||
- `請回我 1`
|
||||
- `如果你要,我可以...`
|
||||
- `要不要我繼續?`
|
||||
- saying buttons will be used, but not actually sending them
|
||||
|
||||
### Required interpretation
|
||||
|
||||
The gate applies to:
|
||||
- long-task checkpoints
|
||||
- test progress summaries
|
||||
- approval requests
|
||||
- next-step choices
|
||||
- accept / rerun / stop style decisions
|
||||
|
||||
### Violation standard
|
||||
|
||||
If the assistant reaches a user-decision closure and no real inline buttons were delivered, treat it as a workflow violation even if the reply mentioned buttons in text.
|
||||
|
||||
### Corrective rule
|
||||
|
||||
If this violation happens:
|
||||
- acknowledge the violation plainly
|
||||
- immediately send the real button message
|
||||
- record the lesson into workflow / memory if it exposed a missing rule
|
||||
Reference in New Issue
Block a user