Evidence Standard

No source, no branch.

ProofBranch is being built for a world where agents can accelerate research, but every proposed tree update still needs provenance, conflict visibility, and human approval.

Request early access

The bar

Speed is useful only when the evidence survives inspection.

Family-history platforms cannot treat tree changes like ordinary text generation. A good answer must carry its sources, show its uncertainty, and make the reviewer’s decision easier.

Two historical records compared side by side with source annotations, chronology markers, and visible conflict highlights
01

Evidence first

A proposal should be grounded in source material and preserve the record trail that led there.

02

Chronology aware

Dates, places, life events, and household context should constrain what the agent is allowed to suggest.

03

Conflict visible

Contradictions should become review prompts, not hidden weaknesses inside polished prose.

04

Provenance preserved

Extracted facts should remain connected to source images, citations, notes, and the reasoning path.

05

Human approval required

The final tree decision belongs to the researcher or platform review flow. The agent prepares the case.

For serious platforms

Build research speed around a standard your users can trust.

ProofBranch is prelaunch and looking for early partner conversations.

Request early access