Academy
5. Deliverables and Follow-ups
Find mission deliverables in Studio, reply to a finished mission to correct or extend it, and understand how follow-up missions inherit context.
When @oupi finishes a mission, every file it produces — documents, spreadsheets, presentations, code — is saved in a Studio folder tied to that mission. You can access these deliverables either from the mission page in the Assistant or directly from Studio. If the mission is a recurring one (a scheduled wake-up), a durable folder collects the output of every run, and you can also have the files emailed to you automatically. Deliverables are never lost or buried in a chat thread; they live in Studio as first-class files you can open, edit, share, or feed into another mission.
Before you use any deliverable, check the verification verdict on the mission page. Every mission ends with an automatic check that compares the result to your original goal and returns one of three outcomes: verified (the result matches the goal), failed (something went wrong), or could not be verified. That last verdict is not a failure — it simply means the checker could not read the output (for example, a binary file or an action in an external tool) and is handing it to you for a human check. Always read the verdict before relying on the result.
If a deliverable needs corrections or extensions, you don't have to start over. From the mission page, reply to @oupi with your feedback — for example, "shorten it to one page," "add the 2025 figures," or "same analysis for Germany." This launches a follow-up mission that inherits the parent mission's goal and outcome as context, so @oupi already knows what it did and what it concluded. The follow-up picks up where the original left off instead of rebuilding from scratch, saving you time and credits.
Keep follow-up instructions short and specific. Because the follow-up mission already has the full context of the parent, you only need to state what should change or be added — no need to re-explain the original goal. A concise correction like "replace the bar chart with a line chart" works better than repeating the entire brief.
For recurring deliverables (weekly reports, daily monitoring), set up a wake-up so @oupi runs the mission on schedule. Each run's output is stored in the same durable Studio folder, giving you a tidy archive. You can pause, arm, or try a single run from the wake-ups panel without recreating the mission.
Open Studio and look for a folder linked to one of your recent missions. Open the deliverable, then navigate to the mission page in the Assistant. Check the verification verdict. If you'd like to adjust the result, type a short follow-up instruction (e.g., "make the summary shorter") and send it to see a follow-up mission launch with inherited context.
Deliverables from every mission live in Studio folders — accessible from the mission page or Studio itself. Scheduled missions accumulate outputs in a durable folder and can email them. Always check the verification verdict (verified / failed / could not be verified) before using a result. To correct or extend a deliverable, reply directly from the mission page: the follow-up mission inherits the original context, so a brief instruction is all you need.