OpenProof
Application example →The product and document review workflow in development. Decisions remain human.
OPENPROOF LEGAL · LEGAL PROFESSIONALS
Scattered documents. OpenProof organises the evidence, links each finding to its source, preserves contradictions and reservations, then submits the result to human review.
View a reconstructed case ↗Explore the Investigation module — 15 min →
Fictional example without an account · prewritten observations · product in development

TRUTHX · THE TECHNOLOGY IN CONTEXT
The product and document review workflow in development. Decisions remain human.
The structuring and control engine. Multi-agent research will be connected progressively, with results that can be evaluated.
The public structured record format and its integrity check. A fingerprint checks for changes, not the truth of the content.
Read the documentation →01 / THE PROBLEM TO SOLVE
For people examining complex cases: operations, audit, compliance, research and legal document review. Our first collaborative workstream is preparing a case for human review.
Find the original passage, so a summary can be checked against its sources.
Keep competing versions, disagreements and missing documents visible until reviewed.
Prepare a case where the next reader can recover sources, reservations and review decisions.

The conflict remains complex. The record becomes readable.
02 / SOMETHING YOU CAN EXAMINE
Now two founders blame the third for spending, lost customers and disruption. His role, shares, reputation and personal finances are at stake. How can he respond without losing the facts in the conflict?
Examine collective decisions, individual shortcomings and what remains uncertain. Each finding links to a fictional excerpt you can read.
Ready to examineFive allegations, eight fictional excerpts, a timeline and open questions.
Educational examplePrewritten findings, without demonstrating automatic contradiction detection. Decisions remain human.
03 / PLANS & PRICING
Explore the public example, planned software uses and access conditions. The per-case, monthly and annual comparison is available without an account; purchases and subscriptions are not open yet.
View the plans →LET’S TALK ABOUT YOUR NEED
A question, a research contribution or a partnership project? Tell us your objective and the next step you would like.
gersende.ryard.de.parcey@truthx.coDescribe your need without attaching documents or sharing confidential information.
04 / A FOUNDER. A RESEARCH FOUNDATION. A NEXT CHAPTER.

TruthX founder and OpenProof product designer, Gersende connects her transformation experience to an operational question: how can we reconstruct what supports a decision? She designed the initial thirteen-module architecture and leads priorities, contributions and acceptance.
Gersende’s background and commitment →GREYC / UNIVERSITÉ DE CAEN NORMANDIE · 2025–2026
Under Professor Gaël Dias’s academic supervision, Lucy Martin and Clément Correia-Peltier developed a multi-agent prototype and delivered their code, report and presentation in May 2026. Their work covers document extraction, consistency checks, structured analysis and report generation.
This prototype is a research foundation. Integration into the current engine still needs to be implemented and evaluated.
Research and contributions ↗05 / THE OPENPROOF COMMUNITY
A case can cite its sources and still leave part of the story out. In our fictional example, three cofounders fall out: shared decisions, disputed spending and conflicting evidence must remain open to review.
Choose one claim. Find what supports it, what challenges it and what is still missing. Your perspective can help improve the method and the readability of the report. No coding is needed for a first review.
You are testing one OpenProof module: the Investigation workspace and its interactive map. Fictional case, no payment; no private case is opened.
The general form remains available without a GitHub account.
View GitHub thread #44 ↗Follow the work with Gersende →Suggested time. Reading is open; a GitHub account is needed to reply. Entirely fictional material, prepared for the demonstration.

One source passage, one proposed correction and a remaining question.
30 min · #45Identify where a reader hesitates and suggest a clearer layout.
45–60 min · #46An example of a valid, invalid or insufficient reference.
Proposals are reviewed in their GitHub thread. Accepted contributions are credited and linked to the resulting changes.
A GitHub account is needed to reply. Fictional examples only. The complete engine is not yet released under an open-source licence.