Every use of super-admin, admin, mod, or super-mod privileges now lands as a locked, team_6502ish-authored thread in the public Privilege Use forum. Includes infractions, escalations, suspensions, bans, role changes, badge grants, config + branding edits, moderation-queue actions, IP bans, forum management — the full privileged surface.
What changed in AuditLog::record / postToForum
- Destination + author. Forum 213 (Admin System Log Files, private) → forum slug
privilege-use(public). Author 123 (Curator) →@team_6502ish. Lookups are by slug / username instead of hardcoded id so a future forum reseed can't break the wiring the way forum 206 broke the flair-violation reporter earlier this week. Resolve is request-cached. - Trigger rule expanded. From a narrow 20-entry allowlist to a namespace-prefix match covering every privileged surface:
admin./moderation./forum./category./badge./branding./config./broadcast./security./infraction./appeal./ip_ban./content_filter./bbs./cosmetic./platform./role.plus a short list of unnamespaced user-record privilege actions (user.banned,user.suspended,user.role_*,user.warned,user.purged,user.deleted, etc.). - Excluded from transparency posts (but still written to the audit_log row): routine user activity — login, logout, failed login, registration, referrals, onboarding, account self-service. These aren't privilege use and would drown out the signal on a public forum.
- Threads are locked on creation. A public transparency log only works if nobody can post a fake "resolution" reply under an audit entry they regret making.
- Forum-post path wrapped in try/catch. Any failure there (markdown service down, DB hiccup) can't take down whatever admin flow called
AuditLog::record. Theaudit_logrow is the source of truth; the forum thread is a read-mostly mirror.
Smoke-tested by recording a moderation.test probe and confirming the thread landed in /forums/privilege-use authored by team_6502ish with is_locked = 1. Probe cleaned up after verification.
Historic audit posts in the old admin-system-log-files forum stay where they are — only new actions flow to the new destination. If you want the historic entries migrated, say the word and I can write a one-shot backfill.
. __ ____ ___ ____ _ _
/ /_| ___| / _ \___ \(_)___| |__
| '_ \___ \| | | |__) | / __| '_ \
| (_) |__) | |_| / __/| \__ \ | | |
\___/____/ \___/_____|_|___/_| |_|
D2sk - Sysop