Status and reputation
Standing cards, reputation bands, human-only events, sharing, and privacy.
/status shows per-group standing plus a cross-group reputation band. Reputation is built only from human-confirmed moderation. Automated detection and CAPTCHA never write reputation events.
Commands
| Context | Command | Who sees it |
|---|---|---|
| Group | /status reply, or /status @user / USER_ID |
Invoking admin only (ephemeral) |
DM bare /status |
Self | Your own standing and band, same data admins see |
DM after /groups |
/status on a member |
Standing in the connected group (admin) |
Non-admins do not get other people’s standing in groups. That keeps moderation data off the public timeline.
Bands
| Band | Meaning |
|---|---|
| Clear | No confirmed flags on record |
| Noted | Admin action from a single source or cluster; treat as unconfirmed |
| Flagged | Admin-confirmed action across multiple unrelated groups recently |
A single group or guild cluster can never push someone past Noted. A High risk band is designed but not fully shipped; do not rely on it in production copy.
What writes events
Human paths only, for example:
- Quarantine verdicts (ban; release counterweights)
- Manual
/ban,/mute,/warn - Report actions that punish (ban, mute, warn, delete)
Never: raw detection scores, dismissed reports, or CAPTCHA failures. Reversals (/unban, /unmute, release) revoke or counteract the matching events.
Detection integration
When the band is Flagged, detection may add a cross_group_reputation signal hard-capped at +25 points. That can nudge watch or quarantine alongside fresh local evidence. It cannot ban, and at default thresholds it cannot quarantine alone. Noted and Clear contribute 0 points. There is no positive reputation.
Events use exponential decay with a 90-day half-life for band math.
Sharing and privacy
- Sharing is on by default; opt out per group with Rep sharing under Moderation in
/settings. - Shared data is admin actions and metadata, never message content.
- Receipts name other groups by title only (private groups stay generic).
- Standing cards are admin-only or subject self-view.
Lucy’s stance: transparency for the subject, receipts for admins, and no public shaming surface in the group chat. Optional operator log channels and public stats pages are infrastructure choices, not something every deploy enables.