SignalForge / Inspect the evidence
When three articles are still one source
Repeated coverage can resemble independent corroboration. SignalForge keeps source relationships and counter-evidence attached to the claim being assessed.
Synthetic demonstration · Reproduced 16 October 2026 · Development project
01 / The input
Three synthetic articles support the same claim and explicitly cite one primary source. A separate test report is then added, followed by a report that refutes the claim. Provenance and stance are supplied explicitly.
02 / The result
| Evidence supplied | Supporting families | Reported status |
|---|---|---|
| Three articles, shared primary source | 1 | single_origin |
| Add an independent supporting report | 2 | corroborated |
| Add a separate counter-report | 2 | contested |
The three articles initially count as one supporting family. Independent support changes the status to corroborated; explicit counter-evidence changes it to contested. Each stage retains exact evidence and claim identifiers.
Inspect full inputs and outputs (JSON) →03 / What this means for a review
The useful output is an inspectable basis for judgment: which claims have support, where that support originates, and what challenges it. A decision can cite a particular snapshot and be revisited as evidence changes.
What this establishes — and its limits
Corroborated is a rule-based status based on supplied provenance, not proof of truth. Hidden dependence and semantic paraphrases are not automatically resolved. This demonstration runs the pure adjudicator offline; it does not validate live collectors. The general-web collector remains an opt-in mock, scores are uncalibrated heuristics, and local hashes are not external signatures.
This is an independently developed engineering example, not a client engagement or production validation.
Source and reproduction
Output generated from SignalForge revision bfe0a9f using the reproduction script. Read the source contract and limitations.
Reproduce the three examples locally
With the site and three project repositories checked out beneath C:/dev/playground, pin each project to the revisions below. Use clean checkouts and Node 24.19 or newer.
cd C:/dev/playground
git -C coldgate checkout --detach 87844dd8bbfeefae60202d175f18eefc51eecb0f
git -C driftglass checkout --detach e6858ef591b0012d3334d8943ef853eb4a6b04d4
git -C signalforge checkout --detach bfe0a9f93d7049ac9554061a58c119ae5ba517da
cd frostedlogic-site
node scripts/reproduce-work.mjs ../coldgate ../driftglass ../signalforgeApply the method
Discuss evidence for a technology decision
Bring a specific workflow and the decision you need to make. We can scope the review, evidence needed, and practical next steps.