CAThe Citizen Audit

Audit 002

Evidence Map

The evidence register contains 271 evidence items connected to claims, sources, entities, events, unresolved questions, programs, and fiscal years.

Source GateFindingsClaimsLimitations

Evidence register

271 items · 438 graph nodes · 596 graph edges.

Traceable Core

The evidence layer is the audit’s control surface. Findings should emerge only where claims are supported by evidence items tied to source IDs. The graph exists to prevent unsupported narrative leaps.

Largest source burdens
S-0007: 83 items · S-0101: 42 · S-0025: 30 · S-0027: 28.

Most common categories
STAT: 84 · DEF: 36 · APPROP: 35 · DISAG: 27 · UNRES: 24.

Publication unit
The claim, not the paragraph and not the slogan.

Evidence categories

STAT · 84

Statistical evidence

Quantitative records including budget amounts, population figures, workload data, rates, totals, and reported counts.

DEF · 36

Definitions

Terms, program boundaries, statutory definitions, and institutional definitions needed to prevent category errors.

APPROP · 35

Appropriations

Budget authority, enacted appropriations, advance appropriations, TEF structure, and account-level fiscal records.

DISAG · 27

Disagreement / conflict

Places where official sources, oversight bodies, agency statements, or measurement instruments diverge.

UNRES · 24

Unresolved items

Known gaps where the current public record is insufficient for a stronger claim.

DATE / LIM / LAW / REC

Currency and boundaries

Dated evidence, explicit limitations, legal authorities, and recommendation status protect the audit from overreach.

Finding-to-evidence logic

  1. Identify the public question.
  2. Attach source IDs before drafting the finding.
  3. Extract evidence items with category, pinpoint, confidence tier, limitations, and verification status.
  4. Map evidence items to claim IDs.
  5. Promote only supported claim clusters into supported findings.
  6. Keep unresolved, draft, bibliographic, and provenance-labeled claims out of the main finding unless the limitation is explicit.

Next data build

The next upgrade should expose machine-readable claim, source, archive, and evidence registers as downloadable files and searchable rendered tables. This page establishes the public map first so normal readers can understand what the data layer is doing.