Daniele 934726a75d fix(event-triage): never notify about a filtered event ...

Triage was applying the user's notification preferences correctly and then
calling notify() anyway, with the filtering itself as the summary ("filtered
as generic marketing per user preferences") — the interruption the rule was
written to prevent, delivered with an explanation attached.

Nothing in the prompt said that notify() *is* the interruption, so using it as
a record of the decision looked coherent. Say it plainly instead, in the three
places the model passes through: notify delivers immediately and has no silent
variant, a rule that filters a category means no call at all, and a summary
that mentions filtering is the tell that the rule is about to be broken. The
tool description carries the same statement at the call site.

2026-08-20 22:37:15 +01:00

..

AGENT.md

fix(event-triage): never notify about a filtered event

2026-08-20 22:37:15 +01:00

icon.png

rename the TIC system agent to event triage

2026-07-28 21:59:37 +01:00

meta.json

feat(event-triage): user notification preferences via user-memory/notifications.md

2026-08-14 13:21:06 +01:00