Requirements Roadmap Matrix

Version 2.1 by Robert Schaub on 2025/12/23 22:41

Requirements Roadmap Matrix

Last Updated: 2025-12-23  
Version: 3.0  
Status: Authoritative Source  

Information

Purpose: This is the single source of truth for:

  • Requirement-to-phase mapping
  • Implementation levels (Basic → Enhanced → Complete)
  • Importance and Urgency prioritization
  • User Needs fulfillment by phase

All other documents reference this matrix rather than duplicating information.

Phase Definitions

 Phase  Goal  Key Focus
 POC1  Prove AI can analyze claims automatically  Core workflow + quality gates + context-aware analysis (experimental)
 POC2  Improve reliability and robustness  Quality improvements, deduplication
 Beta 0  User testing with limited audience  Production readiness, user features
 V1.0  Public production launch  IFCN compliance, search visibility
 V1.1  First major feature expansion  Advanced capabilities
 V1.5  Media verification expansion  Image/video/audio verification, archive integration
 V2.0  Advanced capabilities  Comprehensive toolset

Phase Philosophy: Each phase builds on proven capabilities from previous phases. We validate AI quality before adding production features.

Requirement Categories

This matrix covers two types of requirements:

      1. Formal System Requirements (16 requirements: FR4, FR7, FR44-FR54, NFR11-NFR13)

These are the primary requirements with full specifications in the Requirements page.

2. POC-Specific Requirements (FR1-FR2, FR5-FR6, FR11, FR13, NFR1-NFR3)

These are detailed in POC Requirements for POC1 implementation but do not have separate formal specification sections.

Mapping: POC-specific requirements are implementation-level details of formal requirements. For example:

  • FR1 (Claim Extraction), FR2 (Context), FR3 (Scenarios), FR5 (Evidence Collection), FR6 (Source Quality) → All part of FR7 (Automated Verdicts)
  • FR11 (Audit Trail) → Part of NFR11 (Quality Assurance)
  • NFR1-NFR3 (Explainability, Performance, Transparency) → Addressed in NFR11 and NFR13
Information

For phase planning: Use the formal requirements (FR4, FR7, FR44-FR54, NFR11-NFR13) as the primary planning units. POC-specific requirements are implementation details within those formal requirements.

Warning

Future Requirement Numbering: To avoid conflicts with existing requirements (FR1-FR54, NFR1-NFR13, UN-1 to UN-28), new requirements will use:

  • FR55-FR84 for future functional requirements
  • NFR14-NFR18 for future non-functional requirements  
  • UN-29 to UN-36 for future user needs

See Gap Analysis for features not yet assigned formal requirement numbers.

Requirements by Phase

Note: Requirements are organized by release and sorted by Urgency (HIGH → MEDIUM → LOW), then Importance (CRITICAL → HIGH → MEDIUM → LOW).

Information

Formal vs POC-Specific: 16 requirements have formal Importance/Urgency prioritization (FR4, FR7, FR44-FR54, NFR11-NFR13). POC-specific requirements (FR1-FR2, FR5-FR6, FR11, FR13, NFR1-NFR3) are implementation details within formal requirements and marked as "(POC-specific)".

POC1

Goal: Prove that AI can extract claims and determine verdicts automatically

Experimental Feature: Context-aware analysis (tests if article credibility differs from claim average)

Requirements: 2 formal + 7 POC-specific

 ID  Title  Importance  Urgency  Notes
 FR7  Automated Verdicts (Enhanced with Quality Gates)  CRITICAL  HIGH  Core AKEL capability - system cannot function without automated verdict generation
 FR4  Analysis Summary (Enhanced with Context-Aware Analysis)  HIGH  HIGH  Enhanced in POC1 to test context-aware analysis (experimental feature). If successful (≥70% accuracy), ships in POC2. See Article Verdict Problem
 FR1  Claim Extraction  (POC-specific)  (POC-specific)  Part of FR7 implementation
 FR2  Claim Context  (POC-specific)  (POC-specific)  Part of FR7 implementation
 FR5  Evidence Collection  (POC-specific)  (POC-specific)  Part of FR7 implementation
 FR6  Source Quality Assessment  (POC-specific)  (POC-specific)  Part of FR7 implementation
 NFR1  Explainability  (POC-specific)  (POC-specific)  Basic implementation
 NFR2  Performance  (POC-specific)  (POC-specific)  Basic implementation
 NFR3  Transparency  (POC-specific)  (POC-specific)  Basic implementation

