Media Library
Bundles, versions, files, and provenance — the media context agents act on.
Bundles, versions, files, and provenance — the actual shape of media work. The Media Library is Mediafier's media-native persistence layer. It is what gives agents the operational context their decisions need.
The shape of media work
Generic file stores aren't shaped for media work. Real media work needs structure: a bundle (a logical work unit — a title, an episode, a campaign), the versions of that bundle as it moves through ingest, QC, edit, and publish, the files that make up each version, and the provenance lineage that connects them all.
Mediafier's Media Library exposes that shape directly. Agents read and write through governed tools that match the operator's mental model, not through generic CRUD.
What customers can do here today
The library covers the full asset lifecycle through a set of governed tools, grouped by intent:
Ingest
Initiate uploads, complete uploads, list active ingests, ingest from a workflow output.
Bundle lifecycle
Create, update, list, search, archive, restore, soft-delete, and unarchive bundles.
Version lifecycle
Create draft versions, list versions, get version details, publish (immutable promotion).
File management
List files in a version, fetch signed download URLs, retrieve metadata.
Provenance
Attach provenance, fetch provenance, walk lineage chains.
Analysis enqueue
Hand a version to the content-intelligence pipeline for asynchronous enrichment.
MEDIA.md compose
Render the canonical media-as-code description for a published version.
Destructive operations (soft-delete, publish, provenance attach, revoke) carry an explicit approval-worthiness risk signal in discovery so planners and review surfaces flag them as high-impact. Operator-side review consumes that signal today.
MEDIA.md — the README.md for media
Every asset can carry a MEDIA.md — a declarative, atomic, modular, versioned description of the asset itself. Think of it as the README.md of media: structured context an agent (and an operator) can read in seconds and act on.
A MEDIA.md captures the things a media operator actually cares about:
What the asset is — title, type, format, runtime.
How it was made — production timeline, contributors, tools used.
What's in it — summary, scenes, key entities, brand-safety state.
What can be done with it — functions, distribution options, language coverage.
Who has acted on it — edit history, QC gates passed, publication state.
Agents read MEDIA.md and know what to do next.
Provenance Passport
Every file and every version carries a Provenance Passport — the immutable record of where the content came from and what has been done to it. The passport answers questions like:
Was any part of this generated by AI? Which model? What was the prompt?
Was this transcoded? From what source format?
Did a human approve a particular state transition?
Where does this segment ultimately trace back to?
Provenance is append-only. New events are added; existing events are not edited or removed. The data layer enforces it.
Why media-native persistence matters
The platform's broader pitch — turning media tools into agent-ready infrastructure — only works if the data the agents reason against matches the operator's reality: a versioned bundle with a passport and a MEDIA.md, not a flat list of files. That is the ground the Media Library covers.
Where to go next
Looking for what the AI can do with media
Studying decision memory across runs
Building or tuning a domain super-agent
Connecting the library to your harness
Last updated