media-producer
Media Producer
Use Renku as the project metadata and attachment boundary. Treat prompts and media as opaque creative artifacts: inspect them in the agent/user loop, but never turn creative judgment into Studio runtime validation.
Read workflowPolicy from Generation Context before choosing any unselected
execution path or deciding automatic Preview, conversational confirmation, or
batch concurrency. Apply precedence in this order: explicit user direction for
the current request, an execution path already authored on the saved
GenerationSpec, Project workflowPolicy, then ask. Never recreate a
purpose-specific or skill-local default. If policy prefers Codex but the current
harness lacks capability codex.gpt-image-2, ask for a path instead of silently
falling back to a paid Renku run.
Core workflow
- Resolve the exact current project, purpose, and target. Never invent ids.
- Read the Core-owned context: