claude
e481ad4930
The capability was built, wired and degrading correctly, and no utterance could reach it. Its aliases sit on the act dispatch, "что требует внимания" routes to a query, and every query source passed — so the turn fell to the web search and came back with an article about the concept of attention. That reads as an answer, which is worse than silence. queryAttention sits next to "tasks", above the recall sources and well above the personal boundary: it is operational state about his things, and a notes pass would otherwise answer from whatever he once wrote about a server. It calls the same handler the act path calls, so the outage string comes free. An absent or unconfigured Praxis falls through instead of claiming the turn, like queryHome and queryNetwork. A configured Praxis that is down claims it and names the gap. "что нового" is left to the feeds source.
69 lines
2.4 KiB
Go
69 lines
2.4 KiB
Go
package main
|
|
|
|
import (
|
|
"context"
|
|
"strings"
|
|
|
|
"github.com/kami/maven/internal/router"
|
|
)
|
|
|
|
// attentionMarkers — the ways he asks what Praxis is holding. Substrings on a
|
|
// stem, because "внимание", "внимания" and "вниманию" are one word to him.
|
|
//
|
|
// "что нового" is deliberately absent: the feeds source claims it, and it
|
|
// still should — a question about news is a question about the feeds she
|
|
// reads. This list is about the operational state of his things.
|
|
var attentionMarkers = []string{
|
|
"внимани", "что требует", "что не так", "что важн", "что срочн",
|
|
"needs attention", "what needs looking",
|
|
}
|
|
|
|
// isAttentionQuery reports whether the utterance asks what needs looking at.
|
|
func isAttentionQuery(u string) bool {
|
|
s := strings.ToLower(strings.TrimSpace(u))
|
|
if s == "" {
|
|
return false
|
|
}
|
|
for _, m := range attentionMarkers {
|
|
if strings.Contains(s, m) {
|
|
return true
|
|
}
|
|
}
|
|
return false
|
|
}
|
|
|
|
// queryAttention answers "что требует внимания?" from Praxis.
|
|
//
|
|
// The capability was already built and already degraded correctly, and no
|
|
// utterance could reach it (Vikunja #475). Its aliases live on the act
|
|
// dispatch, and the question routes to IntentQuery, so it fell through every
|
|
// source to the web search and came back with an encyclopedia article about
|
|
// the concept of attention — worse than silence, because it reads as an
|
|
// answer.
|
|
//
|
|
// Placed above the recall sources and well above the personal boundary: this
|
|
// is operational state about his things, and a notes pass would otherwise
|
|
// answer it from whatever he once wrote about a server. An unconfigured or
|
|
// absent Praxis falls through rather than claiming the turn, the same
|
|
// convention queryHome and queryNetwork follow. A Praxis that is configured
|
|
// and down does claim it, and says it cannot reach the service — that is the
|
|
// degradation the ecosystem contract asks for, and it comes from the same
|
|
// handler the act path uses.
|
|
func (h *reactiveHandler) queryAttention(ctx context.Context, t *queryTurn) (string, bool) {
|
|
if !isAttentionQuery(t.dec.Utterance) {
|
|
return "", false
|
|
}
|
|
if h.ecosystem == nil || h.ecosystem.praxis == nil {
|
|
return "", false
|
|
}
|
|
reply := h.handlePraxisAct(ctx, router.Decision{
|
|
Utterance: t.dec.Utterance,
|
|
Intent: router.IntentAct,
|
|
Slots: router.Slots{Fn: "list_attention", HasFn: true},
|
|
})
|
|
if reply == "" {
|
|
return "", false
|
|
}
|
|
return reply, true
|
|
}
|