Wiki source code of FactHarbor
Last modified by Robert Schaub on 2025/12/18 11:53
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% class="wikigeneratedid" %) | ||
| 2 | ((( | ||
| 3 | (% class="box successmessage" %) | ||
| 4 | ((( | ||
| 5 | **Our Vision** | ||
| 6 | A world where decisions and public debate are grounded in evidence so people can move forward with clarity and confidence. | ||
| 7 | ))) | ||
| 8 | ))) | ||
| 9 | ((( | ||
| 10 | (% class="box infomessage" %) | ||
| 11 | ((( | ||
| 12 | **Our Mission** | ||
| 13 | FactHarbor brings clarity and transparency to a world full of unclear, contested, and misleading information by shedding light on the context, assumptions, and evidence behind claims. | ||
| 14 | ))) | ||
| 15 | ))) | ||
| 16 | (% class="box warningmessage" %) | ||
| 17 | ((( | ||
| 18 | **Non Profit and Transparent** | ||
| 19 | FactHarbor is a **Non-Profit Organisation** and a strictly **Open-Source** project. | ||
| 20 | We serve the public interest with full transparency — no paywalls, no hidden algorithms, and no profit motive. | ||
| 21 | ))) | ||
| 22 | == Why FactHarbor Exists == | ||
| 23 | **The Problem** | ||
| 24 | We live in an environment where information conflicts, misleading content spreads fast, and many people lack the time or tools to verify complex claims. Headlines, soundbites, and viral posts often win over careful reasoning, and “fact-checks” frequently reduce everything to a simple verdict without explaining the //why// behind it. The result is frustration, confusion, and growing distrust — not just in institutions, but in the very idea that complex questions can be assessed fairly. | ||
| 25 | **Our Response** | ||
| 26 | FactHarbor acts as a navigation system for complex claims. We don’t just say “true” or “false” — we make assumptions, evidence, and context visible so you can form your own judgement. Instead of asking you to trust an authority, we show you how different conclusions are reached, where the evidence is strong or weak, and where reasonable people might still disagree. | ||
| 27 | == From Claim to Conclusion – Reasoning You Can Trust Because You Can Inspect == | ||
| 28 | **What FactHarbor Does** | ||
| 29 | FactHarbor helps people make sense of contested questions without stripping away nuance. Instead of chasing quick binary verdicts, we break topics into clear, interconnected claims. For each claim, we highlight the context and assumptions it depends on and link directly to the evidence that supports or challenges it. | ||
| 30 | **Where It Helps** | ||
| 31 | Whether you’re analyzing public policy, science, or everyday decisions, FactHarbor provides a transparent way to compare perspectives. Our underlying model creates reusable “claim maps” that journalists, educators, and researchers can build on, while remaining accessible to anyone seeking a clear, honest overview. | ||
| 32 | **Why It’s Trustworthy** | ||
| 33 | At our core is a simple principle: reasoning must be as transparent as the result. Our rules for structuring claims and weighing evidence are documented in the open — designed to be reviewed, challenged, and improved by you. Trust comes not from authority, but from a process anyone can inspect. | ||
| 34 | **AI’s Role** | ||
| 35 | FactHarbor assumes that AI is a powerful pattern-finder, not a built-in truth detector. That’s why we design the system around explicit frames, assumptions, and evidence, and keep humans in the loop to check which “puzzle” we’re actually solving. AI helps us map the landscape; humans decide what’s trustworthy and how it fits the real world | ||
| 36 | == How It Works: The Core Concepts == | ||
| 37 | FactHarbor structures reasoning into transparent steps, moving beyond simple headlines: | ||
| 38 | * **Claims & Clusters** – We group similar real-world statements into clusters to avoid duplicates and keep related claims together. | ||
| 39 | * **Scenarios** – A claim might be true in one context but false in another. We define these contexts (assumptions, definitions) explicitly as Scenarios. | ||
| 40 | * **Evidence** – Data and sources are linked to specific scenarios, not just to the claim in general. | ||
| 41 | * **Verdicts** – We assign likelihoods (e.g., “Highly likely”, “Unsubstantiated”) to each scenario, based on the available evidence. | ||
| 42 | * **Truth Landscape** – The result is not a single word, but a landscape showing where a claim holds up, where it fails, and where the evidence is still unclear. | ||
| 43 | == The Lifecycle: From Input to Verdict == | ||
| 44 | Data in FactHarbor flows through a structured, auditable process: | ||
| 45 | * **Submission:** Text or URLs are submitted and normalised. | ||
| 46 | * **Scenario Building:** AI proposes contexts; humans refine definitions and boundaries. | ||
| 47 | * **Evidence Handling:** Evidence is retrieved, assessed for quality, and linked. | ||
| 48 | * **Verdict Creation:** Drafting reasoning and likelihoods for each scenario. | ||
| 49 | * **Public Presentation:** The "Truth Landscape" is published for users to explore. | ||
| 50 | * **Time Evolution:** When new evidence arrives, we re-evaluate. Everything is versioned. | ||
| 51 | == Explore FactHarbor == | ||
| 52 | ((( | ||
| 53 | (% class="box" %) | ||
| 54 | ((( | ||
| 55 | == [[Organisation>>FactHarbor.Organisation.WebHome]] == | ||
| 56 | **//Structure, Governance, and Funding.//** | ||
| 57 | Discover how we are organised, how decisions are made, and how you can contribute. | ||
| 58 | * [[Go to Organisation>>FactHarbor.Organisation.WebHome]] | ||
| 59 | ))) | ||
| 60 | ))) | ||
| 61 | ((( | ||
| 62 | (% class="box" %) | ||
| 63 | ((( | ||
| 64 | == [[Specification>>FactHarbor.Specification.WebHome]] == | ||
| 65 | **//Deep Technical Specs.//** | ||
| 66 | Dive into the Architecture, Data Models, API definitions, and detailed algorithms. | ||
| 67 | * [[Go to Specification>>FactHarbor.Specification.WebHome]] | ||
| 68 | * //(Draft content available in [[Holding Page>>FactHarbor.Specification.WebHome]])// | ||
| 69 | ))) | ||
| 70 | ))) |