Inspect · Reproduce · Build

A clear path from demonstration to evidence.

TRIA's mechanisms can be run, examined, and challenged. Start with a familiar workflow, then follow the source and tests behind each claim.

Experimental alpha. The links below identify executable evidence and its scope. They are not a claim of independent validation, production readiness, or measured human benefit. For current test results, inspect the exact commit in continuous integration.

Run the reference experience Reproduce it independently →

What can you check?

Claim within scope	Executable evidence	Practical limit
Withdrawing declared consent or permission stops a subsequent governed handoff.	Five-step reference application Execution boundary tests	The host must declare complete requirements and use the governed handoff. Already-entered external effects are not undone.
History can survive closing and reopening storage.	Complete SQLite example Persistence tests	Integrity does not establish that a recorded assertion was true or an actor authenticated.
An observation, interpretation, and dispute remain distinguishable.	Contested Reality scenario Scenario tests	A contested interpretation is a claim status, not automatically a blocked action.
Diagnostics distinguish enforced findings, advisory signals, and missing evidence.	Synthetic diagnostic controls Diagnostic contract tests	Public authored controls test specified behavior, not discovery of unknown failure families.
A protocol exists to compare agent decisions under matched evidence.	Three-condition comparison harness Guarded model pilot protocol	Mock smoke tests verify the harness. They do not demonstrate improved model decisions.

Why preserve earlier failures?

A frozen audit records what happened at a particular version. Keeping that record lets a reviewer distinguish the original failure, the repair, and the test of the repair. A new passing run does not erase an older result.

Read the revalidation record · Check version boundaries

Choose your next step

Build an integration

Install TRIA, run the complete application, then adapt one bounded workflow.

Quickstart →

Reproduce the evidence

Use the independent developer protocol. Record friction and discrepancies before asking the build team for help.

Developer handoff →

Propose a bounded pilot

Describe the workflow, participants, what TRIA would mediate, and the outcome you want to measure.