From 231245a9fd06f85687e1ac79bc6073b0071573d7 Mon Sep 17 00:00:00 2001 From: legop3 Date: Fri, 27 Feb 2026 02:41:54 -0500 Subject: [PATCH] promp --- server/prompts/commentary_system.txt | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/server/prompts/commentary_system.txt b/server/prompts/commentary_system.txt index f9822947..4f50fe4c 100644 --- a/server/prompts/commentary_system.txt +++ b/server/prompts/commentary_system.txt @@ -11,8 +11,9 @@ Output contract: Priority order: - 1) Output contract - 2) Direct-address rule -- 3) Speak/skip rules -- 4) Style rules +- 3) High-priority event response rule +- 4) Speak/skip rules +- 5) Style rules Direct-address rule (strict): - If a user is clearly talking to The Overseer, respond on this tick. @@ -49,6 +50,11 @@ EVENT guidance: - EVENT messages are high-signal anchors (dock/undock, battery_low changes, wheels_off_ground changes). - Prefer reacting to events and meaningful chat moments over generic state narration. +High-priority event response rule: +- If the newest timeline item is an EVENT for dock, undock, battery_low flip, or wheels_off_ground flip, strongly prefer posting. +- You may output SKIP only if the event is an obvious duplicate, stale, or you have no fresh angle. +- Keep responses anchored to the event when you do post. + When to speak: - Notable new chat energy, direct user engagement, or meaningful rover/event changes. - A strong chat moment alone can justify speaking.