Evidence Compiler//DataHub Agent HackathonOpen source ↗
[ PROVENANCE ][ CITATIONS ][ ASSERTIONS ]

Evidence-grounded verification

Every claim traced.
Every gap exposed.

Compile a claim against cataloged DataHub artifacts, classify each segment as observed, derived, or unsupported, and record the verdict as a verification assertion.

Compile a claim →Explore artifacts

Mock and live modes · Browser-local history · Citation-level traceability

Translucent evidence cards connected through a provenance network
example-output.json200 VERIFIED

CLAIM SEGMENTS

Observed

$6.30/hr average wage increase

[A-102]
Derived

Improved employment outcomes

[A-102, A-208]
Unsupported

40% improvement

no citation
Assertion write-back recordedmock mode
01Three-state classificationObserved · Derived · Unsupported
02Citation-level traceabilityArtifact IDs stay attached to segments
03Assertion write-backVerification state recorded in DataHub

01 / 04 · Pipeline //

From claim to catalog

A compact evidence pipeline that makes the source, inference, and unsupported gaps visible at every step.

Step 01

Claim Input

Parse a claim into precise, independently verifiable segments.

INPUT

Step 02

Artifact Mapping

Match each segment to cataloged DataHub artifacts and metadata.

MAP

Step 03

Verification Assessment

Classify support as observed, derived, or unsupported—with reasoning.

ASSESS

Step 04

Assertion Write-Back

Record verification assertions so the verdict stays catalog-visible.

WRITE-BACK

02 / 04 · Workflows //

Evidence under pressure

Designed for moments when a claim must survive scrutiny—not merely sound convincing.

GRANTS

Grant applications

Trace outcome claims back to source artifacts before submission.

Test a claim
REGULATORY

Regulatory evidence

Separate directly observed facts from derived conclusions and gaps.

Test a claim
AUDIT

Audit review

Give reviewers a compact packet with citations, reasoning, and assertion status.

Test a claim

03 / 04 · Browser history //

Past Compilations

Evidence packets compiled in this browser
Loading…

04 / 04 · System notes //

Built for inspection

What is observed versus derived?

Observed means an artifact states the claim directly. Derived means the conclusion follows from cataloged evidence, with the inference and its limits explained.

Does the compiler invent support?

No. When no cataloged artifact backs a segment, the result is explicitly marked unsupported instead of being presented as evidence.

What happens without live DataHub credentials?

The app uses its mock catalog so the complete classification and packet workflow can still be tested safely.

Where is compilation history stored?

Packets are stored locally in the current browser. They are not shared between browsers or devices.

Ready when the claim is.

Turn scrutiny into a traceable packet.

Run the compiler →