Titan records why every signal was forwarded or blocked, then commits a daily fingerprint of those records to the Bitcoin blockchain. The result: you don't have to trust Titan's database. You can verify a decision was recorded exactly as shown — and hasn't been altered since — with nothing but a block explorer and the math below.
This is the honest division of trust: the chain proves what was decided and that it stands unaltered, not whether the decision was sound. Separate problems, separate solutions.
The verifier below runs entirely in this page — a dependency-free RFC 6962 Merkle walk plus the same fingerprint hashes Titan uses internally. From the decision's recorded preimage fields it recomputes the chain-leaf hash, folds that up to the daily account Merkle root, recomputes the account fingerprint, folds that up to the day's aggregate Merkle root, and recomputes the aggregate fingerprint. That last value is exactly what Titan hands to OpenTimestamps. At each step it recomputes rather than trusts the bundle; if anything doesn't match, it shows a failed verdict.
Verified span: the decision row fields chain, unbroken, to the aggregate fingerprint submitted to OpenTimestamps. Bitcoin boundary: this browser walk stops at that fingerprint; OpenTimestamps and the block links below show where it landed, and you close the final gap by checking that fingerprint against Bitcoin yourself (Sections 03–04).
The aggregate root for that day landed in these Bitcoin blocks. Open any of them — the block's own Merkle root matches the commitment Titan submitted. You're checking Bitcoin, not Titan.
To walk this decision's internal chain in your own browser, load its proof bundle into the panel above — exported with python -m titan.audit_chain_verify 97b984df… --emit-bundle. The browser recomputes the decision row's chain-leaf hash before walking to the aggregate fingerprint b926e6…; that fingerprint is what OpenTimestamps committed to the Bitcoin blocks above, independently checkable right now.
The calendars report “block N contains root X.” Accept it and stop. Cheapest path; you trust their word.
mempool.space, blockstream.info, any equivalent. You trust an explorer's view of Bitcoin — not the calendars, not Titan. The blocks above land you here.
A pruned Bitcoin Core node (~10 GB) validates every block from genesis. You trust no third party — only proof-of-work and your own machine. ots verify --bitcoin-node … against the downloaded proof.
The chain is identical at every rung. Climbing it doesn't make the decision more anchored — it just removes the last third party you were willing to trust.