Claim and Scenario Workflow

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

Claim & Scenario Workflow

This diagram shows how Claims and Scenarios are created and reviewed.

Claim & Scenario Creation

Claim Submission:

  • Contributors submit text
  • AKEL (Technical User) extracts claims automatically
  • Risk tier assigned (A/B/C)

Scenario Development:

  • Contributors propose interpretations
  • AKEL generates scenario drafts
  • Each claim has multiple scenarios

Review Process:

  • Reviewers validate claims and scenarios
  • Publication mode assigned (Mode 1/2/3)
  • Version history preserved
erDiagram
    CONTRIBUTOR {
        string UserID PK
    }
    
    TECHNICAL_USER {
        string SystemID PK
    }
    
    REVIEWER {
        string ReviewerID PK
    }
    
    CLAIM_VERSION {
        string VersionID PK
        string ClaimID FK
        string ParentVersionID FK
        string Text
        enum RiskTier "A,B,C"
        enum PublicationMode "Mode1,Mode2,Mode3"
        enum ReviewStatus
        string CreatedBy FK
        datetime CreatedAt
    }
    
    SCENARIO_VERSION {
        string VersionID PK
        string ScenarioID FK
        string ParentVersionID FK
        string ClaimID FK
        json Definitions
        json Assumptions
        enum PublicationMode
        enum ReviewStatus
        string CreatedBy FK
        datetime CreatedAt
    }
    
    CONTRIBUTOR ||--o{ CLAIM_VERSION : "submits"
    CONTRIBUTOR ||--o{ SCENARIO_VERSION : "proposes"
    TECHNICAL_USER ||--o{ CLAIM_VERSION : "generates"
    TECHNICAL_USER ||--o{ SCENARIO_VERSION : "drafts"
    REVIEWER ||--o{ CLAIM_VERSION : "reviews"
    REVIEWER ||--o{ SCENARIO_VERSION : "validates"
    CLAIM_VERSION ||--o{ SCENARIO_VERSION : "has-scenarios"