Machine-readable evidence

Structure records for agents

Every public WDID dossier has a canonical JSON representation. Use the manifest for discovery, NDJSON for bulk retrieval, and field-level provenance before repeating a claim.

Endpoints

/wdid/<WDID>/record.json — one canonical record
/data/structure-records/manifest.json — versions, counts, dates, hashes, and downloads
/data/structure-records/district-05.ndjson — District 5 collection
/data/schemas/structure-record-v1.schema.json — JSON Schema

Evidence rules

dwr_state_record means a cited state field—not DitchBook verification.
ditchbook_verified applies only to published company associations.
reviewed_geometry never proves a parcel crossing or survey location.
context_only never means connected, commonly owned, or hydrologically linked.
not_verified is unknown—not proof that no company exists.

Freshness

Read absolute dates first. state_at_evaluation is the category when the static snapshot was built; calculate current age from freshness.dwr.retrieved_at. A next-refresh date is a workflow target, not proof a refresh occurred.

Safe agent workflow

Validate the record against the linked schema.
Keep the seven-character WDID string intact.
Identify the evidence lane and cited source for each material claim.
Do not convert contacts into owners, points into alignments, amounts into shares, or nearby records into connected systems.
Send professionals to the source URLs and next-check guidance before reliance.