Provenance Proof you made it
Provenance · authorship layers for anything you publish

AIs watermark their outputs. Why don’t you?

  • Protect your IP. Any page, text, or creation.
  • Upgraded with layers of proof, from a footer notice to a Bitcoin timestamp.
  • Don’t let AI, or anyone, eat your lunch.
The problem

Don’t let AI eat your lunch.

  • Publishing is instant. Copying is instant. Credit isn’t.
  • Models train on your words. Summaries drop your name.
  • Google marks its AI text. C2PA signs AI images. Your work ships naked.
The idea

Layers, not a lock

  • One mark can be stripped. Eleven can’t all be.
  • Some are loud. Some are invisible. Some only a machine will notice.
  • Each copy carries whatever layers it didn’t know to remove.
Eleven layers, surface to deep

Every layer answers a different thief.

  1. Notice & license© line, CC BY or all-rights, how-to-cite. For honest reusers.
  2. Machine-readable creditschema.org author, meta tags, llms.txt. For search and AI crawlers.
  3. Coined-term fingerprintsYour unique phrases, tracked. The only mark that survives paraphrase.
  4. AcrosticsFirst letters of headlines or lines spell your name. Invisible until noticed.
  5. Morse & rhythmA divider’s dashes, a glow’s pulse, spelling you in Morse.
  6. Punctuation MorseStraight and curly apostrophes alternate to spell you. How Genius caught copied lyrics in 2019.
  7. Asset metadataAuthor and license inside every SVG and image. Travels with the file.
  8. BreadcrumbsA clue ladder from source to console to a hidden card. For the curious.
  9. Training canaryA unique string. If a model can finish it, it trained on you.
  10. SignatureYour canonical text, signed with your key. Verifiable by anyone.
  11. TimestampHash anchored in Bitcoin via OpenTimestamps. Proof it existed first.
Hidden in plain sight

Your name, in the first letters

  • We rewrite only the first word. Meaning stays. Voice stays.
  • Copy the page, keep the headlines, keep the signature.
  • Every build re-checks it, so an edit can’t quietly break it.
Rhythm

A divider that spells your initials

  • Dots and dashes drawn as a hairline. Looks like design.
  • Screen readers skip it. Screenshots keep it.
  • The same code can pulse in a glow or a loader.
Training canary

Know if a model trained on you.

  • We plant one unique string where crawlers read.
  • Later, ask any model to finish it.
  • If it can, it learned from your pages. The same trick benchmark authors use.
Proof that holds up

Signed by you. Stamped by Bitcoin

  • Your canonical text, hashed and signed with your key.
  • The hash is anchored in Bitcoin with OpenTimestamps. Nobody can backdate it.
  • Anyone can verify both with free, standard tools.
Order of operations

Ten steps. Most impact first

  1. ClaimCopyright line + license + how-to-cite on every page.
    Minutes
  2. DescribeAuthor metadata, schema.org CreativeWork, llms.txt.
    Minutes
  3. SignGenerate your key. Publish the public half. Sign your canonical text.
    Minutes
  4. StampOpenTimestamps on every signed version. Auto-upgraded once Bitcoin confirms.
    Minutes
  5. PlantA training canary in source and llms.txt.
    Minutes
  6. CoinList your unique terms. We track them across the web.
    An hour
  7. HideAcrostics, Morse dividers, punctuation Morse, asset metadata. Only first words change, with your approval.
    An hour
  8. LeadBreadcrumbs: a clue ladder for people and agents who look closer.
    Optional
  9. RegisterCopyright registration where it counts (US: required to sue).
    A form
  10. WatchEvery deploy re-checks every layer. Alerts on your terms. Scan suspected copies.
    Always on
Websites · pages · text API

Wherever you publish

Websites

A build step

Add Provenance to your static build or CMS. Every deploy adds the layers and re-checks them.

  • Breaks are flagged by page and mark
  • Signature and stamp kept current
Pages

Paste a URL

Get back the upgraded page, the proofs, and a punch list of what we changed and why.

  • You approve every word change
  • Downloadable evidence pack
Text API

One request

Send text, get it back marked, signed and stamped, ready to publish anywhere.

  • Posts, papers, newsletters, prompts
  • Checker endpoint for copies
# mark a post before you publish it
curl -X POST https://api.provenance.dev/v1/mark \
  -H "Authorization: Bearer $KEY" \
  -d '{"author":"Your Name","text":"...","layers":["notice","acrostic","canary","sign","stamp"]}'
# -> { "text": "...", "signature": "...", "ots": "...", "canary": "PROV-7f3c...", "report": [...] }
The checker

Spot a copy in seconds.

  • Point it at a page, a folder, or a URL.
  • It decodes the acrostics, the Morse, the metadata, the canary, the signature.
  • Out comes an evidence score and exactly what matched.
Built and running on aliabdulla.com

Dogfooded first

Provenance started as the proof layer for Ali Abdulla’s UTOPS essay: every mark below is live there and re-checked on every build, in a real browser.

25marks, checked every build
11layers, surface to Bitcoin
0visible clutter for readers
14.5evidence score for a full copy (vs 0.0 unrelated)
The honest part

Proof, not magic

  • Copyright protects your expression. Ideas alone aren’t ownable.
  • A from-scratch rewrite carries no hidden marks. Your coined terms still leak.
  • Registration gives the legal teeth. We tell you when and how.
  • No zero-width tricks. Nothing that breaks screen readers or search.
Early access

Publish like it’s yours.

  • First sites get all eleven layers set up with them, by hand.
  • Websites, single pages, or the text API.

Ali@AliAbdulla.com