Changes for page User Class Diagram

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

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