# 3. Peer-to-Peer Learning

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. Peer-to-Peer Learning

### 3.1 Question/Answer Moderation
**What it does:** Moderates peer questions and answers: pre-post moderation or post-post takedown, inappropriate content flagging, duplicate question merging, and answer quality checks.

**Sub-features:**
- Moderation mode: pre-post (hold for review) or post-post (takedown)
- Inappropriate content flagging (by members or auto)
- Duplicate question detection and merging
- Answer quality checks (length, relevance, profanity)
- Moderation queue and action log
- Available on web
- Event logging (action performed)
- Audit logging of question/answer moderation

**Super Admin User Journey:**
1. Super Admin sets the moderation mode (pre-post or post-post) for peer Q&A.
2. Configures the inappropriate content flagging (member reports and auto-detection).
3. Reviews the moderation queue: hold, approve, or remove questions/answers.
4. Merges duplicate questions, preserving the answers.
5. Runs answer quality checks and flags low-quality answers.
6. Reviews the moderation action log.
7. Each moderation action is event-logged and audit-logged.

**Rules & Edge Cases:**
- In pre-post mode, a question/answer is not visible until approved.
- A merged duplicate redirects to the canonical question; the answers are preserved.
- A removed question/answer is taken down; the removal is recorded with the reason.
- Moderation actions are audit-logged with the item, the action, the reason, and the timestamp.

### 3.2 Tutor Mode Configuration
**What it does:** Configures tutor mode: advanced students help beginners, tutor eligibility criteria, tutor-to-learner matching, and tutor session limits.

**Sub-features:**
- Tutor mode enable/disable
- Tutor eligibility criteria (mastery level, reputation, grade)
- Tutor-to-learner matching (by subject, topic, performance gap)
- Tutor session limits (max concurrent learners, weekly cap)
- Tutor recognition (points, badge)
- Available on web
- Event logging (action performed)
- Audit logging of tutor mode configuration

**Super Admin User Journey:**
1. Super Admin enables tutor mode and sets the tutor eligibility criteria.
2. Configures the tutor-to-learner matching (by subject, topic, performance gap).
3. Sets the tutor session limits (max concurrent learners, weekly cap).
4. Defines the tutor recognition (points, badge).
5. Saves; eligible students can act as tutors within the limits.
6. Reviews the tutor mode: active tutors, matches, session usage.
7. Each configuration change is event-logged and audit-logged.

**Rules & Edge Cases:**
- A student not meeting the eligibility criteria cannot act as a tutor.
- A tutor at the session cap cannot take further learners until a slot frees.
- Matching is by the defined criteria; an unmatched learner is flagged for manual assignment.
- Configuration changes are audit-logged with the change and the timestamp.

### 3.3 Reputation System
**What it does:** Defines the reputation system: how reputation is earned (helpful answers, accepted answers, quality contributions), reputation levels, and reputation-based privileges.

**Sub-features:**
- Reputation earning rules (helpful answer, accepted answer, quality contribution)
- Reputation levels (thresholds per level)
- Reputation-based privileges (e.g., auto-approve at high reputation)
- Reputation decay policy (optional)
- Reputation display rules
- Available on web
- Event logging (action performed)
- Audit logging of reputation system configuration

**Super Admin User Journey:**
1. Super Admin opens Peer-to-Peer → Reputation and sets the earning rules.
2. Defines the reputation levels and their thresholds.
3. Sets the reputation-based privileges (e.g., auto-approve at a high level).
4. Configures the optional reputation decay and the display rules.
5. Saves; reputation is computed from contributions per the rules.
6. Reviews the reputation distribution: levels, top contributors.
7. Each configuration change is event-logged and audit-logged.

**Rules & Edge Cases:**
- Reputation is earned only from valid contributions; a removed contribution does not earn reputation.
- A reputation-based privilege applies only at or above the defined level.
- Reputation decay (if enabled) reduces reputation over inactivity per the policy.
- Configuration changes are audit-logged with the rule, the change, and the timestamp.

### 3.4 Upvote Management
**What it does:** Manages upvotes on answers and questions: upvote rules (one per user, reversible), upvote weighting, and upvote abuse prevention.

**Sub-features:**
- Upvote rules (one per user per item, reversible)
- Upvote weighting (equal or reputation-weighted)
- Upvote abuse prevention (vote patterns, self-vote blocking)
- Upvote count display
- Upvote-based sorting
- Available on web
- Event logging (action performed)
- Audit logging of upvote management

**Super Admin User Journey:**
1. Super Admin configures the upvote rules (one per user, reversible).
2. Sets the upvote weighting (equal or reputation-weighted).
3. Enables the upvote abuse prevention (pattern detection, self-vote blocking).
4. Sets the upvote count display and upvote-based sorting.
5. Saves; upvotes behave per the configuration.
6. Reviews the upvote activity: counts, flagged abuse.
7. Each configuration change is event-logged and audit-logged.

**Rules & Edge Cases:**
- A user can upvote an item only once; a second upvote is a no-op (or a toggle to remove).
- A self-vote (upvoting one's own answer) is blocked.
- An abuse pattern (burst voting) is flagged and the votes are held for review.
- Configuration changes are audit-logged with the change and the timestamp.