🔄 Riksdagsmonitor — State Diagrams

🎭 System Behavior and State Transitions for Democratic Transparency
📊 Lifecycle Management · Workflow States · AI-Driven Processes

📋 Document Owner: CEO | 📄 Version: 1.2 | 📅 Last Updated: 2026-05-06 (UTC)
🔄 Review Cycle: Quarterly | ⏰ Next Review: 2026-08-06
🏢 Owner: Hack23 AB (Org.nr 5595347807) | 🏷️ Classification: Public

Executive Summary

This document illustrates the key state transitions and behavioral models within the Riksdagsmonitor platform. These diagrams provide a comprehensive view of how system components change states in response to user interactions, data updates, workflow executions, and automated processes. All state models align with Hack23 AB's AI Policy and Secure Development Policy.

📚 Architecture Documentation Map

1. 📰 News Article Lifecycle States

📊 Data Focus: Illustrates how news articles flow from generation to publication across 14 languages.

🔄 Process Focus: Shows state transitions as articles are generated, translated, validated, reviewed, and published.

🤖 AI Integration: Agentic workflows (Copilot + riksdag-regering-mcp) generate and translate content with human oversight.

stateDiagram-v2
    [*] --> Draft
    
    Draft --> Translation: Content Generated
    Draft --> Error: Generation Failed
    
    Translation --> Validation: All Languages Complete
    Translation --> TranslationFailed: AI Hallucination/Context Loss
    
    Validation --> Review: All Checks Passed
    Validation --> ValidationFailed: data-translate Markers Remain
    
    Review --> Approved: Human Approval
    Review --> Rejected: Changes Requested
    
    Approved --> Published: PR Merged
    
    Published --> Rollback: Production Issue
    Published --> [*]
    
    TranslationFailed --> Draft: Retry Translation
    ValidationFailed --> Translation: Fix Translations
    Rejected --> Draft: Revise Content
    Error --> Draft: Fix and Retry
    Rollback --> Draft: Recreate Article
    
    note right of Draft
        Article generated by Copilot agent
        Swedish content from riksdag-regering-mcp
        data-translate markers added
    end note
    
    note right of Translation
        Multi-language translation (14 languages)
        EN, SV, DA, NO, FI, DE, FR, ES
        NL, AR, HE, JA, KO, ZH
    end note
    
    note right of Validation
        scripts/validate-news-translations.js
        Exit 0: All translations complete
        Exit 1: Markers detected
    end note
    
    note right of Published
        Deployed to production
        Immutable state
        Cannot transition back to DRAFT
    end note
Copy

1.1 State Definitions

1.2 State Transition Matrix

1.3 State Invariants

• PUBLISHED → DRAFT: ❌ BLOCKED - Published articles are immutable (cannot revert to draft)
• VALIDATION_FAILED → PUBLISHED: ❌ BLOCKED - Cannot publish with untranslated markers
• ERROR → PUBLISHED: ❌ BLOCKED - Must resolve errors before publishing
• DRAFT → PUBLISHED: ❌ BLOCKED - Must pass through TRANSLATION → VALIDATION → REVIEW → APPROVED
• TRANSLATION → REVIEW: ❌ BLOCKED - Must validate first

1.4 Error State Handling

2. 🤖 Agentic Workflow States

📊 Data Focus: GitHub Actions workflows executing Copilot agents with MCP server integration.

🔄 Process Focus: Shows workflow lifecycle from scheduling through deployment.

🤖 AI Integration: Limited Risk AI system per Hack23 AI Policy requiring human oversight.

stateDiagram-v2
    [*] --> Queued
    
    Queued --> Running: Workflow Starts
    Queued --> Cancelled: Manual Cancellation
    
    Running --> Generating: Copilot Agent Active
    
    Generating --> Translating: Content Generated
    Generating --> HallucinationDetected: AI Error Detected
    
    Translating --> Validating: Translation Complete
    Translating --> TranslationError: Translation Failed
    
    Validating --> Success: All Checks Passed
    Validating --> Failure: Validation Failed
    
    Success --> PRCreated: Pull Request Opened
    
    PRCreated --> PRReview: Awaiting Review
    
    PRReview --> Merged: PR Approved & Merged
    PRReview --> Closed: PR Rejected/Cancelled
    
    Merged --> Deployed: Deployment Complete
    Deployed --> [*]
    
    HallucinationDetected --> Failure
    TranslationError --> Failure
    Failure --> Logged: Error Logged
    Logged --> [*]
    Closed --> [*]
    Cancelled --> [*]
    
    note right of Queued
        Scheduled or manual trigger
        Awaiting GitHub Actions runner
    end note
    
    note right of Generating
        Copilot agent queries riksdag-regering-mcp
        Generates Swedish content
        Real-time monitoring active
    end note
    
    note right of HallucinationDetected
        AI-specific error state
        Prompt injection detection
        Context drift monitoring
    end note
    
    note right of PRReview
        Human oversight required
        Limited Risk AI system
        MUST review before merge
    end note
