The user strikes system appears to be implemented in the backend, but the admin dashboard (/dashboard/user_strikes) is currently hidden behind a commented-out route pending UI completion.
Once the UI is finished, the docs should cover:
- What strikes are and how they differ from user scores (separate systems: scores use
weightedPenaltyRate; strikes are a distinct accumulating count)
- Configuring which actions apply strikes (
applyUserStrikes toggle per action)
- Setting per-policy strike values (
userStrikeCount on each policy)
- Configuring strike thresholds that trigger automatic actions (
user_strike_thresholds table)
- The
UserStrikesSignal for use as a condition in proactive rules
Implementation refs
server/services/userStrikeService/userStrikeService.tsclient/src/webpages/dashboard/userStrikes/ (4 tabs: Policy Scores, Strike-Enabled Actions, Thresholds & Settings, Analytics)- DB:
public.user_strike_thresholds, public.policies.user_strike_count, public.actions.apply_user_strikes; Scylla: user_strikes table (90-day TTL)
The user strikes system appears to be implemented in the backend, but the admin dashboard (
/dashboard/user_strikes) is currently hidden behind a commented-out route pending UI completion.Once the UI is finished, the docs should cover:
weightedPenaltyRate; strikes are a distinct accumulating count)applyUserStrikestoggle per action)userStrikeCounton each policy)user_strike_thresholdstable)UserStrikesSignalfor use as a condition in proactive rulesImplementation refs
server/services/userStrikeService/userStrikeService.tsclient/src/webpages/dashboard/userStrikes/(4 tabs: Policy Scores, Strike-Enabled Actions, Thresholds & Settings, Analytics)public.user_strike_thresholds,public.policies.user_strike_count,public.actions.apply_user_strikes; Scylla:user_strikestable (90-day TTL)