Turn one contested question into a portable decision artifact that shows what
supports the current position, what pushes against it, and what remains unknown.
Do not use a graph to decorate an answer that has not been sourced.
For a simple factual claim or a general fact-checking request, use a verification
workflow such as doublecheck instead. Use this skill when the relationships
between evidence, intermediate claims, trade-offs, and missing facts matter.
position. Narrow the question until a reader can identify what action or
belief the map is testing.
sources. Record the URL or absolute local path, publisher, publication date,
retrieval date, section/page/line/timestamp locator, and a short checkable
excerpt. Read references/evidence-ladder.md
when source quality is disputed.
position: the single current verdict;claim: an intermediate proposition;evidence: a faithful statement of one source region;unknown: a specific missing fact that could change the verdict.supports, contradicts, qualifies, ormissing. Add a plain-language note explaining why the source node bears on
the target. Topical similarity is not support. Different scope, date, or
population is not automatically a contradiction.
provisional verdict survives it. Represent scope differences withqualifies edges.
Add an unknown, narrow the position, or qualify a claim.
.doubt.json suffix. Followreferences/map-schema.md. Keep IDs short,
stable, and semantic.
scripts/validate.mjs relative to this SKILL.md, then run it with Node.js
18 or newer:
```bash
node
```
The bundled validator uses only Node.js built-ins and does not require npm or
network access. Fix every finding before reporting success. Only say the map
is valid when the command exits 0 and prints VALID followed by a
64-character receipt. A file hash, node count, JSON parse, or manual schema
review is not a Doubt receipt. If deterministic validation cannot run, report
that block instead of inventing success.
Render the validated map only when the user has already installeddoubt-ai@0.8.0; do not install or execute a remote package implicitly:
```bash
doubt map decision.doubt.json --out decision.html
```
following command retrieves each recorded HTTP(S) source and fails closed if
an excerpt cannot be matched:
```bash
doubt verify decision.doubt.json \
--out decision.verified.doubt.json
```
Never run this command implicitly. Local file verification does not use the
network. Do not write a verification object by hand or hide a mismatch.
counterevidence, unknowns, edge notes, and exact source regions remain
readable. Treat JSON as the canonical editable artifact; HTML is a
shareable view.
A finished map must satisfy all of these:
position has incoming reasoning;excerpt;
unknown node;Report:
Never describe a structurally valid map as proven true. Validation establishes
traceability and graph integrity; source quality and inference quality still
require human review.