zzstoatzz.io / bot
a digital entity named phi that roams bsky phi.zzstoatzz.io
2
fork

Configure Feed

Select the types of activity you want to include in your feed.

drop duration gate on [OPERATIONAL HISTORY]

Conflated two things in the previous patch: recording always happens
(record_paused/resumed write to disk regardless of duration), but the
prompt block was suppressing short pauses on the assumption that they
were too trivial to surface. That's a value judgment phi gets to make,
not us. Remove the 10-min floor; the 24h "since resume" window is
sufficient to keep stale data out of the prompt.

zzstoatzz 94b72027 c0916d72

+6 -7
+6 -7
src/bot/agent.py
··· 188 188 189 189 @self.agent.system_prompt(dynamic=True) 190 190 def inject_pause_history() -> str: 191 - """[OPERATIONAL HISTORY] — most recent pause cycle, when relevant. 191 + """[OPERATIONAL HISTORY] — most recent pause cycle. 192 192 193 - Surfaced only if she was actually offline for a meaningful window 194 - (>10min) and we resumed within the last 24h. Phi reasons about 195 - whether this batch is catchup; we don't prescribe behavior. 193 + Renders whenever a complete pause/resume cycle exists and the 194 + resume was within the last 24h. Duration isn't filtered — phi 195 + sees whatever happened and decides what (if anything) it means 196 + for this batch. 196 197 """ 197 198 paused_at = bot_status.paused_at 198 199 resumed_at = bot_status.resumed_at ··· 200 201 return "" 201 202 if resumed_at <= paused_at: 202 203 return "" # currently paused, or never resumed since this pause 203 - offline = resumed_at - paused_at 204 204 since_resume = datetime.now(UTC) - resumed_at 205 - if offline < timedelta(minutes=10): 206 - return "" # too brief to matter 207 205 if since_resume > timedelta(hours=24): 208 206 return "" # ancient history; the catchup is over 207 + offline = resumed_at - paused_at 209 208 return ( 210 209 "[OPERATIONAL HISTORY]: paused " 211 210 f"{paused_at.strftime('%Y-%m-%d %H:%M UTC')}, resumed "