Requirements

Version 2.1 by Robert Schaub on 2025/12/12 09:32

Requirements

This chapter defines the requirements for FactHarbor.

User Roles

Reader

  • Responsibilities: Browse, search, view scenarios/verdicts, flag issues.
  • Permissions: Read-only access.
  • Limitations: Cannot change content.

Contributor

  • Responsibilities: Submit claims, draft scenarios, attach evidence.
  • Permissions: Create/Edit drafts, comment.
  • Limitations: Cannot publish without review.

Reviewer

  • Responsibilities: Validate contributions, check consistency.
  • Permissions: Change status to "Published" or "Rejected".

Expert

  • Responsibilities: Domain-specific judgment, refine assumptions.
  • Permissions: Attach expert annotations, propose re-evaluation.

Moderator

  • Responsibilities: Handle abuse, spam, and manipulation.
  • Permissions: Hide content, ban users.

Maintainer / Administrator

  • Responsibilities: Node config, security, role assignment.
  • Permissions: System configuration.

AKEL (AI)

  • Responsibilities: Propose drafts, normalize, classify.
  • Permissions: Create machine-generated drafts.
  • Limitations: Never publishes without human approval.

Functional Requirements

Claim Intake & Normalization

  • FR1: Support text, URL, document input.
  • FR2: Normalize wording while preserving original.
  • FR3: Classify by domain/type.
  • FR4: Cluster similar claims.

Scenario System

  • FR5: Create scenarios linked to clusters.
  • FR6: Require Definitions, Assumptions, Boundaries.
  • FR7: Full versioning.
  • FR8: Side-by-side comparison.

Evidence Management

  • FR9: Ingest external sources.
  • FR10: Assess reliability/quality.
  • FR11: Link evidence to multiple scenarios.

Verdicts & Truth Landscape

  • FR12: Likelihood-based verdicts per scenario.
  • FR13: Aggregate into Truth Landscape.
  • FR14: Show evolution over time.

Workflow & Audit

  • FR15: Draft -> Review -> Publish states.
  • FR16: Moderation tools.
  • FR17: Full audit trail.

Federation Requirements

  • FR18: Node autonomy.
  • FR19: Configurable data sharing.
  • FR20: Sync with conflict handling.
  • FR21: Node discovery.

Non-Functional Requirements

  • NFR1 - Transparency: Visible reasoning and AKEL labeling.
  • NFR2 - Security: Role-based access, secure storage.
  • NFR3 - Privacy: Minimal data retention, compliance hooks.
  • NFR4 - Performance: < 2s response (POC).
  • NFR5 - Scalability: Support thousands of users (Release 1.0).
  • NFR6 - Interoperability: Open API.
  • NFR7 - Observability: Metrics and logs.
  • NFR8 - Maintainability: Modular architecture.
  • NFR9 - Usability: Progressive disclosure of complexity.

Release Levels

  • POC (Fully Automated): Single node. "Text to Truth Landscape" workflow. Automated extraction, scenario generation, and verdict computation.
  • Beta 0: Few nodes, external testers. Expanded manual workflows and moderation.
  • Release 1.0: Scalable, Federated, High Automation. Multi-node federation.