Multi-turn

Monitoring tells you what's broken now. Memory tells you it's the third time. We run a 39-pole smart-parking deployment in Korea: cameras, plate readers and an engine on every pole, 24/7. It fails slowly. A reboot here, a hold there, a rollout that only half lands. The signal is spread across weeks, but an agent's context only covers hours. Forget Fleet is an always-on operations agent built on Muse Glimmer 30B, running locally on one DGX Spark. Every day Glimmer reads the fleet's events and decides what to carry for weeks: remember a new problem, link a repeat to an earlier memory, explain an event that's expected (for example bays removed for construction), resolve a fix, or supersede an old belief. When a pole's failures recur on three or more days, it writes an alert that cites the exact events behind every claim. Code confirms each cited event exists and belongs to that pole, and Muse Spark independently verifies the alert. Days when five or more poles fail together escalate to Muse Spark to tell a shared cause apart from independent faults. In a recorded run over 302 real events (Oct 9 - Nov 4), Glimmer made every memory decision locally: 54 calls, at no per-token cost. On Oct 21, five poles went quiet the same evening. Muse Spark separated the three simultaneous 19:00 silences (one shared cause) from two unrelated gaps, and pointed to that evening's removal work. Of 8 recurring-failure alerts Glimmer raised, Muse Spark confirmed 1 (P-19: three outages in 19 days) and held 7. Six of the held alerts were for bays that had been removed for construction, which a plain monitor would have paged six times. Every memory and every alert links back to the exact events behind it, so an operator can check any claim in seconds. Data: 302 real events from Oct 9 to Nov 4 (our ops logbook plus 36,692 hourly archive records), anonymised. No camera images, plate numbers or names were used. Built during the hackathon: the agent, ledger, clients, stream builder, replay, evaluation and viewer. Pre-existing and not submitted: the parking deployment itself, and our hosted memory product Forget, which inspired the design but is neither included nor called.