The abstract, organised by the seven fields
The readable form of film/script.py:498-501. This is the document that did not
exist: the seven fields as text, each carrying the one sentence that says what
the project does in that field.
Grounded in ep067-…-renaud-meeting/draft.md (Film & Media as Knowledge
Practice: Agent-Supported Production, reconciled 2026-08-13 against the Notion
page of record) and in Episode 300's master chart chart_1785178283091.
Film & Media as Knowledge Practice — Agent-Supported Production
The result expected. An experimental documentary short whose edit emerges from an agent-supported process, plus a documented, reusable Relational Production Protocol — a four-movement ceremony shape: pre-production intent-setting, on-set observational logging, post-production narrative-cluster processing, closure ceremony. The film is not scored afterward; its narrative carries its own music, story and song made by one process.
The seven fields it spans:
1. Indigenous methodologies
The production is structured as ceremony rather than extraction, drawing on Shawn Wilson's Research is Ceremony — knowledge emerging through witnessed relationship, with relational accountability preserved as a system constraint rather than an ethical afterword.
2. Relational ethics
Consent and provenance are recorded at every ingest; the record of who contributed what travels with the artefact. A process that only took has failed regardless of output quality — the criterion is falsifiable and is written into the chart as an element of performance.
3. Systems & cybernetics
A Perceptual Agent Layer captures creative intent as structured event streams; a Narrative Cluster Processor transforms raw material into thematic structure; quality-enforcement loops hold storyteller coherence. The film is the output of a feedback system that observes its own making.
4. Software architecture
The pipeline is real software — observe → classify → project, implemented and published, with a manifest format that co-locates audio, transcription, key, BPM, sections and MIDI as one addressable artefact rather than a folder of files.
5. Human-computer interaction
The filmmaker authors; the composer observes and decomposes without overwriting. That asymmetry is enforced architecturally, so collaboration proceeds by structured response rather than simultaneous editing — a low-bandwidth, asynchronous interface for two people on two devices.
6. Film & media studies
Cinema here generates knowledge through juxtaposition, rhythm and relational witnessing rather than recording a pre-existing reality. The claim under test is that the toolset is the transformation, not a faster route to the same film.
7. Music & sound studies
The score is derived from the narrative material itself. If the song could have been written without the story, the central claim has not been tested — which is the project's own stated falsification condition.
What a viewer meets: an animated piece in which what was shadow has become form they can hear, and a viewer who knows none of the above can hear the transformation without being told it happened.
Note on one number, deliberately absent
Earlier statements of this outcome said "a 90-second animated piece." That
figure is retracted at episode.yaml:106-110 of the Episode 300 vessel: what
exists is a 75-second interactive HTML (built on gaia, Claude Design, not a
video) and a 96.3-second rendered film (At the Fire: The Platform Learns to
Dance, Manim CE 0.20.1 on eury), and HANDOFF-260728.md says do not merge them.
The chart's desired outcome still carries the retracted number. Changing a master's desired outcome is William's language, not the seat's — so no duration is claimed above. Nothing sent outward should carry that figure until he restates it.