Facthink Facthink
How it works

A claim graph, grown by four stages.

You bring a claim or research goal, your expertise and your topic priorities. They seed a shared claim graph. Four stages, run by seven specialised agents and a set of fixed rules, read from that graph and save their results back into it.

The pipeline · read it top to bottom rounded boxes are agents · grey boxes are fixed rules
flowchart TB subgraph IN["Your inputs"] direction LR claim["Your claim or research goal"]:::user expert["Your expertise + interests"]:::user prio["Your topic priorities"]:::user end subgraph SB["① Map your claim"] ex(["Extraction Agent turns your claim into concepts joined by directed links"]):::extraction end subgraph SV["③ Check the evidence"] er(["Evidence Reviewer reads every short-listed passage behind a link, all in one sitting"]):::evidence vd["a fixed rule turns those readings into the verdict — the agent never decides"]:::det end subgraph SX["② Propose ⟷ critique"] th(["Research Synthesist one ongoing conversation: mine ideas → propose → revise, the source papers always in hand"]):::synthesist subgraph PAN["Critic Panel"] direction LR j1(["Critic agent A grades + ranks every proposal on its own"]):::critic j2(["Critic agent B grades + ranks every proposal on its own"]):::critic j3(["Third judge reads the same proposals, joins only when A and B disagree"]):::critic end agg["fixed rules merge the grades into a pass gate + final ranking"]:::det end subgraph SE["④ Design the experiments"] des(["Experiment Designer drafts a full test plan for each hypothesis you confirmed, grounded in the methods literature"]):::experimentDesigner evl(["Experiment Validator grades the plan on five criteria, sends it back once if needed"]):::experimentValidator end G[("Claim graph")]:::store done(((" done "))):::terminal claim --> ex ex -->|"adds concepts + links"| G prio -->|"records what matters to you"| G G -->|"reads the graph + full-text passages from the papers"| th th -->|"draft hypotheses + reasoning + quotes"| j1 th --> j2 th -.->|"only when A and B disagree"| j3 j1 --> agg j2 --> agg j3 -.-> agg agg -->|"critique + ranking"| th agg -->|"best few shown to you → confirmed → saved"| G G -->|"reads every link with short-listed evidence (in the real run this happens early, right after ①)"| er er --> vd vd -->|"records the verdicts"| G G -->|"reads each confirmed hypothesis + its possible confounders"| des des -->|"experiment plan"| evl evl -.->|"problems flagged → one revision"| des evl -->|"records the plan"| G G -->|"your hypotheses + their experiment plans"| done expert -->|"steers"| SX classDef terminal fill:#2b3640,stroke:#1a232b,color:#ffffff; classDef user fill:#ffffff,stroke:#90906F,color:#2D2D2F; classDef extraction fill:#ffffff,stroke:#4A7A80,color:#4A7A80,stroke-width:1.6px; classDef evidence fill:#ffffff,stroke:#66663F,color:#66663F,stroke-width:1.6px; classDef synthesist fill:#ffffff,stroke:#6E5260,color:#6E5260,stroke-width:1.6px; classDef critic fill:#ffffff,stroke:#BD9C6E,color:#73562F,stroke-width:1.6px; classDef det fill:#E8E7D9,stroke:#95947E,color:#3A3A3D; classDef store fill:#F7E8C9,stroke:#BD9C6E,color:#5A4526,stroke-width:1.8px; classDef experimentDesigner fill:#ffffff,stroke:#8F6420,color:#8F6420,stroke-width:1.6px; classDef experimentValidator fill:#ffffff,stroke:#8F6420,color:#7A5418,stroke-width:1.6px; style IN fill:#E8E7D9,stroke:#CBCAB4,stroke-width:1px style SB fill:#D0DFE2,stroke:#A8C2C7,stroke-width:1px style SV fill:#DDDCC6,stroke:#AFAF8E,stroke-width:1px style SX fill:#E8DDE2,stroke:#CDB9C1,stroke-width:1px style PAN fill:#EFE7EA,stroke:#CDB9C1,stroke-width:1px style SE fill:#F7E8C9,stroke:#D9C08C,stroke-width:1px linkStyle default stroke:#6F6F5E,stroke-width:1.6px linkStyle 3,12,15 stroke:#4A7A80,color:#4A7A80,stroke-width:1.6px linkStyle 1,2,11,14,18,19 stroke:#73562F,color:#73562F,stroke-width:1.6px linkStyle 20 stroke:#523B44,color:#523B44,stroke-width:1.6px
Arrow key: save — a result is written into the claim graph read — a stage reads what is already in the graph steers — your expertise shapes what stage ② proposes hand-off — steps inside a stage passing work along (dashed = only when needed)

One timing wrinkle: the stages are numbered the way this page explains them, but in the running system the evidence check ③ happens early: every link with short-listed evidence is verified right after ①, before any hypothesis is drafted.

