Wiki source code of Specification
Last modified by Robert Schaub on 2026/02/08 08:32
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{warning title="Version 0.9.32 (Draft)"}} |
| 2 | This document describes the **Specification** of FactHarbor. It is a working draft. | ||
| 3 | {{/warning}} | ||
| |
1.2 | 4 | |
| |
1.1 | 5 | = Specification = |
| |
1.2 | 6 | |
| |
1.1 | 7 | This section defines the technical architecture, data models, and functional requirements of FactHarbor. |
| |
1.2 | 8 | |
| |
1.1 | 9 | == 1. Mission == |
| |
1.2 | 10 | |
| |
1.1 | 11 | **FactHarbor brings clarity and transparency to a world full of unclear, controversial, and misleading information by shedding light on the context, assumptions, and evidence behind claims — empowering people to better understand and judge wisely.** |
| |
1.2 | 12 | |
| |
1.1 | 13 | == 2. Purpose == |
| |
1.2 | 14 | |
| |
1.1 | 15 | Modern society faces a deep informational crisis: |
| |
1.2 | 16 | |
| |
1.1 | 17 | * Misinformation spreads faster than corrections. |
| 18 | * High-quality evidence is buried under noise. | ||
| 19 | * Meanings shift depending on context — but this is rarely made explicit. | ||
| 20 | * Users lack tools to understand *why* information conflicts. | ||
| 21 | * Claims are evaluated without clearly defined assumptions. | ||
| 22 | FactHarbor introduces structure, transparency, and comparative reasoning. It provides: | ||
| 23 | * Multiple valid scenarios for ambiguous claims. | ||
| 24 | * Transparent assumptions, definitions, and boundaries. | ||
| 25 | * Full evidence provenance. | ||
| 26 | * Likelihood-based verdicts (one per scenario). | ||
| 27 | * Versioning and temporal change tracking. | ||
| 28 | * Hybrid AI–human collaboration. | ||
| |
1.2 | 29 | |
| |
1.1 | 30 | == 3. Core Concepts == |
| |
1.2 | 31 | |
| |
1.1 | 32 | * **Claim**: A statement needing structured interpretation. |
| 33 | * **Scenario**: Definitions, assumptions, boundaries, and context. | ||
| 34 | * **Evidence**: Information supporting or contradicting a scenario. | ||
| 35 | * **Verdict**: Likelihood estimate based on weighted evidence **for a specific scenario**. | ||
| 36 | * **Summary View**: User-facing overview. | ||
| 37 | * **AKEL**: AI subsystem for drafting and assistance (human supervised). | ||
| 38 | * **Federation**: Decentralized nodes hosting datasets. | ||
| 39 | * **Truth Landscape**: The aggregation of multiple scenario-dependent verdicts showing where a claim is plausible. | ||
| 40 | * **Time Evolution**: Versioning of all entities allowing historical views. | ||
| |
1.2 | 41 | |
| |
1.1 | 42 | == 4. Functional Lifecycle == |
| |
1.2 | 43 | |
| |
1.1 | 44 | The system follows a six-step lifecycle: |
| |
1.2 | 45 | |
| |
1.1 | 46 | 1. **Claim submission**: Automatic extraction and normalisation; Cluster detection. |
| 47 | 2. **Scenario building**: Clarifying definitions and assumptions; AI proposals with human approval. | ||
| 48 | 3. **Evidence handling**: AI-assisted retrieval; Human assessment of reliability; Explicit scenario linking. | ||
| 49 | 4. **Verdict creation**: AI-generated draft verdicts; Human refinement; Reasoning explanations. | ||
| 50 | 5. **Public presentation**: Concise summaries; Truth Landscape comparison; Deep dives. | ||
| 51 | 6. **Time evolution**: Versioning of all entities; Re-evaluation triggers when evidence changes. | ||
| |
1.2 | 52 | |
| |
1.1 | 53 | == 5. Chapters == |
| |
1.2 | 54 | |
| |
1.1 | 55 | This specification is organized into the following sections: |
| |
1.2 | 56 | |
| |
1.1 | 57 | === Core Documentation === |
| |
1.2 | 58 | |
| 59 | * [[AI Knowledge Extraction Layer (AKEL)>>Archive.FactHarbor 2026\.02\.08.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]] - AI system architecture | ||
| |
1.3 | 60 | * [[Architecture>>Archive.FactHarbor 2026\.02\.08.Specification.Architecture.WebHome]] - System architecture and design |
| |
1.4 | 61 | * [[Automation>>Archive.FactHarbor 2026\.02\.08.Specification.Automation.WebHome]] - Automated processes and workflows |
| |
1.5 | 62 | * [[Data Model>>Archive.FactHarbor 2026\.02\.08.Specification.Data Model.WebHome]] - Database schema and entities |
| |
1.10 | 63 | * [[Requirements>>Archive.FactHarbor 2026\.02\.08.Specification.Requirements.WebHome]] - Functional and non-functional requirements |
| |
1.13 | 64 | * [[Workflows>>Archive.FactHarbor 2026\.02\.08.Specification.Workflows.WebHome]] - Process workflows |
| |
1.2 | 65 | |
| |
1.1 | 66 | === Diagrams === |
| |
1.2 | 67 | |
| |
1.6 | 68 | * [[Diagrams>>Archive.FactHarbor 2026\.02\.08.Specification.Diagrams.WebHome]] - Visual architecture and workflow diagrams |
| |
1.2 | 69 | |
| |
1.1 | 70 | === Additional Resources === |
| |
1.2 | 71 | |
| |
1.7 | 72 | * [[Data Examples>>Archive.FactHarbor 2026\.02\.08.Specification.Examples.WebHome]] - Sample data structures |
| |
1.8 | 73 | * [[FAQ>>Archive.FactHarbor 2026\.02\.08.Specification.FAQ.WebHome]] - Frequently asked questions |
| |
1.9 | 74 | * [[Federation & Decentralization>>Archive.FactHarbor 2026\.02\.08.Specification.Federation & Decentralization.WebHome]] - Future federation plans |
| |
1.11 | 75 | * [[Review & Data Use>>Archive.FactHarbor 2026\.02\.08.Specification.Review & Data Use.WebHome]] - Data usage policies |