Feature: Importance-based event classification #22
Labels
No labels
audit-2025-12-03
component/api
component/commands
component/llm
component/memory
component/tick-loop
component/tools
priority
high
priority
low
status
in-progress
status
needs-info
status
needs-triage
status
on-hold
type
bug
type
documentation
type
enhancement
type
feature
type
refactor
type
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
blightbow/evennia_ai#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overview
Update message classification to return
PerceptionEventwith importance scoring rather than routing to separate buffers.Classification Changes
Current:
classify_message()returns("TRIGGER" | "CONTEXT" | "IGNORE", metadata)New:
classify_message()returnsPerceptionEventwith attributes:requires_response: True for TRIGGER conditionsimportance: Scored based on multiple factorsperception_streamImportance Scoring Heuristics
Files to Modify
messaging/classification.py- Return PerceptionEvent, add importance scoringevent_handling.py- Newrecord_perception_event(),record_self_action()tool_execution.py- Callrecord_self_action()after tool executionPhase
Phase 2 of Milestone #4