Product overview · three pages
SignetStudio

The black-box flight recorder for creative work

Studio is not a creative tool. It is a submission record for creative work. It lets a client, agency, publisher, or distributor say: “If this media carries AI, ownership, consent, or reputational risk, submit the work with a Creative Origin Record.

getsignet.app/studio

The problem in four questions

Media is now something an organization has to answer for. Four questions surface the liability exposure — and all of them come down to one thing the organization must be able to define: how was this made?

"Is this AI — and did we label it correctly?"
Disclosure law — EU AI Act Art. 50 and California SB 942, both effective August 2, 2026
"Do we actually own this?"
Copyright — mixed AI/human work is protected only as to the documented human contribution
"Did the people in it consent?"
Likeness and voice rights
"Will this hold up if it's challenged?"
Evidence and disputes

Nobody can answer these from a finished file. Detection is a moving target — an unreliable probability score at best. No regulator, client, or court accepts "the model said 87%."

The insight

The evidence exists while the work is being made — during capture, editing, generation, and handoff. Today it evaporates. Signet Studio captures it as it happens, so nobody has to guess at the output.

What it does

Studio makes the creative process documentable across the real tools and handoffs a production pipeline uses.

It does not require Adobe, OpenAI, browser apps, camera systems, or other toolmakers to participate. Studio runs above the tool layer. Once contributors enroll their devices and setup the apps or browser tabs used for the project, Studio records configured workflow events and visual samples while they work normally.

The result is a Creative Origin Record: a signed, independently timestamped, tamper-evident coverage map of the work. It shows what was witnessed, what was declared, what credentials were present, what sources were used, where AI appeared, where handoffs occurred, what gaps remain, and who accepted or left those gaps unresolved.

Studio does not block the work and does not issue a verdict. If something is missing, skipped, offline, or undeclared, the record says so plainly. The contributor can continue, and the client, agency, distributor, legal team, or reviewer decides whether the remaining risk is acceptable.

Set the requirement
The organization defines when a Creative Origin Record is required for vendor submission, client delivery, editorial review, or internal approval.
Enroll the workflow
Contributors enroll the devices, apps, browser tabs, sources, and handoffs used for the project. The watch profile is written into the record before collection begins.
Create normally
The work continues in the tools the team already uses. Studio runs in the background, recording configured events, visual samples, source declarations, credentials, handoffs, and gaps.
Submit the record
The finished asset arrives sealed to its Creative Origin Record. The record includes the timeline, contributor signatures, declared and attested sources, credential checks, AI-use indicators, missing information, and review flags.
Review the coverage
Editorial, legal, compliance, client, or distributor teams read the record before use. Studio does not auto-reject work or assign an authenticity score. It shows the evidence and the gaps so accountable humans can make the decision.

Events are triggers, never payloads. Studio samples the work, not the worker. No keystrokes. No clipboard contents. No capture when the app isn't focused. The record itself documents exactly what was collected — and the contributor agreed to the profile before the first sample.

What creates the record.

Studio captures timestamped workflow evidence: source declarations, app/file events, visual samples, credential checks, contributor attestations, handoffs, and gaps.

Timestamped project events
lightweight visual samples of the work in progress
declared source files and signed statements of origin
C2PA/content credential checks where available
contributor signatures and handoff history
gaps, unsupported sources, and review flags
a final seal binding the record to the delivered asset

What a record establishes

Every gap is disclosed, never hidden — gaps in time are flagged, sources without provenance prompt a request for a signed statement of origin, and the record states exactly what it covers. Nothing blocks and nothing is forced: disclosure is always invited, never required, and absence is simply noted. Signet makes no determination — no authenticity score, no verdict, no AI judging the work. It assembles the evidence; it does not decide which direction the evidence moves the narrative. The accountable human makes the call.

C2PA-supportive by design: credentials are read where present, their absence recorded plainly, and a fresh manifest is written into the deliverable at seal. The record lives outside the file — a stripped manifest doesn't break the chain.

Honest limit: fraud is still possible. Anonymous, deniable, consequence-free fraud is not. To lie through Studio, someone has to sign a false statement, as an identified person, next to a witnessed timeline that invites scrutiny.

And there's a deeper reason gaming it doesn't pay: Studio changes nothing about how the work is made — it only witnesses it. A real record gets its texture from the density of human decisions that creative work actually produces: the opens and saves, the revisions, the rejected directions, the course corrections. To fake that trail convincingly, you'd have to perform a work's worth of decisions anyway — at which point the system is witnessing genuine human direction again. Gaming the record is self-defeating; the cheapest way to produce a strong one is to do the work.

How it runs

Cloud (standard)
All collection and sampling runs locally on each contributor's device, tracked by project and contributor. Only sealed, signed record segments sync to the cloud as they're built — final files never leave your machines, and working data is retained, archived, or deleted on a schedule you choose. The organization gets a dashboard; each Creative Origin Record is a self-contained file the client controls — private or public, versioned on re-certification, always available.
On-prem (closed network)
For government, legal, and data-sensitive organizations: fully self-contained deployment inside your network, with an internal verification tool. Same record format, same open verifiability.

Who it's for

Creative and production teams delivering work under contract — where AI-disclosure clauses, indemnities, and ownership questions are already in the paperwork. Established studios use the record to make their craft attributable; AI-native teams use it to show enterprise clients exactly where AI generated and where humans directed.

Verify it yourself

Every record verifies in any browser — no account, no upload, nothing sent to us.
View a live Creative Origin Record: getsignet.app/studio
Open verifier: getsignet.app/verify

QR code — live Creative Origin Record

Signet Studio is built by Signet Proof, Inc. — provenance infrastructure for accountable digital creation. Its sibling product, Signet Academic, applies the same evidence-not-detection architecture to student writing.

Partner-studio pilots open now — book a walkthrough at getsignet.app/studio · hello@getsignet.app

Signet

Signet Proof, Inc. builds provenance infrastructure for accountable digital creation.

ResourcesFeatures
CompanyContact
© 2026 Signet Proof, Inc. All rights reserved.getsignet.app