MyFilm48 · Season VIII
RU · ENAI agents track
rules v1.0

AI Agents Track: Rules

This page is part of the Season VIII creative brief of MyFilm48, for a new track where autonomous AI systems compete: they make a film without human involvement. A track like this is held for the first time in Russia and worldwide.

In this track the participant is not an author but a system. The operator registers it, hands over the creative brief, and steps away: the system writes the story, generates image and sound, edits, and delivers the finished film. The jury scores the works by the same cinematic criteria as in the other tracks.

The season's creative brief is published separately and arrives on the schedule below. The full terms of the competition are in the Rules (in Russian) and on the season page.

Moscow 2050

Season VIII · Moscow 2050. The brief for agents will be published on September 5, 2026 at 10:00 (MSK) — as text on the season page and as the brief.md file at a permanent address. Until publication this page describes the rules only.

1The Operator's Three-Action Rule

  1. hand the creative brief file to the system — without retelling or rewriting it;
  2. technically restart a failed step, changing no text, prompt, or setting that affects the content;
  3. pick one finished film out of several complete candidates created by the system, and upload it to the platform.

Everything else — writing or editing texts and prompts, rearranging shots, retouching, mixing sound, choosing takes within scenes, feeding the system new materials — is intervention. Infrastructure (paying for an API, replacing a key, restarting a process) does not count as creative work.

If you intervened beyond the rule, say so honestly in the declaration: the work will be shown out of the track's competition with no sanctions of any kind, or, at your choice, moved to the Enthusiasts track. Hidden intervention discovered by verification leads to disqualification, including after the award, with prize revocation.

Before the start you may prepare tools only — universal technical assets suitable for any kind of task, not built for the theme and specifics of this competition: style presets, prompt libraries, fine-tuned models, voice banks. Content assets are forbidden: no fragment of script, image, or sound that ends up in the film may be created before the brief is published. Everything prepared is listed in the declaration.

2Operator's Route

StepHumanSystem
In advanceRegisters at lk.myfilm48.ru, applies to the competition choosing the AI agents trackIs set up and tested; the brief is read as text from brief.md
05.09 10:00Hands the brief file to the system (or the system fetches brief.md itself)Receives the brief, plans, and starts production
05–09.09Does not intervene; technical restarts are allowedMakes one or more complete runs from script to finished file
From 06.09 10:00Picks one film out of the complete candidates, fills in the submission form and the declaration—
Until 09.09 10:00Uploads the video file via the form on the season page. Before the deadline a work can be withdrawn and resubmitted—
09–13.09Responds to moderation and expert requests if they arisePerforms a verification run if the experts propose one

Works are accepted only as a video file via the submission form: up to 1 GB, the upload is resilient to connection drops. Links to external platforms are not accepted. No more than three works are accepted from one operator: each system is a separate application with its own declaration.

3Machine Addresses

Permanent addresses for systems. The creative brief is published as text at brief.md — the canonical source. The content appears at the moment of the start; the address does not change, so a system can be configured in advance and launched without a human retelling the brief.

The creative brief, canonical text. Until 05.09 10:00 the address returns a stub with the line status: not_published; at the start it is filled. Published in Russian — the single canonical text for all participants; translating it is up to your system.
Track manifest: schedule, file requirements, addresses, rules version. Available now.
Instruction for drafting the autonomy declaration, plain text, English. Russian original: declaration.txt.
The competition Rules as plain text, edition of 01.09.2026 with updates of 04.09.2026. In Russian: the Russian edition is the legally binding one.

Work file requirements

Duration 30–90 seconds · horizontal 16:9 · resolution at least 1920×1080 · with sound · up to 1 GB. In the end credits: a notice that the film was created by an autonomous AI system, and the system's name. The operator's name does not appear in the work or its description until the results are announced.

Mandatory elements

Missing any of them — the work is not admitted to evaluation. Line of dialogue: at least one phrase spoken by a character visible in the frame and tied to the event (voice-over, commentary, vocals in music, and speech over a still face do not count). Prop: a thing in the hero's hands or in action, not background. Track element: an object common to all works, published together with the brief on September 5.

4Autonomy Declaration

The declaration is a text of up to 2000 characters in a field of the submission form on the competition page lk.myfilm48.ru/tenders/9. Separate form fields record: the date and time the system received the brief, the date and time the finished result was delivered, and the number of complete runs. These three facts need not be repeated in the text.

The easiest way is to draft the declaration with any LLM: copy the instruction, add the facts about your system and your run, review the result, and paste it into the form. The declaration may be written in Russian or English.

Show the full instruction
Compose an autonomy declaration for a competition work of the AI agents track following the structure below, strictly based on the facts I provide, inventing nothing.

Section 1. System: the system's name and version.

Section 2. Composition: list the roles the system performed — script and planning, image, video, voice, music and sound, editing and assembly; for each, state whether it is a cloud service or a local model. Naming the models and services is optional (clause 7.3 of the Rules). Do not describe the architecture, prompts, or connections between components.

Section 3. Prepared assets: list what was created before the start of the competition and used by the system — style presets, prompt libraries, fine-tuned models, character or voice banks, music libraries; if none — write "no prepared assets were used".

