Changes for page Workflows
Last modified by Robert Schaub on 2025/12/24 20:34
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,352 +1,342 @@ 1 1 = Workflows = 2 2 3 -This page describes the core workflowsfor contentcreation,review,and publication inFactHarbor.3 +This chapter defines the core workflows used across the FactHarbor system. 4 4 5 - ==Overview ==5 +Each workflow describes: 6 6 7 -FactHarbor workflows support three publication modes with risk-based review: 7 +* Purpose 8 +* Participants 9 +* Steps 10 +* Automation vs. manual work 8 8 9 -* **Mode 1 (Draft)**: Internal only, failed quality gates or pending review 10 -* **Mode 2 (AI-Generated)**: Public with AI-generated label, passed quality gates 11 -* **Mode 3 (Human-Reviewed)**: Public with human-reviewed status, highest trust 12 +Workflows included: 12 12 13 -Workflows vary by **Risk Tier** (A/B/C) and **Content Type** (Claim, Scenario, Evidence, Verdict). 14 +1. Claim Workflow 15 +2. Scenario Workflow 16 +3. Evidence Workflow 17 +4. Verdict Workflow 18 +5. Re-evaluation Workflow 19 +6. Federation Synchronization Workflow 20 +7. User Role & Review Workflow 21 +8. AKEL Workflow 22 +9. Global Trigger Flow 23 +10. Entity Lifecycle Notes 14 14 15 15 ---- 16 16 17 -== Claim Submission & PublicationWorkflow ==27 +== Claim Workflow == 18 18 19 -=== Step 1: Claim Submission === 29 +**Purpose:** 30 +Transform raw text or input material into a normalized, classified, deduplicated, and versioned claim ready for scenario evaluation. 20 20 21 -**Actor**: Contributor or AKEL 32 +**Participants:** 33 +* Contributor 34 +* AKEL 35 +* Reviewer 22 22 23 -**Actions**: 24 -* Submit claim text 25 -* Provide initial sources (optional for human contributors, mandatory for AKEL) 26 -* System assigns initial AuthorType (Human or AI) 37 +=== Steps === 27 27 28 -**Output**: Claim draft created 39 +1. **Ingestion** 40 +* User submits text, URL, transcript, or multi-claim content 41 +* AKEL extracts one or multiple claims 29 29 30 -=== Step 2: AKEL Processing === 43 +1. **Normalization** 44 +* Standardizes wording 45 +* Reduces ambiguity 46 +* Flags implicit assumptions 31 31 32 -**Automated Steps**: 33 -1. Claim extraction and normalization 34 -2. Classification (domain, type, evaluability) 35 -3. Risk tier assignment (A/B/C suggested) 36 -4. Initial scenario generation 37 -5. Evidence search 38 -6. **Contradiction search** (mandatory) 39 -7. Quality gate validation 48 +1. **Classification (AKEL draft → Reviewer confirm)** 49 +* ClaimType 50 +* Domain 51 +* Evaluability 52 +* SafetyCategory 40 40 41 -**Output**: Processed claim with risk tier and quality gate results 54 +1. **Duplicate & Similarity Detection** 55 +* Embeddings created 56 +* Similar claims found 57 +* Reviewer merges, splits, or confirms uniqueness 42 42 43 -=== Step 3: Quality Gate Checkpoint === 59 +1. **Version Creation** 60 +* New ClaimVersion stored 61 +* Every edit creates a new immutable version 44 44 45 -**Gates Evaluated**: 46 -* Source quality 47 -* Contradiction search completion 48 -* Uncertainty quantification 49 -* Structural integrity 63 +1. **Cluster Assignment** 64 +* AKEL proposes cluster membership 65 +* Reviewer confirms 50 50 51 -**Outcomes**: 52 -* **All gates pass** → Proceed to Mode 2 publication (if Tier B or C) 53 -* **Any gate fails** → Mode 1 (Draft), flag for human review 54 -* **Tier A** → Mode 2 with warnings + auto-escalate to expert queue 67 +1. **Scenario Linking (optional)** 68 +* Existing scenarios connected 69 +* AKEL may propose new drafts 55 55 56 -=== Step 4: Publication (Risk-Tier Dependent) === 71 +1. **Publication** 72 +* Claim becomes active and visible 57 57 58 -**Tier C (Low Risk)**: 59 -* **Direct to Mode 2**: AI-generated, public, clearly labeled 60 -* User can request human review 61 -* Sampling audit applies 74 +**Flow:** 75 +Ingest → Normalize → Classify → Deduplicate → Cluster → Version → Publish 62 62 63 -**Tier B (Medium Risk)**: 64 -* **Direct to Mode 2**: AI-generated, public, clearly labeled 65 -* Higher audit sampling rate 66 -* High-engagement content may auto-escalate 77 +---- 67 67 68 -**Tier A (High Risk)**: 69 -* **Mode 2 with warnings**: AI-generated, public, prominent disclaimers 70 -* **Auto-escalated** to expert review queue 71 -* User warnings displayed 72 -* Highest audit sampling rate 79 +== Scenario Workflow == 73 73 74 -=== Step 5: Human Review (Optional for B/C, Escalated for A) === 81 +**Purpose:** 82 +Define the specific analytic contexts needed to evaluate each claim. 75 75 76 -** Triggers**:77 -* Userrequestsreview78 -* Auditflagsissues79 -* High engagement(TierB)80 -* A utomatic(TierA)84 +**Participants:** 85 +* Contributor 86 +* Reviewer 87 +* Domain Expert 88 +* AKEL 81 81 82 -**Process**: 83 -1. Reviewer/Expert examines claim 84 -2. Validates quality gates 85 -3. Checks contradiction search results 86 -4. Assesses risk tier appropriateness 87 -5. Decision: Approve, Request Changes, or Reject 90 +=== Steps === 88 88 89 -**Outcomes**: 90 -* **Approved** → Mode 3 (Human-Reviewed) 91 -* **Changes Requested** → Back to contributor or AKEL for revision 92 -* **Rejected** → Rejected status with reasoning 92 +1. **Scenario Proposal** 93 +* Drafted by contributor or generated by AKEL 93 93 94 ----- 95 +1. **Completion of Required Fields** 96 +Must include: 97 +* Definitions 98 +* Assumptions 99 +* ContextBoundary 100 +* EvaluationMethod 101 +* SafetyClass 102 +* VersionMetadata 95 95 96 -== Scenario Creation Workflow == 104 +1. **Safety Interception (AKEL)** 105 +Flags: 106 +* non-falsifiable structures 107 +* pseudoscientific assumptions 108 +* unsafe contexts 97 97 98 -=== Step 1: Scenario Generation === 110 +1. **Redundancy & Conflict Check** 111 +* Similar scenarios merged 112 +* Contradictions flagged 99 99 100 -**Automated (AKEL)**: 101 -* Generate scenarios for claim 102 -* Define boundaries, assumptions, context 103 -* Identify evaluation methods 114 +1. **Reviewer Validation** 115 +Ensures clarity, neutrality, and methodological validity. 104 104 105 -**Manual (Expert/Reviewer)**: 106 -* Create custom scenarios 107 -* Refine AKEL-generated scenarios 108 -* Add domain-specific nuances 117 +1. **Expert Approval (mandatory for high-risk domains)** 109 109 110 -=== Step 2: Scenario Validation === 119 +1. **Version Storage** 120 +* Each revision = new ScenarioVersion 111 111 112 -**Quality Checks**: 113 -* Completeness (definitions, boundaries, assumptions clear) 114 -* Relevance to claim 115 -* Evaluability 116 -* No circular logic 122 +**Flow:** 123 +Draft → Validate → Safety Check → Review → Expert Approval → Version → Activate 117 117 118 -**Risk Tier Assignment**: 119 -* Inherits from parent claim 120 -* Can be overridden by expert if scenario increases/decreases risk 121 - 122 -=== Step 3: Scenario Publication === 123 - 124 -**Mode 2 (AI-Generated)**: 125 -* Tier B/C scenarios can publish immediately 126 -* Subject to sampling audits 127 - 128 -**Mode 1 (Draft)**: 129 -* Tier A scenarios default to draft 130 -* Require expert validation for Mode 2 or Mode 3 131 - 132 132 ---- 133 133 134 -== Evidence EvaluationWorkflow ==127 +== Evidence Workflow == 135 135 136 -=== Step 1: Evidence Search & Retrieval === 129 +**Purpose:** 130 +Structure, classify, validate, version, and link evidence to scenarios. 137 137 138 -** AKEL Actions**:139 -* Search academic databases, reputablemedia140 -* **Mandatory contradiction search** (counter-evidence,reservations)141 -* Extractmetadata (author, date, publication,methodology)142 -* A ssesssourcereliability132 +**Participants:** 133 +* Contributor 134 +* Reviewer 135 +* Domain Expert 136 +* AKEL 143 143 144 -**Quality Requirements**: 145 -* Primary sources preferred 146 -* Diverse perspectives included 147 -* Echo chambers flagged 148 -* Conflicting evidence acknowledged 138 +=== Steps === 149 149 150 -=== Step 2: Evidence Summarization === 140 +1. **Evidence Submission** 141 +* File, dataset, URL, or extracted text 151 151 152 -**AKEL Generates**: 153 -* Summary of evidence 154 -* Relevance assessment 155 -* Reliability score 156 -* Limitations and caveats 157 -* Conflicting evidence summary 143 +1. **Metadata Extraction (AKEL)** 144 +* EvidenceType 145 +* Category 146 +* Provenance 147 +* Study design 148 +* ExtractionMethod 149 +* ReliabilityHints 158 158 159 -**Quality Gate**: Structural integrity, source quality 151 +1. **Relevance Check** 152 +Reviewer verifies which scenarios the evidence applies to. 160 160 161 -=== Step 3: Evidence Review === 154 +1. **Reliability Assessment** 155 +* AKEL proposes reliability 156 +* Reviewer confirms 157 +* Expert review for complex papers 162 162 163 -** Reviewer/Expert Validates**:164 - * Accuracyofsummaries165 -* Appropriatenessofsources166 -* Completeness of contradictionsearch167 -* Reliabilityassessments159 +1. **ScenarioEvidenceLink Creation** 160 +Each link stores: 161 +* relevance score 162 +* justification 163 +* evidence version 168 168 169 -**Outcomes**: 170 -* **Mode 2**: Evidence summaries published as AI-generated 171 -* **Mode 3**: After human validation 172 -* **Mode 1**: Failed quality checks or pending expert review 165 +1. **Versioning** 166 +* Any update = new EvidenceVersion 173 173 168 +**Flow:** 169 +Submit → Extract Metadata → Evaluate Relevance → Score Reliability → Link → Version 170 + 174 174 ---- 175 175 176 -== Verdict GenerationWorkflow ==173 +== Verdict Workflow == 177 177 178 -=== Step 1: Verdict Computation === 175 +**Purpose:** 176 +Generate likelihood estimates per scenario based on evidence and scenario structure. 179 179 180 -**AKEL Computes**: 181 -* Verdict across scenarios 182 -* Confidence scores 183 -* Uncertainty quantification 184 -* Key assumptions 185 -* Limitations 178 +**Participants:** 179 +* AKEL (drafts) 180 +* Reviewer 181 +* Domain Expert 186 186 187 -**Inputs**: 188 -* Claim text 189 -* Scenario definitions 190 -* Evidence assessments 191 -* Contradiction search results 183 +=== Steps === 192 192 193 -=== Step 2: Verdict Validation === 185 +1. **Evidence Aggregation** 186 +Collect relevant evidence versions. 194 194 195 -**Quality Gates**: 196 -* All four gates apply (source, contradiction, uncertainty, structure) 197 -* Reasoning chain must be traceable 198 -* Assumptions must be explicit 188 +1. **Draft Verdict Generation (AKEL)** 189 +Outputs: 190 +* likelihood range 191 +* uncertainty factors 192 +* conflict detection 193 +* sensitivity analysis 199 199 200 -**Risk Tier Check**: 201 -* Tier A: Always requires expert validation for Mode 3 202 -* Tier B: Mode 2 allowed, audit sampling 203 -* Tier C: Mode 2 default 195 +1. **Reasoning Draft** 196 +Structured explanation chain generated by AKEL. 204 204 205 -=== Step 3: Verdict Publication === 198 +1. **Reviewer Validation** 199 +Ensures logic, evidence fit, no hallucinations. 206 206 207 -**Mode 2 (AI-Generated Verdict)**: 208 -* Clear labeling with confidence scores 209 -* Uncertainty disclosure 210 -* Links to reasoning trail 211 -* User can request expert review 201 +1. **Expert Review** 202 +Required for: 203 +* medicine 204 +* psychology 205 +* engineering 206 +* political misinformation 207 +* controversial or risky domains 212 212 213 -**Mode 3 (Expert-Validated Verdict)**: 214 -* Human reviewer/expert stamp 215 -* Additional commentary (optional) 216 -* Highest trust level 209 +1. **Verdict Storage** 210 +* Every update creates a new VerdictVersion 217 217 212 +**Flow:** 213 +Aggregate → Draft Verdict → Draft Explanation → Review → Expert Approval → Version 214 + 218 218 ---- 219 219 220 -== Audit Workflow ==217 +== Re-evaluation Workflow == 221 221 222 -=== Step 1: Audit Sampling Selection === 219 +**Purpose:** 220 +Keep verdicts current when evidence or scenarios change. 223 223 224 -**Stratified Sampling**: 225 -* Risk tier priority (A > B > C) 226 -* Low confidence scores 227 -* High traffic content 228 -* Novel topics 229 -* User flags 222 +=== Trigger Types === 230 230 231 -**Sampling Rates** (Recommendations): 232 -* Tier A: 30-50% 233 -* Tier B: 10-20% 234 -* Tier C: 5-10% 224 +* Evidence updated, disputed, retracted 225 +* Scenario assumptions changed 226 +* Claim reclassification 227 +* AKEL contradiction detection 228 +* Federation sync 235 235 236 -=== Step 2: Audit Execution===230 +=== Steps === 237 237 238 -**Auditor Actions**: 239 -1. Review sampled AI-generated content 240 -2. Validate quality gates were properly applied 241 -3. Check contradiction search completeness 242 -4. Assess reasoning quality 243 -5. Identify errors or hallucinations 232 +1. **Trigger Detection** 233 +Re-evaluation engine receives event. 244 244 245 -**Audit Outcome**: 246 -* **Pass**: Content remains in Mode 2, logged as validated 247 -* **Fail**: Content flagged for review, system improvement triggered 235 +1. **Impact Analysis** 236 +Find affected: 237 +* scenarios 238 +* evidence links 239 +* verdicts 248 248 249 -=== Step 3: Feedback Loop === 241 +1. **AKEL Draft Re-calculation** 242 +New: 243 +* likelihood 244 +* reasoning 245 +* uncertainty 250 250 251 -**System Improvements**: 252 -* Failed audits analyzed for patterns 253 -* AKEL parameters adjusted 254 -* Quality gates refined 255 -* Risk tier assignments recalibrated 247 +1. **Reviewer Validation** 248 +1. **Expert Review** (high-risk) 249 +1. **Version Storage** 256 256 257 -**Transparency**: 258 -* Audit statistics published periodically 259 -* Patterns shared with community 260 -* System improvements documented 251 +**Flow:** 252 +Trigger → Analyze → Recompute → Review → Expert → Version 261 261 262 262 ---- 263 263 264 -== ModeTransition Workflow ==256 +== Federation Synchronization Workflow == 265 265 266 -=== Mode 1 → Mode 2 === 258 +**Purpose:** 259 +Exchange structured data between nodes. 267 267 268 -**Requirements**: 269 -* All quality gates pass 270 -* Risk tier B or C (or A with warnings) 271 -* Contradiction search completed 261 +=== Steps === 262 +1. Detect version changes 263 +1. Build bundle (diff + Merkle tree + signatures) 264 +1. Push to peers 265 +1. Validate lineage + hashes 266 +1. Resolve conflicts (merge or branch) 267 +1. Optional re-evaluation 272 272 273 -**Trigger**: Automatic upon quality gate validation 269 +**Flow:** 270 +Change → Bundle → Push → Validate → Merge/Fork → Update 274 274 275 - === Mode 2 → Mode 3 ===272 +---- 276 276 277 -**Requirements**: 278 -* Human reviewer/expert validation 279 -* Quality standards confirmed 280 -* For Tier A: Expert approval required 281 -* For Tier B/C: Reviewer approval sufficient 274 +== User Role & Review Workflow == 282 282 283 -**Trigger**: Human review completion 276 +**Purpose:** 277 +Ensure correctness, neutrality, safety, and resistance to manipulation. 284 284 285 -=== Mode3 → Mode 1 (Demotion)===279 +=== Steps === 286 286 287 -**Rare - Only if**: 288 -* New evidence contradicts verdict 289 -* Error discovered in reasoning 290 -* Source retraction 281 +1. **Submission** 282 +Claim / scenario / evidence / verdict. 291 291 292 -**Process**: 293 -1. Content flagged for re-evaluation 294 -2. Moved to draft (Mode 1) 295 -3. Re-processed through workflow 296 -4. Reason for demotion documented 284 +1. **Auto-check (AKEL)** 285 +Flags unsafe content, contradictions, format issues. 297 297 298 - ----287 +1. **Reviewer Validation** 299 299 300 -== User Actions Across Modes == 289 +1. **Expert Validation** 290 +Required for sensitive domains. 301 301 302 -=== On Mode 1 (Draft) Content === 292 +1. **Moderator Oversight** 293 +Triggered by suspicious behavior. 303 303 304 -**Contributors**: 305 -* Edit their own drafts 306 -* Submit for review 295 +**Flow:** 296 +Submit → Auto-check → Review → Expert → Moderator (if needed) 307 307 308 -**Reviewers/Experts**: 309 -* View and comment 310 -* Request changes 311 -* Approve for Mode 2 or Mode 3 298 +---- 312 312 313 -== =OnMode 2 (AI-Generated) Content===300 +== AKEL Workflow == 314 314 315 -**All Users**: 316 -* Read and use content 317 -* Request human review 318 -* Flag for expert attention 319 -* Provide feedback 302 +**Purpose:** 303 +Support extraction, drafting, structuring, and contradiction detection. 320 320 321 -**Reviewers/Experts**: 322 -* Validate for Mode 3 transition 323 -* Edit and refine 324 -* Adjust risk tier if needed 305 +=== Stages === 325 325 326 -=== On Mode 3 (Human-Reviewed) Content === 307 +**A — Input Understanding:** 308 +Extraction, normalization, classification. 327 327 328 -**All Users**: 329 -* Read with highest confidence 330 -* Still can flag if new evidence emerges 310 +**B — Scenario Drafting:** 311 +Definitions, boundaries, assumptions. 331 331 332 -**Reviewers/Experts**: 333 -* Update if needed 334 -* Trigger re-evaluation if new evidence 313 +**C — Evidence Processing:** 314 +Retrieval, summarization, ranking. 335 335 336 ----- 316 +**D — Verdict Drafting:** 317 +Likelihood, explanations, uncertainties. 337 337 338 -== Diagram References == 319 +**E — Safety & Integrity:** 320 +Contradictions, hallucination detection. 339 339 340 -{{include reference="FactHarbor.Organisation.Diagrams.Claim-Scenario-Lifecycle"/}} 322 +**F — Human Approval:** 323 +Reviewer and/or expert. 341 341 342 -{{include reference="FactHarbor.Specification.Diagrams.Manual vs Automated matrix.WebHome"/}} 325 +**Flow:** 326 +Input → Drafts → Integrity → Human Approval 343 343 344 344 ---- 345 345 346 -== RelatedPages ==330 +== Global Trigger Flow (Cascade) == 347 347 348 -* [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]] 349 -* [[Automation>>FactHarbor.Specification.Automation.WebHome]] 350 -* [[Requirements (Roles)>>FactHarbor.Specification.Requirements.WebHome]] 351 -* [[Governance>>FactHarbor.Organisation.Governance]] 332 +Trigger Sources: 333 +* Claim change 334 +* Scenario change 335 +* Evidence change 336 +* Verdict contradiction 337 +* Federation update 338 +* AKEL model improvements 352 352 340 +**Cascade Flow:** 341 +Trigger → Dependency Graph → Re-evaluation → Updated Verdicts 342 +