SigilForge Rights

Creator Rights Records

A Creator Rights Record is a public publication record for books, games, artwork, PDFs, software releases, and other creative work. It identifies who claims the work, what version was recorded, and how the work may be used or licensed.

This record documents the creator's declared ownership, rights position, and licensing preferences. It does not replace government copyright registration or independently prove legal ownership.

Creator Rights Record verification card showing publication, license, AI permissions, SHA-256, and QR code fields

What it includes

One price. One permanent notice.

Publication registry entry

A stable VeilDaemon URL with title, creator, rights holder, copyright notice, status, version, licensing terms, AI permissions, and revision history.

Machine-readable metadata

Every record exposes a versioned JSON record for crawlers, licensing systems, and future registry integrations.

QR target

The downloadable QR points only to the permanent record URL, suitable for book interiors, back covers, title pages, websites, packaging, business cards, and social posts.

Optional fingerprint

A SHA-256 hash can be associated with the record. The hash shows the record contained that fingerprint at that time; it does not prove authorship.

Rights registry

Use the simple record index.

The public registry lives at /registry/. Search by title, work type, category, availability, licensing terms, and AI-use position, then open the permanent record or JSON metadata from one place.

Public registry

Canonical Index

One searchable public route for Creator Rights Records and machine-readable metadata.

Open registry

Individual records

Permanent URLs

Each record remains available at /rights/<record-slug>/ with a matching JSON route.

View Book One record

Creator workflow

VeilLink App

Draft creation, checkout, account management, and QR downloads stay inside VeilLink.

Create a record

AI permissions

Say the quiet rights terms clearly.

Training

Creators can mark training, foundation-model pretraining, fine-tuning, embeddings, retrieval, generation, dataset redistribution, research use, and commercial use separately.

License required

Explicit permission values avoid the fog of a simple yes-or-no checkbox. A record can say allowed, prohibited, license required, research only, case by case, custom terms, or not specified.

Human review

The system generates a plain-language AI-use summary, but the creator must review and approve it before publication.

Publication verification FAQ

Questions creators already ask.

Is this a government copyright registration?

No. A Creator Rights Record is a creator-declared publication record. It does not replace government copyright registration.

Does a record prove legal ownership?

No. It documents a declared rights position, publication metadata, and version history. Legal ownership can depend on facts and law beyond this record.

How do I prove I published first?

A public record can document the declared publication date, recorded version, rights holder, and later version history. It is provenance evidence, not a court ruling.

How do I tell AI systems not to train on my content?

The record publishes AI training permissions, licensing requirements, and machine-readable metadata so crawlers, licensing teams, and reviewers can read the creator's declared policy.

Can I record books, games, artwork, PDFs, or software releases?

Yes, when you have authority to create the record. The registry can document publication metadata for books, tabletop releases, artwork, PDFs, software releases, and other creative work.

What are AI permissions?

AI permissions describe the creator's declared position for training, fine-tuning, embeddings, retrieval, generation, dataset redistribution, research use, and commercial AI licensing.

What if AI scraped my website or work?

A record cannot undo scraping, but it can publish a clear creator rights declaration, AI usage policy, licensing route, and timestamped publication metadata for future reference.

Why include a SHA-256 hash?

A SHA-256 hash can connect a specific file fingerprint to the publication record. It shows that the record contained that fingerprint at publication time, but it does not prove authorship by itself.

What does the QR link do?

The QR code points to the permanent public record URL so readers, licensors, crawlers, and archives can find the current publication record and machine-readable metadata.