Copy

2.1 State Definitions

2.2 State Transition Matrix

2.3 AI-Specific States (Hack23 AI Policy Compliance)

2.4 Workflow Coordination

Shared State File: workflow-state.json

{
  "lastUpdate": "2026-02-15T15:30:00Z",
  "recentArticles": [
    {
      "slug": "2026-02-15-week-ahead-en.html",
      "timestamp": "2026-02-15T15:25:00Z",
      "workflow": "news-week-ahead",
      "title": "Week Ahead in Swedish Parliament",
      "topics": ["parliament", "schedule", "committees"]
    }
  ],
  "mcpQueryCache": {
    "hash123": {
      "query": "recent motions",
      "result": {...},
      "timestamp": "2026-02-15T14:00:00Z"
    }
  },
  "workflows": {
    "news-week-ahead": {
      "lastRun": "2026-02-15T05:51:00Z",
      "status": "success",
      "articles": 1
    },
    "news-evening-analysis": {
      "lastRun": "2026-02-14T18:00:00Z",
      "status": "success",
      "articles": 1
    },
    "news-realtime-monitor": {
      "lastRun": "2026-02-15T14:00:00Z",
      "status": "success",
      "articles": 2
    }
  }
}
Copy

3. 📊 Dashboard Data States

📊 Data Focus: LocalStorage-based caching for CIA dashboard exports and Riksdag data.

🔄 Process Focus: Shows data lifecycle from initial fetch through refresh cycles.

⚡ Performance Focus: Minimizes API calls while maintaining data freshness.

stateDiagram-v2
    [*] --> Empty
    
    Empty --> Fetching: Initial Load
    
    Fetching --> Cached: Fetch Success
    Fetching --> Error: Fetch Failed
    
    Cached --> Stale: Freshness Threshold Exceeded
    Cached --> [*]: User Exits
    
    Stale --> Refreshing: Background Refresh
    Stale --> Cached: Use Stale Data
    
    Refreshing --> Cached: Refresh Success
    Refreshing --> Error: Refresh Failed
    
    Error --> Fetching: Retry
    Error --> Cached: Fallback to Stale Cache
    Error --> [*]: Max Retries Exceeded
    
    note right of Empty
        No cached data
        First visit or cache cleared
    end note
    
    note right of Cached
        Valid cached data
        Within freshness threshold
        Served instantly from LocalStorage
    end note
    
    note right of Stale
        Cached data expired
        Still usable as fallback
        Background refresh triggered
    end note
    
    note right of Error
        Network failure
        API unavailable
        Fallback to stale cache if available
    end note
Copy

3.1 State Definitions

3.2 Freshness Thresholds

3.3 State Transition Matrix

3.4 Cache Strategy

LocalStorage Schema:

{
  "riksdagsmonitor_cache": {
    "production_stats": {
      "data": {...},
      "timestamp": "2026-02-15T15:30:00Z",
      "version": "1.0"
    },
    "seasonal_patterns": {
      "data": {...},
      "timestamp": "2026-02-10T10:00:00Z",
      "version": "1.0"
    },
    "politician_data": {
      "data": {...},
      "timestamp": "2026-02-15T14:00:00Z",
      "version": "1.0"
    }
  }
}
Copy

Freshness Check Algorithm:

function isFresh(cachedItem, thresholdHours) {
  const now = new Date();
  const cached = new Date(cachedItem.timestamp);
  const ageHours = (now - cached) / (1000 * 60 * 60);
  return ageHours < thresholdHours;
}
Copy

4. 🔀 Pull Request Review States

📊 Data Focus: PR lifecycle from creation through deployment.

🔄 Process Focus: Shows review workflow with quality gates and human approval.

🔒 Security Focus: All checks must pass before merge.

