BitShovel.One real problem at a time
Open the current workflowCurrent Workflow中文

One real problem at a time

中文

HISTORICAL DIG · JUL—AUG 2026

What must be clear before an AI short drama starts production?

One short drama can touch asset rights, territory, account identity, channel entry, disclosure, contracting, and payment at once. These are not one copyright-approved stamp: an answer in one column cannot close another.

First recorded · Last public revision · Revision 4
Work and asset rightsRegion and channelPublisher and contracting partyPayee and collaborator splitFiling and AI disclosure

AI SHORT-DRAMA MOTHER WORKFLOW · NODE 01

Relation to the current subject

Decide who may make it, who is responsible, and where it goes before script and shots.

The mother Workflow puts rights and business route first because every later script, casting, voice, generation, and edit decision increases the cost of returning. This node does not seek one all-clear badge. It asks whether another person can reopen the territory, channel, responsible parties, asset basis, and disclosure route for one candidate version. Only then does the next node have a reason to build a script and static shot package.

Record state at the time

  • AI short drama
  • Rights and business route
  • Deep record
  • Developing
  • Historical E2 · six official sources rechecked · no title-specific contract or platform determination

REVISION 4 JUDGMENT

Judgment at the time

Do not ask does it have copyright? Ask who carries this version through this territory and route—and on what record.

Open full rationale and return rules
Freeze one specific planned release route instead of asking whether the project has copyright in the abstract. Use one route card to name the exact version, territory and channel, publisher, contracting party, payee, collaborator split, the basis for story, likeness, voice, image, music, font, and model use, and the disclosures or filings that may apply to that route. Each field is confirmed, unknown, or conflict, with an openable source, owner, and checked date. Any required unknown or party conflict closes batch production. Technical provenance, account verification, and platform review do not substitute for rights.
Who it was for
People preparing a first commercial sample, accepting a commission, adapting an existing story, or sharing production and release responsibilities
Why it mattered then
Open note

The costliest rework may not be a bad shot. It may be discovering after the cut is finished that story, likeness, voice, or music provenance is unclear; the uploader cannot represent the contracting party; payment and collaborator terms conflict; or the chosen route needs different material.

Where the judgment stops
Open note

This is an unrun, unfrozen production preflight—not legal advice, platform preclearance, or a contract template. Chinese release, EU transparency, and U.S. copyrightability are different contexts. The Bilibili material describes one dated submission, qualification, and settlement route. BitShovel has no corresponding story, performer, voice, asset, contract, account, filing, submission, review, or income result and makes no finding that any title may be released.

BEFORE OPENING THE CARD

Fit check

First accept that pause is a valid deliverable at this node.

This record may help

  • You have one concrete candidate: one version, territory, channel, and a set of openable asset sources.
  • You will leave unknowns unknown and let the route card say pause before production instead of forcing a pass.

Do not use it yet when

  • A core story, likeness, voice, music, image, font, or training reference still has unknown provenance.
  • No territory or channel is chosen, but you want one universal release checklist.
  • You need BitShovel to confirm a contract, ownership, filing eligibility, platform acceptance, or revenue—this record has none of that evidence.

HISTORICAL TRIAL · UNRUN, UNFROZEN 60-MINUTE ROUTE CARD

Historical trial

Check one planned route only; do not generate, submit, or sign.

Time needed
A sixty-minute ceiling for one planned route; waits for permission, platform replies, or professional advice are separate, and this round remains unrun
Likely cost
Do not generate, submit, or sign yet; price formal permission, filing, or professional advice separately if needed
Permission boundary
Keep contracts, permissions, and channel pages read-only; do not sign, upload, assert rights, or submit identity documents for anyone
  1. 01

    First step

    Open this step

    Assign one candidate sample an ID and file hash. Fill four columns: work and assets; territory and channel; publisher, contracting party, and payee; filing and disclosure. Mark each item confirmed, unknown, or conflict, with source, owner, checked date, and expiry. Never convert a blank into none automatically.

  2. 02

    What should exist

    Open this step

    A route card saved with the candidate package and one explicit decision: enter the next node, wait for evidence, or close this route.

  3. 03

    How to tell it worked

    Open this step

    Someone outside production can open each record, state which version goes where, who publishes, contracts, and receives payment, which rights and disclosures remain open, and why the route continues or stops. This means only that the route is inspectable—not that release is authorized.

  4. 04

    Stop when

    Open this step

    Stop when a core asset right is unknown; publisher, contracting party, or payee conflicts; collaborator terms lack a written basis; territory or channel is unclear; or a required filing, label, or declaration has no owner.

  5. 05

    How to back out

    Open this step

    Keep the gap and decision record, remove unknown assets, return to an original or traceable version, and choose a named-owner, non-exclusive, stoppable test route. Do not upload, sign, or accept commercial delivery.

