Changes for page Workflows

Last modified by Robert Schaub on 2025/12/24 20:34

From 3.1 to 4.1 From 5.1 to 6.1

From version 4.1

edited by Robert Schaub
on 2025/12/12 15:41

Change comment: Imported from XAR

To version 5.1

edited by Robert Schaub
on 2025/12/12 21:50

Change comment: Rollback to version 3.1

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -3,340 +3,125 @@
  This chapter defines the core workflows used across the FactHarbor system.
  Each workflow describes:
--
  * Purpose
  * Participants
  * Steps
  * Automation vs. manual work
--Workflows included:
++== 1. Claim Workflow ==
--1. Claim Workflow
--2. Scenario Workflow
--3. Evidence Workflow
--4. Verdict Workflow
--5. Re-evaluation Workflow
--6. Federation Synchronization Workflow
--7. User Role & Review Workflow
--8. AKEL Workflow
--9. Global Trigger Flow
--10. Entity Lifecycle Notes
++**Purpose:** Transform raw text or input material into a normalized, classified, deduplicated, and versioned claim.
------
++**Participants:**
++* Contributor
++* AKEL
++* Reviewer
--== Claim Workflow ==
++**Steps:**
++1. **Ingestion**: User submits text/URL; AKEL extracts claims.
++1. **Normalization**: Standardize wording, reduce ambiguity.
++1. **Classification**: Domain, Evaluability, Safety (AKEL draft → Human confirm).
++1. **Duplicate Detection**: Check embeddings for existing claims.
++1. **Version Creation**: Store new ClaimVersion.
++1. **Cluster Assignment**: Assign to Claim Cluster.
++1. **Scenario Linking**: Connect to existing or draft new scenarios.
++1. **Publication**: Make visible.
--**Purpose:**
--Transform raw text or input material into a normalized, classified, deduplicated, and versioned claim ready for scenario evaluation.
++**Flow:** Ingest → Normalize → Classify → Deduplicate → Cluster → Version → Publish
--**Participants:**
--* Contributor
--* AKEL
--* Reviewer
++== 2. Scenario Workflow ==
--=== Steps ===
++**Purpose:** Define the specific analytic contexts needed to evaluate each claim.
--1. **Ingestion**
--* User submits text, URL, transcript, or multi-claim content
--* AKEL extracts one or multiple claims
++**Steps:**
++1. **Scenario Proposal**: Drafted by contributor or AKEL.
++1. **Required Fields**: Definitions, Assumptions, ContextBoundary, EvaluationMethod, SafetyClass.
++1. **Safety Interception**: AKEL flags non-falsifiable or unsafe content.
++1. **Conflict Check**: Merge similar scenarios, flag contradictions.
++1. **Reviewer Validation**: Ensure clarity and validity.
++1. **Expert Approval**: Mandatory for high-risk domains.
++1. **Version Storage**: Save ScenarioVersion.
--1. **Normalization**
--* Standardizes wording
--* Reduces ambiguity
--* Flags implicit assumptions
++**Flow:** Draft → Validate → Safety Check → Review → Expert → Version → Activate
--1. **Classification (AKEL draft → Reviewer confirm)**
--* ClaimType
--* Domain
--* Evaluability
--* SafetyCategory
++== 3. Evidence Workflow ==
--1. **Duplicate & Similarity Detection**
--* Embeddings created
--* Similar claims found
--* Reviewer merges, splits, or confirms uniqueness
++**Purpose:** Structure, classify, validate, version, and link evidence to scenarios.
--1. **Version Creation**
--* New ClaimVersion stored
--* Every edit creates a new immutable version
++**Steps:**
++1. **Submission**: File, URL, or text.
++1. **Metadata Extraction**: Type, Category, Provenance, ReliabilityHints.
++1. **Relevance Check**: Verify applicability to scenario.
++1. **Reliability Assessment**: Score reliability (Reviewer + Expert).
++1. **Link Creation**: Create ScenarioEvidenceLink with relevance score.
++1. **Versioning**: Update EvidenceVersion.
--1. **Cluster Assignment**
--* AKEL proposes cluster membership
--* Reviewer confirms
++**Flow:** Submit → Extract → Relevance → Reliability → Link → Version
--1. **Scenario Linking (optional)**
--* Existing scenarios connected
--* AKEL may propose new drafts
++== 4. Verdict Workflow ==
--1. **Publication**
--* Claim becomes active and visible
++**Purpose:** Generate likelihood estimates **per scenario** based on evidence.
--**Flow:**
--Ingest → Normalize → Classify → Deduplicate → Cluster → Version → Publish
++**Steps:**
++1. **Aggregation**: Collect linked evidence for a specific scenario.
++1. **Draft Verdict**: AKEL proposes likelihood and uncertainty for that scenario.
++1. **Reasoning**: AKEL drafts explanation chain.
++1. **Validation**: Reviewer checks logic and hallucinations.
++1. **Expert Review**: Required for sensitive topics.
++1. **Storage**: Save VerdictVersion.
------
++**Flow:** Aggregate → Draft → Reasoning → Review → Expert → Version
--== Scenario Workflow ==
++== 5. Re-evaluation Workflow ==
--**Purpose:**
--Define the specific analytic contexts needed to evaluate each claim.
++**Purpose:** Keep verdicts current when inputs change.
--**Participants:**
--* Contributor
--* Reviewer
--* Domain Expert
--* AKEL
++**Steps:**
++1. **Trigger**: Evidence update, Scenario change, or Contradiction.
++1. **Impact Analysis**: Identify affected nodes.
++1. **Re-calculation**: AKEL proposes new likelihoods.
++1. **Validation**: Human review.
++1. **Storage**: New version.
--=== Steps ===
++**Flow:** Trigger → Analyze → Recompute → Review → Version
--1. **Scenario Proposal**
--* Drafted by contributor or generated by AKEL
++== 6. Federation Synchronization Workflow ==
--1. **Completion of Required Fields**
--Must include:
--* Definitions
--* Assumptions
--* ContextBoundary
--* EvaluationMethod
--* SafetyClass
--* VersionMetadata
++**Purpose:** Exchange structured data between nodes.
--1. **Safety Interception (AKEL)**
--Flags:
--* non-falsifiable structures
--* pseudoscientific assumptions
--* unsafe contexts
++**Steps:**
++1. Detect Version Changes.
++1. Build Signed Bundle (Merkle tree).
++1. Push/Pull to Peers.
++1. Validate Signatures & Lineage.
++1. Resolve Conflicts (Merge/Fork).
++1. Trigger Re-evaluation.
--1. **Redundancy & Conflict Check**
--* Similar scenarios merged
--* Contradictions flagged
++== 7. User Role & Review Workflow ==
--1. **Reviewer Validation**
--Ensures clarity, neutrality, and methodological validity.
++**Purpose:** Ensure correctness and safety.
--1. **Expert Approval (mandatory for high-risk domains)**
++**Steps:**
++1. Submission.
++1. Auto-check (AKEL).
++1. Reviewer Validation.
++1. Expert Validation (if needed).
++1. Moderator Oversight (if flagged).
--1. **Version Storage**
--* Each revision = new ScenarioVersion
++== 8. AKEL Workflow ==
--**Flow:**
--Draft → Validate → Safety Check → Review → Expert Approval → Version → Activate
++**Stages:**
++* Input Understanding
++* Scenario Drafting
++* Evidence Processing
++* Verdict Drafting
++* Safety & Integrity
++* Human Approval
------
++== 9. Global Trigger Flow (Cascade) ==
--== Evidence Workflow ==
++**Sources:** Claim/Scenario/Evidence change, Verdict contradiction, Federation update.
--**Purpose:**
--Structure, classify, validate, version, and link evidence to scenarios.
++**Flow:** Trigger → Dependency Graph → Re-evaluation → Updated Verdicts
--**Participants:**
--* Contributor
--* Reviewer
--* Domain Expert
--* AKEL
--
--=== Steps ===
--
--1. **Evidence Submission**
--* File, dataset, URL, or extracted text
--
--1. **Metadata Extraction (AKEL)**
--* EvidenceType
--* Category
--* Provenance
--* Study design
--* ExtractionMethod
--* ReliabilityHints
--
--1. **Relevance Check**
--Reviewer verifies which scenarios the evidence applies to.
--
--1. **Reliability Assessment**
--* AKEL proposes reliability
--* Reviewer confirms
--* Expert review for complex papers
--
--1. **ScenarioEvidenceLink Creation**
--Each link stores:
--* relevance score
--* justification
--* evidence version
--
--1. **Versioning**
--* Any update = new EvidenceVersion
--
--**Flow:**
--Submit → Extract Metadata → Evaluate Relevance → Score Reliability → Link → Version
--
------
--
--== Verdict Workflow ==
--
--**Purpose:**
--Generate likelihood estimates per scenario based on evidence and scenario structure.
--
--**Participants:**
--* AKEL (drafts)
--* Reviewer
--* Domain Expert
--
--=== Steps ===
--
--1. **Evidence Aggregation**
--Collect relevant evidence versions.
--
--1. **Draft Verdict Generation (AKEL)**
--Outputs:
--* likelihood range
--* uncertainty factors
--* conflict detection
--* sensitivity analysis
--
--1. **Reasoning Draft**
--Structured explanation chain generated by AKEL.
--
--1. **Reviewer Validation**
--Ensures logic, evidence fit, no hallucinations.
--
--1. **Expert Review**
--Required for:
--* medicine
--* psychology
--* engineering
--* political misinformation
--* controversial or risky domains
--
--1. **Verdict Storage**
--* Every update creates a new VerdictVersion
--
--**Flow:**
--Aggregate → Draft Verdict → Draft Explanation → Review → Expert Approval → Version
--
------
--
--== Re-evaluation Workflow ==
--
--**Purpose:**
--Keep verdicts current when evidence or scenarios change.
--
--=== Trigger Types ===
--
--* Evidence updated, disputed, retracted
--* Scenario assumptions changed
--* Claim reclassification
--* AKEL contradiction detection
--* Federation sync
--
--=== Steps ===
--
--1. **Trigger Detection**
--Re-evaluation engine receives event.
--
--1. **Impact Analysis**
--Find affected:
--* scenarios
--* evidence links
--* verdicts
--
--1. **AKEL Draft Re-calculation**
--New:
--* likelihood
--* reasoning
--* uncertainty
--
--1. **Reviewer Validation**
--1. **Expert Review** (high-risk)
--1. **Version Storage**
--
--**Flow:**
--Trigger → Analyze → Recompute → Review → Expert → Version
--
------
--
--== Federation Synchronization Workflow ==
--
--**Purpose:**
--Exchange structured data between nodes.
--
--=== Steps ===
--1. Detect version changes
--1. Build bundle (diff + Merkle tree + signatures)
--1. Push to peers
--1. Validate lineage + hashes
--1. Resolve conflicts (merge or branch)
--1. Optional re-evaluation
--
--**Flow:**
--Change → Bundle → Push → Validate → Merge/Fork → Update
--
------
--
--== User Role & Review Workflow ==
--
--**Purpose:**
--Ensure correctness, neutrality, safety, and resistance to manipulation.
--
--=== Steps ===
--
--1. **Submission**
--Claim / scenario / evidence / verdict.
--
--1. **Auto-check (AKEL)**
--Flags unsafe content, contradictions, format issues.
--
--1. **Reviewer Validation**
--
--1. **Expert Validation**
--Required for sensitive domains.
--
--1. **Moderator Oversight**
--Triggered by suspicious behavior.
--
--**Flow:**
--Submit → Auto-check → Review → Expert → Moderator (if needed)
--
------
--
--== AKEL Workflow ==
--
--**Purpose:**
--Support extraction, drafting, structuring, and contradiction detection.
--
--=== Stages ===
--
--**A — Input Understanding:**
--Extraction, normalization, classification.
--
--**B — Scenario Drafting:**
--Definitions, boundaries, assumptions.
--
--**C — Evidence Processing:**
--Retrieval, summarization, ranking.
--
--**D — Verdict Drafting:**
--Likelihood, explanations, uncertainties.
--
--**E — Safety & Integrity:**
--Contradictions, hallucination detection.
--
--**F — Human Approval:**
--Reviewer and/or expert.
--
--**Flow:**
--Input → Drafts → Integrity → Human Approval
--
------
--
--== Global Trigger Flow (Cascade) ==
--
--Trigger Sources:
--* Claim change
--* Scenario change
--* Evidence change
--* Verdict contradiction
--* Federation update
--* AKEL model improvements
--
--**Cascade Flow:**
--Trigger → Dependency Graph → Re-evaluation → Updated Verdicts
--
++{{include reference="FactHarbor.Specification.Diagrams.Global Trigger Cascade.WebHome"/}}

Changes for page Workflows

Summary

Details

Applications

Navigation

Need help?