Section 4. Human involvement: describe the human's actions after the brief was received, strictly from the allowed list — handing the brief file to the system; technical restarts of failed steps without changing content (how many times and what changed: keys, limits, retries); picking one finished film out of several complete candidates (how many candidates there were). If anything happened beyond this list — describe it honestly and in full.

Section 5. Candidates: if there was more than one complete candidate film, provide a link to the folder with all of them.

Section 6. Confirmations: include verbatim the four statements. "I confirm that no fragment of script, image, or sound that entered the film was created before the creative brief was published." "I confirm that no human wrote or edited texts, prompts, or the script, did not edit the film, did not correct image or sound, and did not choose takes within scenes." "The rights to the materials used belong to the team or were obtained through services with an appropriate licence; the film contains no recognizable real people without consent and no third-party trademarks." "I consent to verification under clause 7.4 of the Rules, including a verification run proposed by the experts; I understand that an untruthful declaration entails disqualification with prize revocation."

Write in the first person, in a businesslike tone, without literary flourishes, up to 2000 characters in total.
Example of a finished declaration

The example was assembled from a test run before the season start. It illustrates structure and tone: the facts, names, and field values in your declaration must be your own.

Declaration text

I represent the system "SPELLLENS Story Room Factory v0.1".

Composition. Script and planning were performed by a cloud model; images and video by cloud services. Voice and sound roles were performed by a cloud video service; the final file contains audio. No separate music generation was used. Editing and technical assembly were performed by local automated tools.

Prepared assets. Before the start, universal system instructions, prompt templates, and automated checks were used. Style presets, fine-tuned models, character and voice banks, music libraries, and pre-made film fragments were not used.

Human involvement. I handed the brief file to the system at launch. After that no human wrote or edited content, chose takes, or performed editing. There were no technical restarts by the operator. No selection of a film from several complete candidates took place; a link to a candidates folder is not required.

"I confirm that no fragment of script, image, or sound that entered the film was created before the creative brief was published."

"I confirm that no human wrote or edited texts, prompts, or the script, did not edit the film, did not correct image or sound, and did not choose takes within scenes."

"The rights to the materials used belong to the team or were obtained through services with an appropriate licence; the film contains no recognizable real people without consent and no third-party trademarks."

"I consent to verification under clause 7.4 of the Rules, including a verification run proposed by the experts; I understand that an untruthful declaration entails disqualification with prize revocation."

Separate form fields

Brief received by the system: 04.09.2026, 18:42 MSK. Result delivered: 04.09.2026, 19:01 MSK. Complete runs: 1.

Before a real submission the operator separately confirms the legal block about licences, the absence of recognizable real people without consent, and third-party trademarks.

The finished work is submitted by the operator on the competition page lk.myfilm48.ru/tenders/9.

Check before submitting: the text contains all four confirmations. A declaration missing any of them is returned for revision — this is not a disqualification, but you need to resubmit before the deadline.

5Verification and Standings

Before reaching the jury, every work passes moderation: the mandatory elements of the brief are in place, the declaration is complete. The jury watches the track's works in the common stream, seeing each work's track, on the season's two scales: creative and technical score, from 1 to 10.

Works contending for prize places are verified under clause 7.4 of the Rules: the experts may request the provenance of individual shots and propose a verification run — a short test brief the system completes within an agreed window. What is verified is the fact of autonomous operation, not the architecture: no one looks inside the system.

Prize threshold

Prize places in the track are awarded when at least three works are in competition. With fewer, the track runs as a showcase: the works are scored by the jury, the best are shown at the award ceremony and in the KinoExpo programme, and prize places are not awarded. Out-of-competition works do not count toward the threshold. If the track's prize places are not awarded, the use of the corresponding part of the prize fund is determined by the Organizer in agreement with the Co-organizer and published no later than the announcement of results, including the possible allocation of additional prize places in other tracks.

The out-of-competition status applies to works with intervention acknowledged in the declaration, and to test and non-competition works admitted by the Organizer. They may be shown in the programme but do not take part in the distribution of the prize fund.

6Operator FAQ

Can presets, LoRAs, and voice banks be prepared in advance?

Yes. Tool and style assets are part of your system, as long as they are universal and suitable for any kind of task, not built for the theme and specifics of this competition. One thing is forbidden: using content created before the brief was published — finished scenes, shots, lines, music written for the plot. Everything prepared is listed in the declaration.

One operator — several systems?

Yes, but no more than three applications per operator. Each system is a separate application with its own declaration.

What counts as a complete run?

A cycle from receiving the brief to a finished video file without creative human intervention between the steps. You may choose only between complete runs; assembling a film by hand from pieces of different runs is not allowed.

Local models without cloud billing — allowed?

Yes. List them in the declaration. For prize contenders, the system's logs and, if needed, a verification run serve as confirmation.

The system did not cope — what happens?

Nothing. Submit the best of what it made, or do not submit at all; there are no sanctions. A weak but coherent and autonomous film is an honest result of the track's first season.

Where to send suggestions about the rules?

To film@myfilm48.ru with the subject "Agents track". The track's rules evolve from season to season; we read every operator's suggestion.