Mission DNA
Private by defaultUser-owned reusable patterns do not become global learning automatically.
Reuse
Mission DNA and Blueprints
Mission DNA and Blueprints help you reuse good execution patterns without copying private source material or flattening different work types into one generic template.
Guide summary
Use this page to understand the surface before you act inside it.
Understand Official Blueprints, private Mission DNA, Blueprint Packs, and how reusable execution patterns fit into Mission Builder.
Guide type
ReuseThis guide reflects the current product workflow and surface ownership.
Sections
8Summary first, then steps, mistakes, and recovery notes.
Related guides
4Written against the current product structure and core execution workflow.
Official Blueprints
Curated by opheli.aiNormal users can use them but do not publish them.
Related action
Start from a BlueprintUse a pattern when the work is repeatable or the setup is complex.
Guide section
What it is
Mission DNA and Blueprints capture reusable execution patterns.
When to use it
Use them when the same execution pattern appears repeatedly or when you want a stronger starting point than a blank builder.
Where to find it
Find them in the Blueprint Library, Launch Mission, and related Mission DNA surfaces.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Assuming Blueprints replace review
Related action
Open Blueprint Packs or Launch Mission when you want the quickest guided start.
Guide section
Why it matters
They reduce setup time, improve consistency, and carry context requirements, operator roles, and quality rules into new work.
Guide section
How it fits into the workflow
Blueprints sit upstream of mission creation. They influence setup before runs happen.
Guide section
Step-by-step usage
- Choose an Official Blueprint or a private reusable pattern.
- Review context requirements and operator roles.
- Prefill Mission Builder with the pattern.
- Adjust the objective and inputs for the specific mission.
- Launch only after the prefilled plan still makes sense for the current work.
Guide section
Inputs and outputs
Inputs needed
A repeatable work pattern
Optional prior successful run for DNA extraction
Context requirements
Operator and quality rules
Outputs produced
Reusable builder setup
Safer mission framing
Reduced setup time
Guide section
Common mistakes
- Assuming Blueprints replace review
- Expecting private DNA to become shared by default
- Copying full private uploads into reusable patterns
Guide section
Troubleshooting
If a Blueprint feels off, treat it as a starting point and edit the plan before launch instead of forcing a bad fit.
Guide section
Official vs private
Official Blueprints
Curated by opheli.ai for broader product use.
My private Blueprints
User-owned reusable patterns or Mission DNA extracted from the user’s own work.
Why users cannot publish official Blueprints
Official publication is curated product content, not an open marketplace inside the normal user workflow.