stateDiagram-v2
    [*] --> Open
    
    Open --> Draft: Mark as Draft
    Open --> CIRunning: CI Triggered
    
    Draft --> Open: Ready for Review
    
    CIRunning --> CIPassed: All Checks Pass
    CIRunning --> CIFailed: Quality Gate Failed
    
    CIPassed --> ReviewRequested: Assign Reviewer
    
    CIFailed --> Open: Fix Issues
    
    ReviewRequested --> ChangesRequested: Feedback Provided
    ReviewRequested --> Approved: Review Approved
    
    ChangesRequested --> Open: Push Updates
    
    Approved --> ReviewDismissed: New Commits Pushed
    Approved --> MergeReady: All Requirements Met
    
    ReviewDismissed --> ReviewRequested: Re-request Review
    
    MergeReady --> Merged: Merge Button Clicked
    
    Merged --> Deployed: GitHub Pages Deployment
    Deployed --> [*]
    
    Open --> Closed: Close without Merge
    Draft --> Closed: Abandon Draft
    Closed --> [*]
    
    note right of CIRunning
        HTMLHint validation
        Link checking (linkinator)
        JavaScript linting (ESLint)
        Dependency scanning
        Secret scanning
    end note
    
    note right of MergeReady
        All checks passed
        Approved by reviewer
        No merge conflicts
        Branch up to date
    end note
    
    note right of Deployed
        GitHub Pages updated
        CDN cache invalidated
        Production monitoring active
    end note
Copy

4.1 State Definitions

4.2 Quality Gates (CI Checks)

4.3 State Transition Matrix

4.4 Merge Requirements Checklist

Before transition to MERGE_READY state, ALL must be true:

• ✅ All CI checks passed (HTML, links, security)
• ✅ At least 1 approval from reviewer
• ✅ No merge conflicts with base branch
• ✅ Branch is up to date with base
• ✅ No requested changes pending
• ✅ No critical security vulnerabilities detected
• ✅ All required status checks passed

5. 🚀 CI/CD Pipeline States

📊 Data Focus: Deployment pipeline from commit to production monitoring.

🔄 Process Focus: Shows build, test, security scan, and deployment workflow.

🔒 Security Focus: Multiple security gates (CodeQL, Dependabot, secret scanning).

stateDiagram-v2
    [*] --> Commit
    
    Commit --> Build: Trigger CI/CD
    
    Build --> Test: Build Success
    Build --> Failed: Build Error
    
    Test --> Scan: Tests Passed
    Test --> Failed: Test Failures
    
    Scan --> DeployStaging: Security Checks Passed
    Scan --> Vulnerable: Critical Vulnerability Detected
    
    Vulnerable --> Failed: Block Deployment
    
    DeployStaging --> HealthCheck: Staging Deployed
    DeployStaging --> Failed: Deployment Error
    
    HealthCheck --> DeployProduction: Health Check Passed
    HealthCheck --> Unhealthy: Health Check Failed
    
    Unhealthy --> Rollback: Critical Issue
    
    DeployProduction --> Monitor: Production Deployed
    DeployProduction --> Failed: Deployment Error
    
    Monitor --> ErrorsDetected: Production Errors
    Monitor --> [*]: Stable
    
    ErrorsDetected --> Rollback: Critical Errors
    ErrorsDetected --> Monitor: Minor Errors (Log & Monitor)
    
    Rollback --> Commit: Revert & Fix
    Failed --> Commit: Fix & Retry
    
    note right of Build
        Vite build executing
        Asset optimization
        HTML/CSS/JS bundling
    end note
    
    note right of Scan
        CodeQL security scan
        Dependabot vulnerability check
        Secret scanning
        License compliance
    end note
    
    note right of DeployProduction
        GitHub Pages deployment
        AWS CloudFront cache invalidation
        Multi-region S3 sync
    end note
    
    note right of Monitor
        Uptime monitoring
        Performance metrics (Core Web Vitals)
        Error tracking
        User analytics
    end note
Copy

5.1 State Definitions

5.2 Security Scanning Gates

5.3 State Transition Matrix

5.4 Deployment Targets

5.5 Health Check Criteria

Staging Health Checks:

• ✅ HTTP 200 response for index.html
• ✅ All 14 language versions accessible
• ✅ CSS/JS assets loading
• ✅ No console errors
• ✅ Links resolve correctly

Production Health Checks:

• ✅ All staging checks
• ✅ CloudFront cache serving correctly
• ✅ S3 replication complete
• ✅ Core Web Vitals within targets (LCP < 2.5s, FID < 100ms, CLS < 0.1)
• ✅ Uptime monitoring active

6. 🌐 Translation Validation States

📊 Data Focus: Multi-language content validation lifecycle.