The pipeline in plain terms

Seven specialised agents do the reading and writing. Everything that decides — which verdict an edge gets, which hypotheses pass, how they rank, what gets saved — is a fixed rule, so a run can be replayed and audited step by step.

Your expertise steers the proposing stage, so what is mined and proposed stays close to your interests.

①

Map your claim

The Extraction Agent turns your claim or research goal into a small graph: concepts joined by directed links, each recording a relationship a source asserts. Every link starts out unverified. Your topic priorities are recorded on the matching concepts.

②

Propose ⟷ critique

The Research Synthesist works in one ongoing conversation with the retrieved papers always in hand: it first mines the concepts the papers add, each tied to the exact phrase it was read from, then proposes candidate hypotheses, each with a new concept, typed links, an explicit mechanism chain and quoted source spans.

A Critic Panel then reads the whole pool: two independent critic agents each grade field novelty and establishedness, audit every mechanism step and term, and rank the proposals on their own; a third judge joins only when the two disagree. Fixed rules merge the grades into a pass gate and a ranking, and the critique goes back to the Synthesist, which repairs what was flagged and derives new candidates. The best few are then shown to you, and nothing is saved until you, or the selection rule in your profile, confirm it.

③

Check the evidence

For every link with retrieved evidence, the Evidence Reviewer reads the short-listed passages in one sitting and grades each one: how it bears on the link, and how sound its study design is. It is not allowed to state a verdict. A fixed rule fuses the grades, together with the open risks and scope limits the reviewer lists, into one verdict and a confidence. A verdict is accepted only if its confidence clears 0.5 and beats the runner-up clearly; otherwise the link is recorded as insufficient evidence, an abstention rather than a refutation.

④

Design the experiments

For every hypothesis you confirmed, the Experiment Designer expands the one-line sketch into a full test plan grounded in a targeted search of the methods literature: design, operationalisation, baselines, datasets and metrics, controls drawn from the graph's confounder and mediator concepts, and the outcomes that would confirm or refute it. The independent Experiment Validator grades the plan on five criteria (clarity, validity, robustness, feasibility, reproducibility) and sends it back for one round of revision. The plan is saved into the graph, bound to its hypothesis.

In the middle sits the claim graph, the one shared record. Every result is saved into it as a versioned update that must pass five checks before it lands, every stage after ① reads from it, and at the end it hands you your hypotheses with their experiment plans and a full audit trail.
Trace a real run, end to end →
Inside stage ② · Hypothesis scoring

How a hypothesis is scored

Every proposed hypothesis runs a three-stage gauntlet before any reach you. The thresholds and weights below are the configured defaults, echoed in each run's audit, not fixed truths.

A.

The building-block judgments

Each scored 0–1. Most blend two ingredients: the proposing agent's rating and a hard semantic-similarity measurement.

AI rating semantic similarity
NoveltyHow new is the concept?
Math part = how far the new concept sits from everything already in the graph.
7030
Fit to topicInside the scope of interest?
Math part = meaning-closeness of the new concept to the seed claim.
7030
OverlapJust a restatement?
Math leads: closest match of the concept to anything in the graph or to its sibling candidates.
3070
TestabilityRunnable as a benchmark?
No objective meaning-measure exists, so the AI's judgment alone.
100 · AI

Plus four judgments the proposing agent gives directly, with no measurement blended in: plausibility, value of testing, importance, mechanism specificity.

B.

Three stages to a ranking

Stage 1strict pass / fail · fail-closed

The eligibility gate

Eligible only if all four hold at once. Missing any single bar disqualifies the hypothesis no matter how high the others are.

novelty ≥ 0.4 testability ≥ 0.5 fit ≥ 0.5 overlap < 0.8
Stage 2independent critic panel · median

The critic panel

Two critic agents, separate from the proposer, each grade every proposal on its own relative to the field, not just this graph; a third judge is consulted only when the two disagree. Grades combine by the median, which resists a single outlier reviewer. Each judge also audits every mechanism step and term against the quoted sources; what it flags goes back to the Synthesist for repair.

Field noveltyHow new to a practitioner, given the literature. Replaces the proposer's own novelty for ranking.
EstablishednessHow strongly the retrieved papers already treat the relationship as a known result.
Stage 3score → rank

Quality score, then final rank

Quality score · equal-weight average of six
field noveltyplausibilitytestabilityvalue of testingimportancemechanism specificity
Final ranking score
quality × (1 − establishedness)

Establishedness is a 0–1 rating of how strongly the literature already treats the relationship as a known result. It demotes the familiar; it never disqualifies.

Eligible hypotheses sort by this score, the higher the better. The best few are shown to you, and only the ones you confirm, or your profile's selection rule keeps, are saved into the graph and sent on to experiment design.