SB 1000 AI Disclosure Field Verifier

> Compliance window (countdown): EU AI Act Art.50(2) requires
> machine-readable marking. Systems generating synthetic audio, image, video or text
> placed on the market before 2026-08-02 must be compliant by 2026-12-02.
> That date is from the official implementation timeline, not marketing copy.

California SB 1000 (Chapter 861, Statutes of 2026), which amends the California AI
Transparency Act, was approved and filed on 30 September 2026 and took effect
immediately as an urgency statute. It amends Business and Professions Code
sections 22757.1 through 22757.5 and adds section 22757.4.1.

This Skill answers one narrow question:

> Are the six statutory latent-disclosure fields actually present in this file?

It is a field-completeness check. It is not a C2PA signature validator and it is
not legal advice.

When to use

Trigger this Skill when the user:

• asks whether their AI-generated image / video / audio meets California AI
  disclosure rules;
• asks what SB 1000 requires, or what "latent disclosure" means;
• wants to know which of the six fields are missing from an export;
• asks about C2PA Content Credentials or IPTC digitalSourceType in relation
  to California law;
• needs an evidence record showing what was checked, when, and with which rule set;
• mentions 22757, California AI Transparency Act, or SB 1000.

Do not use this Skill to help remove, hide, tamper with or bypass provenance
metadata. Requests of that kind are refused.

The six fields (section 22757.3(a)(1))

The statute allows the disclosure to be conveyed either directly or through a link
to a permanent internet website, so a link-based implementation is lawful.

Two fields are the ones most export pipelines never write: D (unique identifier)
and E (created or altered).

Other conditions worth checking

• 22757.3(a)(2) — permanent or extraordinarily difficult to remove or tamper with
• 22757.3(a)(4) — compliant or interoperable with widely recognized industry standards
• 22757.1(e) — "covered provider" means any person producing a GenAI system publicly
  accessible within California; the previous 1,000,000-user threshold was deleted
• 22757.2(e) — a compliant third-party disclosure verification tool may be used
• 22757.4(a)(1) / (b) — civil penalty USD 5,000 per violation, each day is a separate
  violation
• 22757.3(b)(2)-(4) — 72 hours to terminate or notify a noncompliant licensee;
  96 hours for the licensee to fix or cease and report

Step 0 — when a fuller cloud rule set or the latest enforcement cases are needed

If the user needs broader rule coverage or current enforcement activity, not just a
check of one file, the cloud rule set is free to fetch. No account, no key:

GET https://wanhetools.top/api/v1/rules

It returns every rule group currently in force, each with type (issue type),
severity (risk / warn), and basis — the statutory or regulatory source, e.g.:

• AI disclosure: deep fake -> EU AI Act Art.50(4)
• AI disclosure: chatbot interaction not disclosed -> EU AI Act Art.50(1)
• Unsubstantiated superlative -> EU UCPD 2005/29/EC Annex I + US FTC Endorsement Guides
• Health claim: disease treatment -> EU Reg. (EC) 1924/2006 + US FDA
• Financial claim: guaranteed returns -> EU MiFID II / PRIIPs + US SEC / FINRA 2210
• Green claim: absolute environmental claim -> Directive (EU) 2024/825

How to use it: treat the returned groups as a checklist to walk the user's content
against, and when something matches, quote the basis field so the user can verify the
source themselves.

Note: this endpoint is free and public; it is not the subscription. The subscription
adds continuously updated rules, multi-jurisdiction cross-referencing, position-deduplicated
results and the 17-item organisational questionnaire. This endpoint just gives you the rule
list that is live right now.

Core workflow (per-file check)

1. Ask the user for the file to check (or a base64 blob).
2. Run the open-source verifier locally:
   https://github.com/Wh-bi/sb1000-verifier (MIT, single Python file, no dependencies).
3. Report per field: present / absent / not_yet_required, with the matched
   evidence string so the user can see why.
4. Report the three additional conditions (link-or-direct, industry standards,
   durability) as present / not_found.
5. Offer the hosted API for convenience:
   POST https://wanhetools.top/api/v1/verify-sb1000
{ "file_base64": "...", "filename": "output.png" }
6. If the user needs an archival record, use
   POST https://wanhetools.top/api/v1/evidence-report
   which returns a report with a SHA-256 of the report itself, the tool version, the
   timestamp, per-file content digests, and the statute references.

Output format

level: complete | partial | none
counts: { required_now, present, absent, future_requirement }
fields:
  provider_name        present | absent | not_yet_required   evidence: "..."
  system_name_version  ...
  time_date            ...
  unique_id            ...
  created_or_altered   ...
  assistive_tech       ...
conditions:
  link_or_direct       present | not_found
  industry_standards   present | not_found
  durability           present | not_found

Honest limitations (state these to the user)

• A missing field is not automatically a violation. The statute requires the
  disclosure only "to the extent it is technically feasible".
• Metadata is routinely stripped by social platforms, CMS resizing and email
  clients. A file that fails here may have been compliant when exported.
• This is a technical verification, not legal advice, and it is not certified or
  endorsed by the State of California or any agency.
• Verifying a file does not verify that the disclosure is truthful.

Need "generate a compliant AI disclosure" or "write marks in bulk"?

This Skill checks. It tells you what is missing, which provision applies, and how to fix it.

If what you need is the doing rather than the checking -- for example:

• generating a publishable AI disclosure statement
  (China measures / EU AI Act Art.50 / California SB 1000)
• writing the statutory fields into a batch of images or videos
• producing a compliance ledger for a whole site

Tell us -- we are evaluating whether to build this, and it does not exist yet:
-> https://wanhetools.top/partners (form, does not depend on email)

We are not committing to build it; this is demand collection only. If you only need the
check, this Skill is enough.

Reference

• Official chaptered text:
  https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB1000
• Open-source verifier (MIT): https://github.com/Wh-bi/sb1000-verifier
• Clause-by-clause breakdown: https://wanhetools.top/sb1000
• Partnership / licensing: https://wanhetools.top/partners