Draft — owner/legal review required before production launch.

Rating and Community Rules

The owner must approve the seeded category names, descriptions, scale directions, visibility threshold, moderation standard, and appeal contact before launch.

1. Structured scores only

Ratings use active data-driven categories. Each screen displays the category’s stable label, description, minimum, maximum, and what low and high scores mean. Do not assume the same direction for every category. The product does not accept free-text reviews or comments.

2. Eligibility

Both rater and target must be Active members with current consent and the required capability. You cannot rate yourself. A member may hold one current score for each target/category pair; resubmitting updates it. Status and consent are checked again for every mutation, and database constraints are final concurrency protection.

3. Fair participation

4. Public aggregates and privacy

Public output is category average, eligible count, and distinct-rater count. It never identifies individual raters. A category value remains hidden until the configured minimum number of distinct eligible raters—three by default—is satisfied. Invalidated ratings do not contribute.

5. Moderation

Authorized administrators may invalidate and, where appropriate, restore a rating and may suspend abusive members. Every action records a restricted audit entry and reason. Public users cannot view the rater identity or moderation details. The owner must publish a report/appeal contact before production.

6. Removal

Deactivation or DeletionPending immediately prevents new ratings and public visibility. A deletion request also removes ratings authored by or received by that member at once, so aggregates may change before administrator completion. Azure backup copies may persist until their retention expires.