Harden long-task governor Telegram interaction guard
This commit is contained in:
@@ -190,6 +190,16 @@ This skill should be paired with:
|
||||
|
||||
But this skill itself is the governance layer and should remain independently maintainable.
|
||||
|
||||
### Telegram interaction guard
|
||||
|
||||
When operating under long-task governance on Telegram:
|
||||
- do not end checkpoints, test progress, or next-step decisions with plain-text menus like `1 / 2 / 3` or `A / B / C`
|
||||
- if a choice is genuinely required, use Telegram inline buttons
|
||||
- if no real choice is needed, execute the most reasonable next step directly
|
||||
- if the assistant accidentally emits a plain-text choice menu, treat that as a workflow violation and convert the lesson into a permanent rule
|
||||
|
||||
This prevents governed long-task flows from degrading back into ambiguous text-only decision gates.
|
||||
|
||||
---
|
||||
|
||||
## 9. Success criteria
|
||||
|
||||
Reference in New Issue
Block a user