Context-Aware Analysis Details:

  • Approach: Single-Pass Holistic Analysis (Approach 1)
  • Implementation: Enhanced AI prompt to evaluate logical structure
  • Testing: 30-article test set (10 straightforward, 10 misleading, 10 complex)
  • Success Criteria: ≥70% accuracy detecting misleading articles
  • Decision Path: If ≥70% → ship in POC2; if 50-70% → try weighted aggregation; if <50% → defer
  • Cost: Zero increase (no additional API calls, no architecture changes)
  • Documentation: Article Verdict Problem

POC2

Goal: Improve system reliability and add essential quality features

Requirements: 3 formal

 ID  Title  Importance  Urgency  Notes
 NFR11  AKEL Quality Assurance Framework  CRITICAL  HIGH  Without quality gates, automated analysis cannot be trusted. POC1 implements 2 gates (Gates 1 & 4), POC2 implements all gates
 FR4  Analysis Summary (Enhanced with Quality Metadata)  HIGH  HIGH  Essential for users to understand and trust verdicts. Enhanced from POC1 with quality metadata display
 FR54  Evidence Deduplication  CRITICAL  LOW  Essential for data integrity and preventing duplicate processing

Beta 0

Goal: Prepare for public launch with essential user-facing features and security

Requirements: 2 formal + 2 POC-specific

 ID  Title  Importance  Urgency  Notes
 NFR13  Quality Metrics Transparency  HIGH  MEDIUM  Users need to understand quality levels
 NFR12  Security Controls  CRITICAL  MEDIUM  Essential for production deployment - moved from V1.0 to Beta 0 for earlier security hardening
 FR11  Audit Trail  (POC-specific)  (POC-specific)  Production-ready audit logging
 FR13  In-Article Claim Highlighting  (POC-specific)  (POC-specific)  User-facing feature for article analysis

V1.0

Goal: Full production launch with IFCN compliance and search engine visibility

Requirements: 4 formal

 ID  Title  Importance  Urgency  Notes
 FR44  ClaimReview Schema Implementation  HIGH  MEDIUM  Required for search engine discoverability (Google/Bing fact-check visibility)
 FR45  User Corrections Notification System  HIGH  MEDIUM  Critical for user trust and transparency, IFCN compliance
 FR48  Contributor Safety Framework  HIGH  MEDIUM  Protects contributors from harassment
 FR49  A/B Testing Framework  MEDIUM  MEDIUM  Enables continuous system improvement through experimentation

V1.1

Goal: Add advanced capabilities

Requirements: 2 formal

 ID  Title  Importance  Urgency  Notes
 FR50  OSINT Toolkit Integration  HIGH  LOW  Valuable capability (geolocation, chronolocation, social media analysis)
 FR52  Interactive Detection Training  MEDIUM  LOW  Education and media literacy features

V1.5

Goal: Media verification expansion (image, video, audio)

Requirements: 4 formal

 ID  Title  Importance  Urgency  Notes
 FR46  Image Verification System  HIGH  MEDIUM  Moved from V1.0 to V1.5 to focus V1.0 on core text-based fact-checking. Includes reverse image search, manipulation detection, EXIF analysis
 FR51  Video Verification System  HIGH  LOW  Moved from V1.1 to V1.5. Includes keyframe extraction, deepfake detection, metadata analysis
 FR47  Archive.org Integration  MEDIUM  MEDIUM  Moved from Beta 0 to V1.5. Ensures evidence persistence even if original sources deleted
 FR53  Cross-Organizational Sharing  MEDIUM  LOW  Collaboration with other fact-checkers (IFCN/EFCSN members)

Requirements Summary by Phase

 Phase  Formal Requirements  POC-Specific  Total  Cumulative
 POC1  2 (FR4, FR7)  7  9  9
 POC2  3 (FR4 enhanced, FR54, NFR11)  0  3  12
 Beta 0  2 (NFR12, NFR13)  2 (FR11, FR13)  4  16
 V1.0  4 (FR44, FR45, FR48, FR49)  0  4  20
 V1.1  2 (FR50, FR52)  0  2  22
 V1.5  4 (FR46, FR47, FR51, FR53)  0  4  26

Total Unique Requirements: 17 formal + 9 POC-specific = 26 total

User Needs by Phase

