VeritaDoc — draft, route, counter-sign. Executed originals you can verify forever.

From first draft to executed original

Four steps. Every signature is an Ed25519 signature over the document hash. The executed original bundles the document and every signer's signature into one verifiable artifact.

1 · Draft

Pick a template, fill it in

Choose from NDA, offer letter, consulting agreement, MSA, SOW, waiver, board resolution. Or upload your own PDF. Typed fields (party, date, dollar amount, jurisdiction) become structured data, not freeform text.

2 · Route

Send a session URL to counter-parties

Each signer gets a URL. They review the document, see the full text, and sign with their Ed25519 key (browser WebAuthn, hardware key, or Verita-family identity). Ordering is declared and enforced.

3 · Counter-sign

Signatures accumulate, in order

Each signature commits to the document hash and the hashes of prior signatures — so a signer after you can't silently modify what you signed. Witness timestamp is collected at execution.

4 · Execute

One PDF + one sidecar = forever

The final executed original is the PDF plus a small .sig.json bundle. Together, they're verifiable offline with any VeritaDoc client — or by hand against published spec — long after any vendor has gone.

The executed original is not locked to a vendor

Other e-sign tools cover the same signing workflow. The difference shows up ten years later, when you still need the audit trail but the vendor has been acquired, repriced, or shuttered.

Audit trail lives where

vendor's database

bundled into the executed PDF

Verify a signature 10 years later

vendor must still exist & cooperate

run the verifier, offline

Signing key belongs to

the platform (on your behalf)

the signer (Ed25519, WebAuthn)

Executed-original format

proprietary, with vendor watermark

PDF + open-spec .sig.json

Counter-sign ordering integrity

vendor's log

each signature commits to prior ones

A starter library for common docs

Typed-field templates so "effective date" is a date and "party name" is a party, not freeform text. Upload-your-own PDF is first-class too.

Mutual NDA

mutual / unilateral variants

Offer Letter

at-will, exempt/non-exempt

Consulting Agreement

fixed-fee or T&M

MSA

master services agreement

SOW

statement of work

Waiver

liability / media release

Policy Ack

handbook acknowledgment

Board Resolution

with secretary certification

Verify an executed document with a single command

The verifier ships as a CLI and a library. It reads the PDF, the sidecar bundle, and tells you exactly who signed, in what order, and whether the document has been touched since.

Nothing is trusted by default. The verifier checks every signature against its signer's published key, walks the commitment chain to confirm ordering integrity, and validates the witness timestamp against an RFC 3161 trust root.

If the document was modified after signing, any signature was forged, or the ordering was tampered with, the verifier says so — and refuses to report "valid."

Published spec. Reference implementation. Reproducible from the ground up.

$ verita doc verify nda.signed.pdf nda.sig.json
✓ valid executed original

  document       Mutual NDA (2026-Q2 template, v1.4)
  sha256         a3f1c2…9b4e
  signers        2/2 required, in declared order
    1. ✓ J. Ramirez · Acme Robotics
         signed 2026-04-12T14:20:51Z
    2. ✓ M. Chen   · Northwind Consulting
         signed 2026-04-12T14:22:07Z
         (commits to prior signatures ✓)
  witness        RFC 3161, Let's Timestamp CA
                 ✓ 2026-04-12T14:22:07Z

VeritaDoc witnesses signatures; it does not notarize them. Notarization is a jurisdiction-specific legal role (usually requiring a commissioned human notary public). VeritaDoc records cryptographic signatures, counter-signature ordering, and a witness timestamp — legal effect derives from the signatures themselves under applicable e-signature law (ESIGN, UETA, eIDAS), not from VeritaDoc acting as a notary. For documents that specifically require notarization (some real-estate transfers, affidavits, etc.), use a commissioned notary.

Part of the Verita- family

VeritaDoc is the workflow sibling. It reuses the family's identity scheme and signature format; the routing and counter-sign layer is where the document-specific logic lives.

VeritaCrypt

sign / notarize files

VeritaPath

trace event lineage

VeritaLink

preserve URL targets

VeritaVault

seal & guard secrets

VeritaPad

p2p messaging w/ transcript

VeritaBase

family substrate

VeritaBadge

issuer-signed credentials

VeritaPoll

group polls, provable tally

VeritaCast

signed broadcast feeds

VeritaChart

flowcharts + signed export

VeritaDoc · this one

draft & countersign business docs

Business documents,
executed for keeps.

Mutual Non-Disclosure Agreement