Academy
2. Forging a Live Artifact from a Successful Mission
Turn a completed mission into a reusable workflow by asking @oupi to forge it, confirming the recipe, and naming what varies between runs.
A Live Artifact is a reusable, parameterized workflow forged from work @oupi has already completed successfully. Instead of re-explaining the same task each time, you capture the recipe — the sequence of steps, tools, and logic — and declare what changes between runs (a file, a date, a keyword). Every future run validates those inputs, executes the workflow, tracks cost and deliverables, and stores everything in your history. Think of it as promoting a one-off mission into a repeatable, shareable capability.
The forge-from-mission path starts on the mission page of a completed task. When a mission's verification verdict is satisfactory, reply to @oupi with something like "turn this into a Live Artifact." @oupi confirms, then analyzes the mission's plan to extract the workflow structure. It proposes a recipe — the fixed logic — and asks you to identify what varies between runs. These become the declared inputs: typed, required or optional, with allowed choices where relevant. Files can be pulled from your file space. Once confirmed, the artifact appears in your Live Artifacts list, ready to run.
Naming what varies is the most critical design decision. Inputs are the contract between the artifact and its future users (including your teammates). Each input has a type (text, file, date, list of choices), a required/optional flag, and validation rules enforced at every run. Well-chosen inputs make the artifact flexible without making it fragile. For example, a weekly-report artifact might declare a date range (required), a list of data sources (required, multi-choice), and an optional executive-summary toggle. Over-parameterizing leads to confusion; under-parameterizing forces users to fork the artifact.
Before forging, review the mission's verification verdict. A "verified" mission gives @oupi the clearest signal of what success looks like. If the verdict was "could not be verified," make sure you validated the output yourself first — the artifact will replicate that same workflow, so the recipe must be sound.
Write your mission goal with the artifact in mind: state the outcome, its format, and constraints clearly. @oupi plans better from a clear destination, and that clarity carries over into the forged recipe. A well-briefed mission becomes a well-structured artifact with minimal editing.
After forging, do a test run immediately with fresh inputs. Check that the deliverables land in the artifact's folder, review the cost, and confirm the verdict. This first run is your quality gate before sharing the artifact with your team or attaching a schedule or trigger.
Open a recently completed mission in your Assistant whose result you were happy with. Reply to @oupi: "Turn this into a Live Artifact." Confirm the recipe it proposes, name at least two inputs that vary between runs, then run the new artifact once from the forge page with fresh values.
To forge a Live Artifact from a mission: (1) complete a mission with a good result and a clear verdict, (2) ask @oupi to turn it into a Live Artifact, (3) confirm the proposed recipe, (4) declare the inputs — what changes between runs — with proper types and constraints, (5) test-run with fresh inputs. The result is a parameterized, trackable workflow you can re-run on demand, schedule, trigger, or share with your team — each member getting their own instance and history.