BITSHOVEL R4 ROUTE CARD · FIXED FICTIONAL RECORD

Method and interfaces

Two honest unknowns are worth more than a false all-clear badge.

Open method boundary

The explainer only shows how to keep different questions in separate columns and deliberately leaves voice permission and payee unknown. It contains no real work, party, platform, contract, or legal determination.

Name one route before productionBITSHOVEL R4 EXPLAINER · FIXED FICTIONAL RECORD
A fixed fictional release-route card separating candidate version, channel, publisher and payee, seven asset-rights fields, filing, and AI disclosure, with two unknowns keeping the route paused

DEMO CUT 07, the demonstration parties, and every status are fixed fictional data. Two items remain unknown, so the decision is pause. This is not a contract, rights clearance, filing, review, channel eligibility, or income result.

About this image and its source

BitShovel explainer created August 17, 2026. It contains no real work, person, voice, asset, contract, account, identity, filing, submission, review, settlement, or income data.

Open source page ↗

SOURCES AND EVIDENCE

Sources and evidence

As of August 17, 2026, six official sources separate release, labeling, enforcement, channel identity, EU transparency, and U.S. copyrightability. They do not decide a specific title.

Open evidence boundary

Historical E2 remains the old page label. Revision 4 rechecks Chinese broadcasting, labeling, copyright, and platform sources plus the EU legal text and U.S. Copyright Office report. They separate the questions; they do not clear rights, filing, contracts, review, or income for a specific title.

  1. 01
    Current Chinese broadcasting notice · Rechecked

    Tiered microdrama review, release numbers, and platform responsibility

    Open source boundary

    The NRTA notice describes tiered review, licenses or filing numbers, and title-card identification for relevant releases in China. It does not decide a specific title, entity, or channel and does not govern overseas distribution.

    Open official source ↗
  2. 02
    Effective Chinese labeling measures · Rechecked

    Visible labels, file metadata, and publisher declaration

    Open source boundary

    The four-agency measures took effect September 1, 2025 and separate visible labels, embedded metadata, and user declaration. They do not replace copyright, human consent, content review, or filing.

    Open official source ↗
  3. 03
    Chinese copyright enforcement guidance · Rechecked

    Notice-and-takedown guidance for microdrama

    Open source boundary

    The industry guide carried by the National Copyright Administration describes complaint routes, material, and handling. It is enforcement guidance—not automatic ownership proof or pre-production permission.

    Open official source ↗
  4. 04
    First-party channel guide · Rechecked

    Bilibili separates individual and institutional qualification, submission, monetization, and settlement routes

    Open source boundary

    The dated official guide supports naming account type, release route, and settlement entry. It describes one channel route and does not prove eligibility, acceptance, contracting, or income.

    Open official source ↗
  5. 05
    Current EU legal text · Rechecked

    EU AI Act Article 50 transparency obligations

    Open source boundary

    The Regulation generally applies from August 2, 2026. Article 50 addresses machine-readable marking and disclosure for certain deepfake, artistic, or fictional content. Roles, exceptions, and implementation still depend on the work and distribution context.

    Open official source ↗
  6. 06
    U.S. Copyright Office report · Rechecked

    AI-assisted works still require a case-specific account of human authorship

    Open source boundary

    The official report explains that U.S. copyrightability depends on the specific work and human contribution. It is not a registration, ownership, infringement, or commercial-delivery finding for this project.

    Open official source ↗

REVISION RECORD

Revision record

Revision 4 stops narrative imagery, a provenance diagram, or a timed program from standing in for one concrete route.

Open 4 revisions
  1. Revision 1

    Put rights proof, filing, AI labels, and delivery ownership into one pre-production checklist.

  2. Revision 2

    Added voice permission and Chinese release material while separating EU and U.S. questions.

  3. Revision 3

    Added a channel-route card naming account type, publisher, contracting party, payee, and collaborator split before batch production.

  4. Revision 4

    Split one broad checklist into a four-column, three-state record for a specific route; removed narrative imagery, the C2PA figure, and time-limited program thresholds; retained current official sources and a first-party fixed fictional explainer.

    What the record said before
    Put rights, filing, AI labels, accounts, contracting, and payment into one checklist; do not batch without required proof.
    What changed
    Freeze one version, territory, and channel. Keep work and assets, route, responsible parties, and filing or disclosure in confirmed, unknown, or conflict states with source, owner, and date. Any required unknown or party conflict pauses the route.

WHAT THIS RECORD LEAVES

What this record leaves

Sometimes the cheapest result is closing an undeliverable route before generating frame one.

Even a complete card only allows the script and static-shot node to begin. It does not mean the title has been cleared, filed, reviewed, contracted, or made profitable. If a required unknown remains, keep the gap, change the asset or route, and do not let later production hide it.

Back to the Dig index