Skip to Content

Changes for page User Class Diagram

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