build-evidence-map

Frame one falsifiable question and a provisional position, then collect bounded source regions with URLs, dates, locators, and excerpts. Atomize reasoning into position, claim, evidence, and unknown nodes connected by supports, contradicts, qualifies, or missing edges, and write the result as a .doubt.json file.

Run node scripts/validate.mjs decision.doubt.json with Node.js 18 or newer. The validator uses only Node.js built-ins, requires no npm install or network access, and prints VALID followed by a 64-character receipt when the map passes all checks.

Use an evidence map when relationships between evidence, intermediate claims, trade-offs, and missing facts matter for a consequential decision. For simple factual claims or general fact-checking, a verification workflow such as doublecheck is the better fit.

Each source needs a title, publisher, publication date, retrieval date, URL or local path, a bounded locator such as a page, section, line range, or timestamp, and a checkable excerpt of 40 to 500 characters. Sources without an exact locatable region become unknown nodes instead.

The schema forbids confidence fields to avoid false precision in reasoning. Uncertainty is expressed structurally instead by adding an unknown node, narrowing the position, or attaching a qualifies edge to a claim.

Rendering to HTML requires the user to have already installed [email protected], and source verification with doubt verify retrieves recorded HTTP sources only with explicit network permission. Neither command is run implicitly, and verification results are never written by hand.