Wiki source code of Requirements Priority Matrix

Last modified by Robert Schaub on 2025/12/23 12:06

version	line-number	content
1.1	1	= Requirements Importance Matrix =
	2
	3	This page shows all functional, non-functional, and user needs requirements ordered by urgency and importance.
	4
1.2	5	Note: Implementation phases and requirement-to-phase mapping are defined in [[Requirements Roadmap Matrix>>Test.FactHarbor pre V0\.9\.79.Roadmap.Requirements-Roadmap-Matrix.WebHome]], not in this importance matrix.
1.1	6
	7	{{info}}
1.4	8	Scope: This matrix prioritizes the 16 formal system requirements that have full specifications in the [[Requirements>>Test.FactHarbor pre V0\.9\.79.Specification.Requirements.WebHome]] page. POC-specific implementation requirements (FR1-FR3, FR5-FR6, FR8, FR11, FR13, NFR1-NFR3) are detailed in [[POC Requirements>>Test.FactHarbor.Specification.POC.Requirements]] and mapped to phases in the [[Requirements Roadmap Matrix>>Test.FactHarbor pre V0\.9\.79.Roadmap.Requirements-Roadmap-Matrix.WebHome]].
1.1	9	{{/info}}
	10
	11	== Importance and Urgency Levels ==
	12
	13	How Requirements are Prioritized:
	14
	15	* Importance = f(risk, impact, strategy)
1.2	16	* What happens if we don't do this? (risk)
	17	* How much value does it create? (impact)
	18	* Does it align with our strategic direction? (strategy)
1.1	19
	20	* Urgency = f(fail fast and learn, legal, promises made)
1.2	21	* Do we need this to validate core assumptions? (fail fast and learn)
	22	* Are we legally required to have this? (legal)
	23	* Have we committed to delivering this? (promises made)
1.1	24
	25	Importance Levels:
1.2	26
1.1	27	* CRITICAL - System doesn't work without it, or major safety/legal risk
	28	* HIGH - Core functionality, essential for success
	29	* MEDIUM - Important but not blocking
	30	* LOW - Nice to have, can be deferred
	31
	32	Urgency Levels:
1.2	33
1.1	34	* HIGH - Immediate need (critical for proof of concept)
	35	* MEDIUM - Important but not immediate
	36	* LOW - Future enhancement
	37
	38	== Functional & Non-Functional Requirements ==
	39
	40	All requirements are sorted by Urgency (HIGH → LOW), then Importance (CRITICAL → LOW).
	41
	42	\|= ID \|= Title \|= Importance \|= Urgency \|= Comment
1.2	43	\| HIGH URGENCY \|\|\|\|\\
1.1	44	\| FR7 \| Automated Verdicts (Enhanced with Quality Gates) \| CRITICAL \| HIGH \| Core AKEL capability - system cannot function without automated verdict generation
	45	\| NFR11 \| AKEL Quality Assurance Framework \| CRITICAL \| HIGH \| Without quality gates, automated analysis cannot be trusted
	46	\| FR4 \| Analysis Summary (Enhanced with Quality Metadata) \| HIGH \| HIGH \| Essential for users to understand and trust verdicts
1.2	47	\| MEDIUM URGENCY \|\|\|\|\\
1.1	48	\| NFR12 \| Security Controls \| CRITICAL \| MEDIUM \| Essential for production deployment
	49	\| FR44 \| ClaimReview Schema Implementation \| HIGH \| MEDIUM \| Required for search engine discoverability
	50	\| FR45 \| User Corrections Notification System \| HIGH \| MEDIUM \| Critical for user trust and transparency
	51	\| FR48 \| Safety Framework for Contributors \| HIGH \| MEDIUM \| Protects contributors from harassment
	52	\| NFR13 \| Quality Metrics Transparency \| HIGH \| MEDIUM \| Users need to understand quality levels
1.2	53	\| FR46 \| Image Verification System \| MEDIUM \| MEDIUM \|\\
	54	\| FR47 \| Archive.org Integration \| MEDIUM \| MEDIUM \|\\
	55	\| FR49 \| A/B Testing Framework \| MEDIUM \| MEDIUM \|\\
	56	\| LOW URGENCY \|\|\|\|\\
1.1	57	\| FR54 \| Evidence Deduplication \| CRITICAL \| LOW \| Essential for data integrity and preventing duplicate processing
	58	\| FR50 \| OSINT Toolkit Integration \| HIGH \| LOW \| Valuable capability for future phases (geolocation, chronolocation, social media analysis)
	59	\| FR51 \| Video Verification System \| HIGH \| LOW \| Valuable capability for future phases (deepfake detection, frame analysis)
1.2	60	\| FR52 \| Interactive Detection Training \| MEDIUM \| LOW \|\\
1.1	61	\| FR53 \| Cross-Organizational Sharing \| MEDIUM \| LOW \|
	62
	63	Total: 16 requirements (13 Functional, 3 Non-Functional)
	64
	65	== User Needs Importance ==
	66
	67	User Needs (UN) are the foundation that drives functional and non-functional requirements. They are not independently prioritized; instead, their importance is inherited from the FR/NFR requirements they drive.
	68
	69	\|= ID \|= Title \|= Drives Requirements \|= Comment
1.2	70	\| UN-1 \| Trust Assessment at a Glance \| FR7, NFR13 \|\\
	71	\| UN-2 \| Claim Extraction and Verification \| FR7 \|\\
	72	\| UN-3 \| Article Summary with FactHarbor Analysis Summary \| FR4 \|\\
	73	\| UN-4 \| Social Media Fact-Checking \| FR7 \|\\
	74	\| UN-5 \| Source Provenance and Track Records \| FR4 \|\\
	75	\| UN-6 \| Publisher Reliability History \| FR4 \|\\
	76	\| UN-7 \| Evidence Transparency \| FR4, NFR13 \|\\
	77	\| UN-8 \| Understanding Disagreement and Consensus \| FR7 \|\\
	78	\| UN-9 \| Methodology Transparency \| NFR13 \|\\
	79	\| UN-10 \| Manipulation Tactics Detection \| FR52 \|\\
	80	\| UN-11 \| Filtered Research \| FR54 \|\\
	81	\| UN-12 \| Submit Unchecked Claims \| FR7 \|\\
	82	\| UN-13 \| Cite FactHarbor Verdicts \| FR44 \|\\
	83	\| UN-14 \| API Access for Integration \| FR44 \|\\
	84	\| UN-15 \| Verdict Evolution Timeline \| NFR13 \|\\
	85	\| UN-16 \| AI vs. Human Review Status \| NFR13 \|\\
	86	\| UN-17 \| In-Article Claim Highlighting \| FR7 \|\\
	87	\| UN-26 \| Search Engine Visibility \| FR44 \|\\
	88	\| UN-27 \| Visual Claim Verification \| FR46, FR51 \|\\
	89	\| UN-28 \| Safe Contribution Environment \| FR48 \|\\

Wiki source code of Requirements Priority Matrix

Applications

Navigation

Need help?