TC Verify Explorer — Independent Verification for Technocore Activity

Cross-Generation Proof Engine

C7 Consistency Experience

C7 proves consistency between two roots when the newer tree contains the earlier tree as an exact prefix. It does not provide an external witness or prevent divergent histories by itself.

✓ CONSISTENT Gen 1 (size 4) → Gen 2 (size 6)

Generation 1 Root (size 4): 0373cfc78e0b17cd733fd38318af51e119ef366954b0a0fbcba251ef15b066b9 ↓ Generation 2 Root (size 6): 792e762d74456dab8b4905490213491d6d4533a10f333da7447c2541bb81d341

"New tree is an exact-prefix extension of the earlier tree."
The RFC 6962 consistency proof (1 intermediate node: b146097a...) mathematically establishes that all 4 records from Generation 1 exist unaltered in Generation 2.

✕ CONSISTENCY NOT ESTABLISHED Gen 2 (size 6) → Gen 3 (evicted)

Generation 2 Root (size 6): 792e762d74456dab8b4905490213491d6d4533a10f333da7447c2541bb81d341 ↓ (Record 0 pruned by server log retention) Generation 3 Root (size 5): e8a1f2b3... [Not an extension of Gen 2]

"The newer export is not an exact-prefix extension of the earlier export."
Eviction can destroy the retained bytes needed to independently verify earlier records. C7 therefore fails when the newer export is no longer an exact prefix of the earlier export.

Verification is conditional on trusted inputs. TC Verify evaluates retained evidence against a root you already hold via the TC-Ledger engine. The explorer does not establish the provenance of that root, authenticate envelope metadata, or provide trusted timestamping by itself.

Retained activity is not guaranteed to represent complete lifetime history. Retention/eviction can remove the original bytes required for independent verification.

Room & Sequence	`demo-room` • Seq 1 • Nonce `1002`
Timestamp	—
Signer DID	—
Message Text	—
Ed25519 Signature	✓ VALID
JCS Evidence ID	—
RFC 6962 Leaf Hash	—
Merkle Inclusion	✓ VALID
Committed Root	—

Available Activity

#research Activity

C7 Consistency Experience

Verify Evidence Locally