1. From Mission to Live Artifact: Understanding the Concept

A Live Artifact is a reusable workflow — the recipe of a task @oupi has already completed successfully. Instead of re-explaining the same goal every time ("find job offers matching this profile," "sort the week's invoices," "produce a weekly report from five sources"), you capture the recipe once and re-run it with new inputs. Each run is tracked with its own inputs, cost, deliverables, and verdict. Think of it as turning a one-off mission into a repeatable, parameterized machine that anyone on your team can operate.

A mission is a single goal handed to @oupi — plan, execute, verify, deliver. It lives and dies as one unit of work. A scheduled task in Studio repeats one specific project on a timer. A Live Artifact sits above both: it is a parameterized workflow with declared inputs (files, dates, keywords) that change from run to run. It can be fired on demand, on a schedule, or on an external trigger. Crucially, it can be shared, installed, and derived — something neither a mission nor a Studio scheduled task supports. Schedules and triggers are execution modes available to both scheduled tasks and Live Artifacts, but only a Live Artifact carries the full lifecycle of inputs, sharing, and marketplace distribution.

Inputs are the declared variables that change between runs: a file to process, a date range, a target keyword, a list of URLs. When you forge a Live Artifact, @oupi identifies what varies and builds a typed input form — each field has a type, can be required or optional, and may offer allowed choices. Files come from your file space. This input contract is validated at every run, so the workflow never starts with missing or malformed data. Well-defined inputs are what make a Live Artifact reliably repeatable rather than a vague prompt.

You create a Live Artifact in two ways. First, from a mission or Studio project that went well: ask @oupi to "turn this into a Live Artifact." It confirms, then forges the workflow with its inputs already inferred from what it just did. Second, start fresh on the forge page and describe the workflow in plain language; @oupi asks what varies between runs and builds the input form from scratch. The first path is faster when you already have a proven mission; the second is better when you're designing a workflow from a blank slate.

Use a Live Artifact when a task is worth repeating with different data, when multiple team members need the same workflow, or when you want automation via schedules or triggers. If a task is truly one-off, a mission is enough. If you just need the same project to repeat on a timer without changing inputs or sharing it, a Studio scheduled task suffices. The decision tree: one-off → mission; repeat same project → scheduled task; parameterized, shareable, automatable → Live Artifact.