Glossary

Band, profile, monitor mode, trusted, exempt, credit, entitlement. Every term the dashboard and the log use, defined once.

Words that appear in the dashboard and the log, defined once. If a page uses a term without explaining it, it should be here.

Judging a message

Detector. One thing the engine looks for. Twenty of them, running in stages. No single detector decides anything on its own.

Signal. Something a detector noticed about a message. Evidence, not a verdict.

Band. How serious the engine judged a message to be, in words rather than numbers: None, Low, Medium, High or Critical. Each band has actions you choose. The band is what appears in the log, and it is deliberately what the public site shows too.

Profile. A named set of sensitivity defaults, from relaxed to locked down, so you do not have to configure everything individually. Changing profile changes many settings at once; the moment you adjust one by hand you are on a custom profile, which is fine and expected.

Monitor mode. The whole engine runs and nothing is enforced. The log records what would have happened. Every server starts here.

Enforce mode. Actions are carried out.

Explicit action. A rule that carries its own action rather than contributing evidence. If it matches, that action happens.

Contributory rule. A rule that adds evidence and lets the whole picture decide. Most of your rules should be these.

Acting on a message

Actions. What Wardnox can do: delete the message, time the member out, kick them, or ban them. Each needs a Discord permission, and it only does what you have configured.

Escalation. Repeat offences within your retention window get progressively firmer responses. Marking something a false positive removes it from that history, so your tuning does not push somebody up the ladder unfairly.

Kill switch. Automatic protection against your own rules. A rule that suddenly starts matching a large share of traffic is switched to monitor mode by itself, your moderators are told, and the message that tripped it is not acted on.

Emergency stop. Stops all enforcement immediately. Scanning and logging carry on, so you keep the record while you work out what went wrong.

Lockdown. Temporarily hardens everything during an attack. Reversible, and snapshotted before it applies.

Snapshot. An automatic copy of your configuration taken before every change, so any change is one click from being undone.

Members

Trusted. A user or role exempt from scanning. Staff are exempt by default, which you can turn off.

Exempt. A message that was not scanned because of who sent it. These are not recorded unless you ask for them, which is why a moderator's message can look like it was never seen.

Verification. A challenge on join, before a member can participate.

Links

Allowlist. Domains you permit. An allowlisted link is removed from the message before anything scores it, so nothing can flag it. Only the link is exempt, not the message around it.

Blocklist. Domains you refuse. Blocking always beats allowing, and always covers subdomains.

Registrable domain. The part of a hostname somebody could actually buy: example.com in help.example.com. Wardnox compares this rather than matching text, which is why allowing example.com never allows example.com.attacker.net.

Paying

Credit. One thing the AI does for you: answering a member, checking a borderline message, or reading a document into the knowledge base. Everything the AI does spends credits and nothing else does. Scanning, blocking, enforcing, verification and logging are never metered.

Allowance. The credits included with your plan each month. It refills and does not stack up. Credits you have bought are separate and stay until spent.

Trial. Fourteen days of Pro when Wardnox joins, with no card. Conversation and the knowledge base become available to switch on; they are not switched on for you.

Entitlement. What your plan permits. Worth separating from what is running: an entitlement decides what you are allowed to enable, never what is enabled.

History. How far back you can read your own security events, and how long they are kept. A ceiling set by your plan, not a quota. Keeping less is always allowed.