🔄 Process Focus: Shows translation workflow from marking through publishing.

🤖 AI Integration: Agentic translation with automated validation.

stateDiagram-v2
    [*] --> Untranslated
    
    Untranslated --> Skip: Content Exempt
    Untranslated --> Marked: data-translate Markers Added
    
    Marked --> Translating: Agentic Translation Started
    
    Translating --> Translated: All Languages Complete
    Translating --> Failed: Translation Error
    
    Translated --> Validated: Validation Script Passed
    Translated --> Invalid: Markers Remain
    
    Failed --> Retrying: Retry Translation
    Retrying --> Translating: Retry Attempt
    Retrying --> Failed: Max Retries Exceeded
    
    Invalid --> Translating: Fix Translations
    
    Validated --> Published: Clean Content Deployed
    
    Published --> Rollback: Production Issue
    Published --> [*]
    
    Rollback --> Untranslated: Recreate Content
    Skip --> Published: Exempt Content
    
    note right of Marked
        Swedish API content wrapped
        <span data-translate="true" lang="sv">
        14 language versions needed
    end note
    
    note right of Translating
        Copilot agent translating
        EN, SV, DA, NO, FI, DE, FR, ES
        NL, AR, HE, JA, KO, ZH
    end note
    
    note right of Validated
        scripts/validate-news-translations.js
        Exit code 0 (success)
        No markers remaining
    end note
    
    note right of Published
        Clean translated content live
        No data-translate markers
        All languages accessible
    end note
Copy

6.1 State Definitions

6.2 Translation Validation Script

Tool: scripts/validate-news-translations.js

Purpose: Detects remaining data-translate="true" markers in non-Swedish articles

Exit Codes:

• 0 - Success: All articles fully translated
• 1 - Failure: Untranslated markers found

Usage:

# Validate all news articles
npm run validate-news

# Check specific directory
node scripts/validate-news-translations.js news/
Copy

Sample Output (Failure):

📋 NEWS TRANSLATION VALIDATION

✓ Fully translated: 142
✗ Needs translation: 3

Untranslated Articles:
  ✗ 2026-02-15-committee-reports-de.html - 10 markers
    Samples:
      1. "Bättre förutsättningar att sända ut statlig personal"
      2. "Ett register för alla bostadsrätter"
  
Action Required:
1. Open each file listed above
2. Find all <span data-translate="true" lang="sv">Swedish text</span> elements
3. Translate the Swedish text to the article's target language
4. Replace the span with plain translated text
5. Consult TRANSLATION_GUIDE.md for terminology
Copy

6.3 State Transition Matrix

6.4 Translation Marker Format

Swedish Content (Needs Translation):

<p>
  The committee proposes 
  <span data-translate="true" lang="sv">bättre förutsättningar för statlig personal</span> 
  in the budget.
</p>
Copy

Translated Content (Clean):

<p>
  The committee proposes better conditions for government personnel in the budget.
</p>
Copy

6.5 Language Support Matrix

6.6 Retry Logic

Translation Retry Policy:

• Max Attempts: 3
• Backoff Strategy: Exponential (5 min, 10 min, 20 min)
• Retry Triggers: AI hallucination, context loss, network error
• Manual Intervention: After 3 failed attempts

Validation Retry Policy:

• Max Attempts: Unlimited (automatic retry after fixes)
• Backoff Strategy: None (immediate re-validation)
• Retry Triggers: Markers detected, validation script exit 1
• Manual Intervention: If markers persist after 3 translation attempts

6A. 📦 Analysis Artifact Lifecycle States

📊 Data Focus: 23 analysis artifacts (Families A-D) produced by every agentic news workflow.

🔄 Process Focus: Shows artifact folder lifecycle from creation through consumption by article rendering.

🤖 AI Integration: Artifacts are produced by Copilot agents and validated by scripts/agentic/analysis-gate.ts.

