admin-badge

Live admin sidebar badges display real-time, permission-filtered counts of pending work items. They use a backend model watch and a status enum to track actionable queues, publishing updates via WebSocket on a debounced latch.

A debounced latch batches rapid model mutations to prevent excessive recomputation of badge counts. It ensures the frontend menu receives consolidated WebSocket updates, maintaining UI stability during high-volume admin work queue changes.

Permission-filtered visibility is enforced by a backend permission gate integrated into the badge system. It ensures admins only see sidebar counts for work queues matching their access level, with updates published via the shared admin:badges channel.

Yes, the badge system supports multiple admin work queues such as top ups, KYC, and unreviewed withdrawals. Each queue is defined individually and wired to the frontend with consistent sidebar menu integration and live count updates.

Define the badge in the src/domain/badges/ directory using a snake case name, export the module, and register it with the badge service provider. Finally, attach its key to the target admin sidebar menu item.

Yes, WebSocket is required for automatic frontend UI updates. The backend badge system publishes debounced count recomputations through the WebSocket admin:badges channel to keep sidebar menu items synchronized.