Run the evidence check first

A useful Tracer pilot begins with a record set and a conclusion your team needs to defend. Before asking for access, verify that the product's method fits that job.

1. Run the live demonstration and open one finding to inspect its source.
2. Scan a Jira export if the disclosed data boundary fits your records.
3. Choose one decision to evaluate: a release review, an audit request, or a customer evidence question.

What to bring

1. Export the Jira search for the project you want to defend.
2. Bring one test-results file in JUnit, CTRF, or OTLP form.
3. Name one decision the team has to defend: a release review, an audit request, or a customer evidence question.

A team that arrives with all three sees a verdict in its first session.

Already participating?

Sign in with your organization key. Organization access is provisioned manually while passkey sign-in is being built.

What a pilot must prove

The evaluation should show whether Tracer can identify the source records behind a conclusion, name the gaps that prevent one, and produce evidence your reviewer can independently inspect. No outcome is promised before that evidence exists.

Read the public claim ledger before treating any quantitative statement as evidence.

Pilot intake is not automated. Tracer does not collect contact information on this page.