docs: add plugin core and Telegram/OpenClaw adapter skeleton / 補 reply-end-controls 核心與 Telegram/OpenClaw 設計骨架
This commit is contained in:
29
core/policy.md
Normal file
29
core/policy.md
Normal file
@@ -0,0 +1,29 @@
|
||||
# Policy
|
||||
|
||||
## Goal
|
||||
|
||||
Define how reply-end choices influence later assistant behavior.
|
||||
|
||||
## Policy rules
|
||||
|
||||
### If `lastChoice = continue`
|
||||
|
||||
- assistant/runtime may continue normal follow-up behavior
|
||||
- assistant may keep short-term task momentum
|
||||
|
||||
### If `lastChoice = stop`
|
||||
|
||||
- assistant should not proactively extend the previous thread
|
||||
- assistant should avoid unnecessary follow-up prompts
|
||||
- assistant should treat the prior exchange as closed
|
||||
|
||||
### If user types a new message
|
||||
|
||||
- typed input takes priority over button state
|
||||
- the new message may implicitly reopen the interaction
|
||||
|
||||
## V1 constraint
|
||||
|
||||
V1 only needs to influence continuation behavior.
|
||||
|
||||
It does not need to redesign routing, tool permissions, or long-term memory behavior.
|
||||
Reference in New Issue
Block a user