Skip to Content

Changes for page User Class Diagram

Last modified by Robert Schaub on 2025/12/24 20:34
From version 4.3
edited by Robert Schaub
on 2025/12/16 20:27
Change comment: Update document after refactoring.
To version 2.1
edited by Robert Schaub
on 2025/12/12 19:37
Change comment: Imported from XAR

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FactHarbor.Archive.FactHarbor V0\.9\.18.Specification.Diagrams.WebHome
1 +FactHarbor.Specification.Diagrams.WebHome
Content
... ... @@ -1,122 +1,49 @@
1 1  **User Class Diagram**
2 2  
3 -This diagram shows the user role hierarchy in FactHarbor v0.9.1, with corrected inheritance.
3 +{{mermaid}}
4 +classDiagram
5 + class User {
6 + <<Abstract>>
7 + +String UserID
8 + +String DisplayName
9 + +String Email
10 + +Enum Type
11 + }
12 + class TechnicalUser {
13 + +String SystemName
14 + }
15 + class ContributingUser {
16 + +String PrimaryRole
17 + }
18 + class TrustedContributor {
19 + +String CertificationLevel
20 + }
21 + class Reviewer {
22 + +String Domain
23 + }
24 + class Expert {
25 + +String ExpertiseArea
26 + }
27 + class FederationAdmin {
28 + +List Permissions
29 + }
30 + class FederationNode {
31 + +String NodeID
32 + +String Status
33 + }
34 + class ReviewAction {
35 + +String ActionID
36 + +DateTime Timestamp
37 + +Enum ActionType
38 + }
4 4  
5 -== Critical: Corrected Inheritance ==
40 + User <|-- TechnicalUser
41 + User <|-- ContributingUser
42 + ContributingUser <|-- TrustedContributor
43 + ContributingUser <|-- Reviewer
44 + Reviewer <|-- Expert
45 + TechnicalUser <|-- FederationAdmin
6 6  
7 -**IMPORTANT CORRECTION**:
8 -* Moderator derives from **Reviewer** (NOT from Expert)
9 -* Maintainer derives from **Contributor** (NOT from Reviewer or Moderator)
10 -
11 -**Two Independent Tracks from Contributor**:
12 -
13 -**Content Track**: Contributor → Reviewer → (Auditor | Expert | Moderator)
14 -* Focus: Content quality, validation, community management
15 -* Skills: Domain expertise, review, moderation
16 -
17 -**Technical Track**: Contributor → Maintainer
18 -* Focus: System operations, configuration, deployment
19 -* Skills: DevOps, system administration, technical configuration
20 -* **Independent from content review** - Maintainers don't need review skills
21 -
22 -**System Track**: Reader → Technical User
23 -* Not human users - automated processes
24 -* Examples: AKEL instances, sync bots, monitors
25 -* Managed by Maintainers
26 -
27 -== Role Hierarchy Explanation ==
28 -
29 -**Base: Reader**
30 -* Anyone, no login required
31 -* Foundation for all other roles
32 -* Can browse, search, compare, flag, and **automatically submit claims**
33 -
34 -**Technical User** (system type, extends Reader)
35 -* **Not human users** - automated system processes
36 -* Examples: AKEL instances, federation sync bots, backup services, monitoring
37 -* Can perform automated operations
38 -* AKEL is primary implementation of Technical User pattern
39 -
40 -**Contributor** (extends Reader)
41 -* Registered human users
42 -* Can submit evidence, propose scenarios, participate in discussions
43 -* All Reader capabilities plus contribution rights
44 -* **Two-way branching**: Can become Reviewer (content track) or Maintainer (technical track)
45 -
46 -**Reviewer** (is-a Contributor - Content Track)
47 -* Trusted community members on **content track**
48 -* Can review and approve content
49 -* Can validate AI-generated content (Mode 2 → Mode 3 for Tier B/C)
50 -* Participates in audit sampling
51 -* **Three-way branching**: Can specialize as Auditor, Expert, or Moderator
52 -
53 -**Maintainer** (is-a Contributor - Technical Track)
54 -* Core technical team members on **technical track**
55 -* System configuration and deployment authority
56 -* Does NOT require review skills
57 -* Manages Technical Users (creates AKEL instances, sync bots, etc.)
58 -* **Independent from content review hierarchy**
59 -
60 -**Specialized Reviewer Roles**:
61 -
62 -**Auditor** (specialized Reviewer - QA track)
63 -* Dedicated quality assurance role
64 -* Reviews sampled AI-generated content
65 -* Validates quality gate enforcement
66 -* Provides feedback for system improvement
67 -
68 -**Expert** (specialized Reviewer - domain track)
69 -* Subject matter specialists
70 -* Final authority for Tier A content in their domain
71 -* Can define domain-specific standards
72 -* Required for Tier A "Human-Reviewed" status
73 -
74 -**Moderator** (specialized Reviewer - process track)
75 -* Community management focus
76 -* Handles abuse and disputes
77 -* Manages users and permissions
78 -* Oversees audit system
79 -* **Independent from domain expertise and technical operations**
80 -
81 -**AKEL** (Technical User implementation)
82 -* AI system implementing Technical User interface
83 -* Creates drafts for Contributor review
84 -* Subject to Auditor oversight
85 -* Never bypasses human authority
86 -
87 -== Key Design Principles ==
88 -
89 -**Why Maintainer derives from Contributor (not Reviewer)**:
90 -* **Different skill set**: Technical operations ≠ Content review
91 -* **Separation of concerns**: Technical authority independent from editorial authority
92 -* **Flexibility**: Can have technical experts without review experience
93 -* **Realistic**: System admin skills and content review skills are distinct
94 -* **Cleaner**: Maintainer manages Technical Users (including AKEL) - natural fit on technical track
95 -
96 -**Why Moderator derives from Reviewer (not Expert)**:
97 -* Moderators handle **process** (community management, disputes) not **domain expertise**
98 -* Experts focus on **subject matter** (medical, legal, scientific validation)
99 -* Allows independent oversight of content quality (Experts) vs community behavior (Moderators)
100 -* Moderators don't need domain expertise to handle community issues
101 -
102 -**Technical User Pattern**:
103 -* **Purpose**: Represents automated system processes
104 -* **Examples**: AKEL (AI processing), Federation sync bots, Scheduled audit tasks, Backup services, Monitoring systems, API integrations
105 -* **Managed by**: Maintainers create and configure Technical Users
106 -* **Authority**: Limited to programmatic operations, no human-level decisions
107 -
108 -**Progressive Trust**:
109 -* Reader → Contributor (registration)
110 -* Contributor → Reviewer (content track) OR Maintainer (technical track)
111 -* Reviewer → Auditor/Expert/Moderator (specializations)
112 -* All appointments based on demonstrated competence
113 -
114 -**Human Authority**:
115 -* Technical Users assist but don't make human-level decisions
116 -* Human Reviewers validate AI outputs
117 -* Experts have final say on Tier A content
118 -* Moderators have final say on community matters
119 -* Maintainers have final say on technical configuration
120 -
121 -{{include reference="Test.FactHarborV09.Specification.Diagrams.User Class Diagram_Mermaid.WebHome"}}
122 -
47 + FederationAdmin --> FederationNode : administers
48 + User --> ReviewAction : performs
49 +{{/mermaid}}