stateDiagram-v2
    [*] --> Empty
    
    Empty --> Populating: Agentic workflow starts writing artifacts
    
    Populating --> Populated: All 23 artifacts written
    Populating --> Incomplete: Timeout or agent error
    
    Populated --> GateChecking: analysis-gate.ts invoked
    
    GateChecking --> GatePassed: All checks 1-9b pass
    GateChecking --> GateFailed: One or more checks fail
    
    GateFailed --> Populating: Agent retries failed artifacts
    
    GatePassed --> Consumed: render-articles.ts reads artifacts
    
    Consumed --> Archived: Article published, artifacts retained
    Archived --> [*]
    
    Incomplete --> [*]: Workflow terminates with error
    
    note right of Empty
        analysis/daily/YYYY-MM-DD/type/ folder
        23 expected files (Families A-D)
    end note
    
    note right of GateChecking
        Check 1: Artifact existence (23 files)
        Check 2: No stub placeholders
        Check 3: Minimum word count
        Check 4: Evidence citations
        Check 5: Mermaid diagrams with colour
        Check 6: Pass-2 evidence (revision proof)
        Check 7: Cross-references
        Check 8: Data-source connectivity audit
        Check 9a: Political classification
        Check 9b: Agency evidence (Statskontoret)
    end note
    
    note right of Consumed
        aggregate-analysis.ts aggregates
        render-articles.ts renders HTML
        Artifacts become read-only
    end note
Copy

6A.1 State Definitions

6B. 🕵️ Political Intelligence Assessment States

📊 Data Focus: Intelligence assessment lifecycle for political analysis products.

🔄 Process Focus: Shows the intelligence cycle from collection through dissemination and feedback.

🤖 AI Integration: Horizon stratification (T+72h → T+1460d) drives assessment scope and confidence levels.

stateDiagram-v2
    [*] --> Collection
    
    Collection --> Processing: Raw data gathered
    
    Processing --> Analysis: Data cleaned and structured
    
    Analysis --> Assessment: Analytical products created
    
    Assessment --> Dissemination: Confidence labels assigned
    
    Dissemination --> Feedback: Published to audience
    
    Feedback --> Collection: New requirements identified
    Feedback --> [*]: Cycle complete
    
    Collection --> Collection: Continuous monitoring
    
    note right of Collection
        Sources: Riksdag MCP (32 tools)
        SCB statistics, IMF economic data
        Government documents, voting records
    end note
    
    note right of Analysis
        20 methodologies applied
        39 analysis templates used
        Horizon-specific framing:
        T+72h, T+7d, T+30d, T+90d, T+365d, T+1460d
    end note
    
    note right of Assessment
        Confidence levels: High/Medium/Low
        WEP language ladder per horizon band
        Scenario analysis (≥3 scenarios)
    end note
    
    note right of Dissemination
        14 languages, RTL support
        Article rendering pipeline
        RSS, sitemap, indexes generated
    end note
Copy

6B.1 State Definitions

6B.2 Horizon Stratification

7. 📊 State Metrics and Monitoring

7.1 Time in State (Average Duration)

7.2 State Transition Frequency Matrix

Top 10 Most Frequent Transitions (Weekly):

7.3 Error Rates (Failed Transitions)

7.4 Bottleneck Analysis

States with Long P95 Durations:

7.5 Monitoring Dashboards

Key Metrics to Track:

1. Article Generation Success Rate: % of workflows reaching PUBLISHED state
2. Translation Quality: % of articles passing validation on first attempt
3. Review Turnaround Time: Time from REVIEW → APPROVED
4. Cache Hit Rate: % of dashboard requests served from CACHED state
5. CI/CD Success Rate: % of commits reaching DEPLOYED state
6. Production Uptime: Time in MONITOR state without errors
7. Rollback Frequency: Number of ROLLBACK events per week

7.6 Alerting Thresholds

8. 🔒 Security and Compliance

8.1 AI Policy Compliance (Hack23 AI Policy)

Limited Risk AI System Classification:

• ✅ Human oversight required (PR_REVIEW state)
• ✅ AI-specific states documented (HALLUCINATION_DETECTED, TRANSLATION_ERROR)
• ✅ Audit logs maintained (LOGGED state, workflow history)
• ✅ Error detection and recovery (automatic retries, rollback procedures)
• ✅ Transparency (state transitions visible in PRs and logs)

AI Risk Controls:

8.2 State Invariants for Security

Security-Critical Invariants:

1. VULNERABLE → DEPLOY_PRODUCTION: ❌ BLOCKED - Cannot deploy with critical vulnerabilities
2. VALIDATION_FAILED → PUBLISHED: ❌ BLOCKED - Cannot publish untranslated content
3. CI_FAILED → MERGED: ❌ BLOCKED - Cannot merge with failing checks
4. HALLUCINATION_DETECTED → PUBLISHED: ❌ BLOCKED - Cannot publish AI errors without review
5. ERROR → DEPLOYED: ❌ BLOCKED - Cannot deploy failed builds

8.3 Audit Trail Requirements

All state transitions MUST be logged with:

