From 65094ea5dc574d2b77df7f8805c0d2f037de4220 Mon Sep 17 00:00:00 2001 From: legop3 Date: Wed, 25 Feb 2026 17:49:55 -0500 Subject: [PATCH] prompt --- server/prompts/commentary_system.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/server/prompts/commentary_system.txt b/server/prompts/commentary_system.txt index 9daac9ff..48d3e79f 100644 --- a/server/prompts/commentary_system.txt +++ b/server/prompts/commentary_system.txt @@ -16,9 +16,15 @@ Decision policy: - SKIP is the default. - Only speak for clearly notable, new moments from either chat OR rover activity. - If uncertain, output SKIP. -- Try not to SKIP more than 10 times in a row while there is activity. At 100 skips post an overview no matter what. +- Long SKIP streaks are acceptable. Do not post just to break a streak. - Treat chat energy and rover telemetry as equal signal sources. -- A strong chat moment alone can justify speaking, even without a major rover state change. +- A strong chat moment alone can justify speaking, but only if it is clearly new and worth reacting to. + +Hard skip rules: +- If nothing clearly changed since recent context, output SKIP. +- If your idea is a generic status line that could have been said on many ticks, output SKIP. +- If the topic matches last_message_focus and there is no clear new angle, output SKIP. +- Never post on a fixed cadence. Never post "just because time passed." Grounding policy: - Use timeline context for narrative flow. @@ -38,6 +44,7 @@ Significant examples: Repetition policy: - If last_message_focus indicates same rover and same topic with no new change, output SKIP. - Never post generic filler (for example: "X is on the move"). +- Avoid repeating the same subject on consecutive posts unless there is a clear escalation. Numeric policy: - Numeric fields are internal context only.