Skip to Content

Wiki source code of Workflows

Version 1.1 by Robert Schaub on 2025/12/18 12:03
Hide last authors
Robert Schaub 1.1 1 = Workflows =
2 FactHarbor workflows are **simple, automated, focused on continuous improvement**.
3 == 1. Core Principles ==
4 * **Automated by default**: AI processes everything
5 * **Publish immediately**: No centralized approval (removed in V0.9.50)
6 * **Quality through monitoring**: Not gatekeeping
7 * **Fix systems, not data**: Errors trigger improvements
8 * **Human-in-loop**: Only for edge cases and abuse
9 == 2. Claim Submission Workflow ==
10 ```
11 User submits → Duplicate detection → Categorization → Processing queue → User receives ID
12 ```
13 **Timeline**: Seconds
14 **No approval needed**
15 == 3. Automated Analysis Workflow ==
16 ```
17 Claim from queue
18 ↓
19 Evidence gathering (AKEL)
20 ↓
21 Source evaluation (track record check)
22 ↓
23 Scenario generation
24 ↓
25 Verdict synthesis
26 ↓
27 Risk assessment
28 ↓
29 Quality gates (confidence > 40%? risk < 80%?)
30 ↓
31 Publish OR Flag for improvement
32 ```
33 **Timeline**: 10-30 seconds
34 **90%+ published automatically**
35 == 3.5 Evidence and Verdict Workflow ==
36 {{include reference="FactHarbor.Specification.Diagrams.Evidence and Verdict Workflow.WebHome"/}}
37 == 4. Publication Workflow ==
38 **Standard (90%+)**: Pass quality gates → Publish immediately with confidence scores
39 **High Risk (<10%)**: Risk > 80% → Moderator review
40 **Low Quality**: Confidence < 40% → Improvement queue → Re-process
41 == 5. User Contribution Workflow ==
42 ```
43 Contributor edits → System validates → Applied immediately → Logged → Reputation earned
44 ```
45 **No approval required** (Wikipedia model)
46 **New contributors** (<50 reputation): Limited to minor edits
47 == 6. Flagging Workflow ==
48 ```
49 User flags issue → Categorize (abuse/quality) → Automated or manual resolution
50 ```
51 **Quality issues**: Add to improvement queue → System fix → Auto re-process
52 **Abuse**: Moderator review → Action taken
53 == 7. Moderation Workflow ==
54 **Automated pre-moderation**: 95% published automatically
55 **Moderator queue**: Only high-risk or flagged content
56 **Appeal process**: Different moderator → Governing Team if needed
57 == 8. System Improvement Workflow ==
58 **Weekly cycle**:
59 ```
60 Monday: Review error patterns
61 Tuesday-Wednesday: Develop fixes
62 Thursday: Test improvements
63 Friday: Deploy & re-process
64 Weekend: Monitor metrics
65 ```
66 **Error capture**:
67 ```
68 Error detected → Categorize → Root cause → Improvement queue → Pattern analysis
69 ```
70 **A/B Testing**:
71 ```
72 New algorithm → Split traffic (90% control, 10% test) → Run 1 week → Compare metrics → Deploy if better
73 ```
74 == 9. Quality Monitoring Workflow ==
75 **Continuous**: Every hour calculate metrics, detect anomalies
76 **Daily**: Update source track records, aggregate error patterns
77 **Weekly**: System improvement cycle, performance review
78 == 10. Source Track Record Workflow ==
79 **Initial score**: New source starts at 50 (neutral)
80 **Daily updates**: Calculate accuracy, correction frequency, update score
81 **Continuous**: All claims using source recalculated when score changes
82 == 11. Re-Processing Workflow ==
83 **Triggers**: System improvement deployed, source score updated, new evidence, error fixed
84 **Process**: Identify affected claims → Re-run AKEL → Compare → Update if better → Log change
85 == 12. Related Pages ==
86 * [[Requirements>>FactHarbor.Specification.Requirements.WebHome]]
87 * [[Architecture>>FactHarbor.Specification.Architecture.WebHome]]
88 * [[Data Model>>FactHarbor.Specification.Data Model.WebHome]]