VAULTMARK

A publication trail you can inspect.

VaultMark records durable book and collection checkpoints, separate publication and Story Bible identities, exact release-file identities, and optional device signatures in a portable hash-linked history. Verification happens locally and needs no Wexley account.

Verify a bundle

Website verifier 1.1.0 · No upload · No private key · Runs locally

HISTORY VERIFIED
01
Writing checkpointPublication + Story Bible identities · device-reported time
linked
02
Release recordedSHA-256 + exact byte length
linked
03
Release sealedES256 signature under included public key
valid
HEAD  8bb1b29e80fe6407…
LOCALSelected files stay in your browser
PORTABLEThe JSON bundle travels with your release
NO UPLOADVerification stays in your browser
SEPARATEIntegrity, signatures, time, and coverage

HOW THE TRAIL WORKS

Each record commits to the one before it.

VaultMark turns meaningful saved stages into an ordered chain. Later seals cover the records before them without rewriting earlier history.

01

Separate content identities

Reader-visible book or collection semantics become one SHA-256 identity. Durable Story Bible data gets a separate identity. Neither manuscript nor planning content is placed in the bundle.

02

Hash-linked record

Each record commits its publication and optional Story Bible identities, production context, word count, device-reported time, and the exact hash of the preceding record.

03

Optional device seal

A milestone or release seal uses ES256. Anyone can verify it under the public key included in the exported history.

PRECISE BY DESIGN

One “valid” badge would hide too much.

VaultMark reports each assurance dimension separately, so an internally consistent unsigned bundle cannot be confused with a signed release.

Integrity
Are record shapes, hashes, order, ownership, schema direction, and the final head internally consistent?
Signatures
Do all included ES256 seals verify under their included P-256 public keys?
Time
Dates are device-reported; the bundle export date is unsigned. Neither is a trusted timestamp.
Identity
The key is self-asserted device-key identity—not verified human identity.
Completeness
Unknown. VaultMark does not prove a bundle is the latest copy or contains every edit.
Coverage
Do exact artifact bytes match a release record covered by a valid later seal?

WHAT IT CAN SHOW

Recorded bytes and history match.

  • Internal hash-chain integrity
  • Separate publication and Story Bible digest identities
  • Signatures under included public keys
  • Exact EPUB, DOCX, PDF, or ZIP byte identity
  • Which later valid seal covers a release record

WHAT IT DOES NOT PROVE

Claims beyond the cryptography.

  • Human identity or legal authorship
  • Copyright ownership or originality
  • Trusted or independently witnessed time
  • Secure erasure or rollback prevention
  • Complete history or latest-copy status

WEBSITE VERIFIER

Check a VaultMark bundle in your browser.

Select an exported history and, optionally, its release file. Verification runs locally on this page without uploading either file or requiring a Wexley account.

Open website verifier