• ✅ Timestamp (ISO 8601 format)
• ✅ From State
• ✅ To State
• ✅ Triggering Event
• ✅ Actor (user, system, AI agent)
• ✅ Conditions Met (or failed)
• ✅ Actions Taken
• ✅ Outcome (success/failure)

Retention Policy: 90 days for operational logs, 7 years for compliance logs

9. 🔄 Integration with Other Documentation

9.1 Cross-References

9.2 Architecture Component State Mapping

9.3 Workflow Execution State Mapping

10. 📈 Future Enhancements

10.1 Planned State Additions

Enhanced AI Monitoring:

• CONFIDENCE_SCORE_LOW - AI-generated content below confidence threshold
• HUMAN_OVERRIDE_REQUIRED - Manual intervention needed
• AI_EXPLANATION_GENERATED - AI provides reasoning for decisions

Advanced Caching:

• PREFETCHING - Proactive cache warming
• CACHE_INVALIDATION - Explicit cache clearing
• MULTI_REGION_SYNC - Cross-region cache synchronization

Deployment Optimization:

• CANARY_DEPLOYMENT - Gradual rollout to subset of users
• BLUE_GREEN_DEPLOYMENT - Zero-downtime deployments
• FEATURE_FLAG_EVALUATION - Dynamic feature enablement

10.2 Monitoring Improvements

• Real-time state transition dashboard (Grafana)
• Machine learning-based anomaly detection for state durations
• Predictive analytics for workflow success rates
• Automated bottleneck identification and alerts

10.3 Automation Opportunities

• Auto-retry for transient failures (network, API timeouts)
• Smart cache preloading based on user behavior patterns
• Automated rollback on production error thresholds
• Self-healing workflows for common failure scenarios

📚 Architecture Documentation Map

Hack23 ISMS Policies

• 🛡️ Secure Development Policy — Architecture documentation requirements
• 🏷️ Classification Framework — CIA triad classification

📋 Document Control:
✅ Approved by: James Pether Sörling, CEO
📤 Distribution: Public
🏷️ Classification:
📅 Effective Date: 2026-02-15
⏰ Next Review: 2026-05-15
🎯 Framework Compliance:

🌐 IMF Cache & Vintage State Machine (Current State)

Status: ✅ Implemented and in production. The IMF cache lives in analysis/imf/ (canonical hub) and analysis/daily/*/economic-data.json (per-article vintage cache). Every cache row is vintage-tagged and SHA-256 pinned. Authority: .github/aw/ECONOMIC_DATA_CONTRACT.md v2.1.

IMF cache row lifecycle

stateDiagram-v2
    [*] --> Empty: cache key absent
    Empty --> Fetching: news-* worker requests dataflow/indicator/country
    Fetching --> Fresh: payload <=6 months old · SHA-256 pinned
    Fetching --> Stale: payload >6 months old
    Fetching --> RateLimited: HTTP 429
    Fetching --> Failed: HTTP 5xx / timeout
    Fresh --> Used: article cites with full confidence
    Stale --> Annotated: staleness_annotated=true required
    Annotated --> Used: article cites with downgraded confidence
    RateLimited --> Backoff: exponential 2^n seconds
    Backoff --> Fetching: retry
    Failed --> CacheFallback: serve last cached vintage
    CacheFallback --> Used: article cites with cache-fallback annotation
    Used --> [*]
Copy

WEO vintage transition (April → October cycle, current behaviour)

stateDiagram-v2
    [*] --> WEO_2026_04: April WEO published; cached
    WEO_2026_04 --> WEO_2026_10: October WEO published (supersedes pointer set)
    WEO_2026_04 --> Archived: superseded; preserved for audit-trail
    WEO_2026_10 --> WEO_2027_04: April 2027 WEO publishes
    WEO_2026_10 --> Archived
    Archived --> [*]: never deleted (provenance integrity)
Copy

Current production guarantees:

• Vintage label format YYYY-MM enforced by tests/imf-inventory.test.ts
• supersedes pointer never overwrites prior vintage row (immutable supersedes-chain)
• Stale vintages (>6 months) trigger automatic article-level annotation per scripts/article-quality-enhancer.ts
• Cache-fallback path tested by tests/economic-context-multi-provider.test.ts

🔗 Hack23 Ecosystem

🗳️ Empower citizens · 🔍 Strengthen democratic accountability · 🕵️ Illuminate the political process

_{© 2008–2026 Hack23 AB (Org.nr 559534-7807) · Maintainer: James Pether Sörling, CISSP CISM}