Review & Data Use

This page describes the Review & Data Use model, defining User roles and how review actions are logged.

User & Role Concepts

• USER: Base entity for all users (human or technical).
• TECHNICAL_USER: Strictly technical identities (services, federation components, background jobs).
• CONTRIBUTING_USER: Users that can contribute content (claims, scenarios, evidence).
  • TRUSTED_CONTRIBUTOR: Additional trust / certification properties.
  • REVIEWER: Can perform review actions on versioned entities.
  • EXPERT: Reviewer with domain‑specific expertise / higher authority.

• FEDERATION_NODE: Technical entity representing a participating node in the federation.
• FEDERATION_ADMIN: Administers one or more federation nodes; not necessarily a content contributor.

Review Actions

The system logs every significant action:

• REVIEW_ACTION logs *who* did *what* on *which* versioned entity.
• Fields: ``ReviewActionID``, ``UserID``, ``EntityType``, ``EntityVersionID``, ``ActionType``, ``Timestamp``.
• Each entry targets a specific VERSIONED entity (e.g., ClaimVersion, ScenarioVersion).
• Claim Clusters may also be targets of review actions (e.g., curation or moderation).

Review & Data Use ERD

User Class Diagram

classDiagram
 class User {
 +UUID id
 +String username
 +String email
 +Role role
 +Int reputation
 +Timestamp created_at
 +contribute()
 +flag_issue()
 +earn_reputation()
 }
 class Reader {
 <>
 +browse()
 +search()
 +flag_content()
 }
 class Contributor {
 <>
 +edit_claims()
 +add_evidence()
 +suggest_improvements()
 +requires: reputation sufficient
 }
 class Moderator {
 <>
 +review_flags()
 +hide_content()
 +resolve_disputes()
 +requires: appointed by Governing Team
 }
 User --> Reader : default role
 User --> Contributor : registers + earns reputation
 User --> Moderator : appointed
 note for User "Reputation system unlocks permissions progressively"
 note for Contributor "Reputation sufficient: Full edit access"
 note for Contributor "Reputation sufficient: Can approve changes"

Simplified flat role structure:

• Three roles only: Reader (default), Contributor (earned), Moderator (appointed)
• Reputation system replaces role hierarchy
• Progressive permissions based on reputation, not titles