Skip to Content

Changes for page User Class Diagram

Last modified by Robert Schaub on 2025/12/24 20:34
From version 4.2
edited by Robert Schaub
on 2025/12/16 20:25
Change comment: Update document after refactoring.
To version 4.4
edited by Robert Schaub
on 2025/12/16 20:28
Change comment: Renamed back-links.

Summary

Details

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