V3RUM and TSL8.

The split.

V3RUM is the verification primitive. It produces a sealed artifact binding a moment to a person, a place, a time, and a content hash. It works inside TSL8. It works anywhere a moment needs witnesses.

TSL8 is a format for ideas you want examined — a play sent to a stranger with a crew of AI agents who've read the whole thing. TSL8 has always carried a verification block; the v0 default was LinkedIn, the thinnest shared identity layer most professionals already trust. V3RUM is the cryptographic upgrade.

They're siblings, not parts of the same product. The naming is the giveaway — both use number-for-letter substitution as their identity move (TSL8 → tessellate, V3RUM → verum), which signals that they're a matched set without making one subordinate to the other.

Inside a TSL8 cargo.

A TSL8 cargo can carry a verum at three points:

1. The cargo seal. When the author finalizes a version of the cargo (v0.3, v0.4, etc.), they seal it with V3RUM. The verum binds the cargo hash to the author's identity and the moment of issue. Future readers — and the AI envoy — can confirm that the cargo they're reading is exactly what the author sealed, and when.
2. The reading chain. When a reader engages with the cargo, each page (or each soft-spot they dwell on) gets its own initial-chain entry, sealed with the reader's verum. This proves attention, not just access. The cargo's owner can later answer "did this reader actually engage with §05?" with cryptographic backing.
3. The reply. A reviewer's reply, including any contribution claims, is itself sealed with V3RUM. The reply chains to the cargo it's replying to. Acknowledgments by the author are similarly sealed. The whole back-and-forth becomes a cryptographically verifiable record.

Outside TSL8.

V3RUM is not TSL8-specific. Anything that needs a "this person, here, now, witnessed" proof can use it:

• Inventor's notebooks, sealed at composition time, establishing priority dates with cryptographic floors that no patent challenger can compromise without compromising drand, BTC, FINRA, and the NYT homepage simultaneously at a specific past moment.
• Journalistic source verification, where a reporter wants to prove they spoke with a source on a specific date without revealing the source's identity.
• Contract signing, where the seal supplements or replaces traditional notarization with a portable cryptographic artifact.
• Scientific protocol pre-registration, where a researcher commits to a method before running the experiment.
• Photographic provenance, where the seal binds an image to its capture moment, enabling later proof of pre-deepfake-era authenticity.
• Custody chains for evidence, art, or any artifact whose history matters.

The format is designed to be useful wherever the question is did this actually happen, in the real world, the way the artifact says it did?

The integration on tsl8.app.

Today, TSL8's verification layer is documented at tsl8.app/verification.html. The v0 spec uses LinkedIn challenge-response. The v1 spec — sealed concurrently with the genesis verum — will reference V3RUM as the canonical cryptographic layer, with LinkedIn remaining as a low-tier identity-bridge witness inside a verum.

Anyone using TSL8 today doesn't have to migrate. The LinkedIn-only path remains valid for low-stakes cargos (the format already calls these "sketch" tier). Authors who want stronger seals — for deep-tech disclosures, defensive prior art, foundational claims — opt into V3RUM and inherit the full witness constellation.