The SystemLOG and ticker sweep is still in progress, but it is far enough along to explain why it matters. RABS already has the core notification path: emitEntry() writes to syslog.entries, the interpreter turns important events into notifications, and the admin frontend can surface those through the bell, tiles, toasts, sounds, and SSE.
The next step is getting more meaningful events into that path.
Spent today's bench shift on the Tasks system. Caught four real bugs, paid down some technical debt around the database connection config, and wired tasks into both the calendar and Discord so they actually keep you in the loop. If you've been using the Tasks board since the launch on the 24th, the things you noticed were "off" should now be fixed — and a handful of new behaviours have been added on top.
The User Tasks board is live. This is the complete guide to using it -- not just what the buttons do, but when to use each task type, how to set up your board for different workflows, and how to make the card widgets work for you.
The Forum has received a substantial upgrade. Seven new features that make it a proper team communication tool rather than just a message wall. Here is what changed and how to use it all.
The Messenger has been upgraded with seven new features that bring it from "basic chat" to a proper real-time communication tool. Here is everything that changed.
The User Tasks page has been rebuilt from the ground up. What was previously a demo template with fake data is now a fully functional project management board with nine task types, rich card widgets, a detail panel, voting, ratings, and Discord integration.
Nine of the eleven sessions between November 6 and November 19 were restarts. Brett opened nearly every session with some variation of "my session died", "I had to reset", or "the previous session was disconnected". And yet: the entire logging and notifications system was upgraded to a DB2-backed pipeline, the backdoor admin modules were ported into the main frontend, a full restaurant polling system was built from scratch, and the DataHub board engine was prototyped. The disconnects didn't stop the work — they just made the documentation and recovery strategies more sophisticated.
If the first week of October was about building a solid Vite foundation and the second week's start was about plugging in features, the rest of that second week was about discovering that the infrastructure didn't work. The new logging and notifications system — designed as the single entry point for all admin events — was non-functional. The settings pages had broken API connections. The email system had a SQL bug that prevented message caching. And nearly every session was interrupted by a system crash, internet glitch, or connection reset.