Understanding answers
Understanding answers
Answer statuses
Every Q&A entry on RiftJudge carries a status badge that tells you how much to trust the answer. Status reflects the community verification lifecycle — not AI confidence.
Three status badges
AI-generated answer that has not been confirmed by the community. Read the references — they are your evidence. Treat the answer as a starting point, not a ruling.
A judge has confirmed the answer is correct — either as the original AI response or after an approved community edit replaced it. The strongest trust signal RiftJudge offers.
Outdated or wrong. A judge deprecated it with a reason (shown as a comment). Read-only — voting, comments, and new proposals are closed.
FAQ #{id} naming
In the app, each Q&A entry appears as FAQ #{id} in breadcrumbs and metadata. Both migrated legacy entries and new web-submitted questions use this naming — for example, FAQ #8598.
Flagged for review
When a question's vote score drops to −3 or below, it is flagged for judge review. Flagging does not change the status badge — a verified answer can still be flagged if the community downvotes it.
Judges decide whether to dismiss the flag or deprecate the answer. See The review queue for how judges handle flagged items.
How verification works
| Path | Result |
|---|---|
| Verify | Judge confirms the AI answer is correct without changes → status becomes verified |
| Approve proposal | Judge accepts a community correction that replaces the answer → status becomes verified |
See Verify & approve for the full queue mechanics.
Rules v{X}
Each answer records the core rules version that was in effect when it was generated. Older answers may reference earlier wording of a rule.
Votes & comments
Community voting tracks trust; Voting & comments covers the full mechanics. Comments are flat, chronological, and immutable once posted.