Summary of when each User Need is fulfilled:

 User Need  Title  Fulfilled in Phase  Via Requirements
 UN-1  Trust Assessment at a Glance  POC1  FR7, NFR13
 UN-2  Claim Extraction and Verification  POC1  FR7
 UN-3  Article Summary with FactHarbor Analysis Summary  POC1  FR4 (enhanced with context-aware analysis)
 UN-4  Social Media Fact-Checking  POC1  FR7
 UN-5  Source Provenance and Track Records  POC1  FR4, FR6
 UN-6  Publisher Reliability History  POC1  FR4, FR6
 UN-7  Evidence Transparency  POC1  FR4, NFR13
 UN-8  Understanding Disagreement and Consensus  POC1  FR7
 UN-9  Methodology Transparency  POC1  NFR13
 UN-10  Manipulation Tactics Detection  V1.5  FR52
 UN-11  Filtered Research  POC2  FR54
 UN-12  Submit Unchecked Claims  POC1  FR7
 UN-13  Cite FactHarbor Verdicts  Beta 0  FR13, FR44
 UN-14  API Access for Integration  V1.0  Production API infrastructure
 UN-15  Verdict Evolution Timeline  Deferred (Not in V1.0)  Edit history only
 UN-16  AI vs. Human Review Status  POC1  NFR13
 UN-17  In-Article Claim Highlighting  Beta 0  FR13
 UN-26  Search Engine Visibility  V1.0  FR44
 UN-27  Visual Claim Verification  V1.5 (images), V1.5 (video)  FR46, FR51
 UN-28  Safe Contribution Environment  V1.0  FR48

Total User Needs: 20 (UN-1 to UN-28, with gaps)

Note: UN-29 to UN-36 reserved for future user needs from Gap Analysis

Key Changes in V3.0

This version includes important updates:

  1. Context-Aware Analysis Added to POC1
       - FR4 enhanced to test context-aware analysis (experimental)
       - Tests if article credibility differs from simple claim average
       - Approach 1: Single-Pass Holistic Analysis
       - Success: ≥70% accuracy → ships in POC2
       - See Article Verdict Problem

2. Media Verification Moved to V1.5
   - FR46 (Image Verification): V1.0 → V1.5
   - FR51 (Video Verification): V1.1 → V1.5
   - FR47 (Archive.org Integration): Beta 0 → V1.5
   - Rationale: Focus V1.0 on core text-based fact-checking

3. Security Hardening Earlier
   - NFR12 (Security Controls): V1.0 → Beta 0
   - Ensures production security before public launch

4. Future Requirement Numbering Established
   - FR55-FR84 reserved for future functional requirements
   - NFR14-NFR18 reserved for future non-functional requirements
   - UN-29 to UN-36 reserved for future user needs
   - Prevents conflicts with existing baseline (FR1-FR54, NFR1-NFR13, UN-1 to UN-28)

Requirements Without Phase Assignments

Warning

If any requirements appear here, they need phase assignment.

Current Status: All 17 formal requirements have phase assignments ✅

Gap Analysis Features (Not Yet Formal Requirements):

The following features from Gap Analysis are not yet assigned formal requirement numbers but would use FR55+, NFR14+, UN-29+ when formalized:

Category 1: Accessibility (2 gaps)

  • WCAG 2.1 Compliance
  • Multilingual Support

Category 2: Platform Integration (2 gaps)

  • Browser Extensions
  • Embeddable Widgets

Category 3: Media Verification (3 gaps)

  • Image Verification (informal → FR46 in V1.5)
  • Video Verification (informal → FR51 in V1.5)
  • Audio Verification (not yet formalized)

Category 4: Mobile & Offline (2 gaps)

  • Mobile Apps / PWA
  • Offline Access

Category 5: Education (2 gaps)

  • Educational Resources
  • Media Literacy Integration

Category 6: Collaboration (2 gaps)

  • Professional Collaboration Tools
  • Community Discussion

Category 7: Advanced Features (2 gaps)

  • User Analytics
  • Personalization

Total: 15 gap features not yet formalized as requirements

References

This matrix is referenced by:

Maintenance:

  • Update this matrix when adding new requirements
  • Update this matrix when changing phase assignments or importance/urgency
  • Verify other documents still reference correctly after updates
  • Use FR55+, NFR14+, UN-29+ for new requirements

Last Review: 2025-12-23 (V3.0)  
Next Review: After POC1 completion or when adding new requirements