Best use
Bounded evidenceAttach only the source material that improves the current mission or task.
Workflow
Context Vault
Context Vault holds notes and supported source material that can be attached to missions or tasks. It is the product’s source-material layer, not a dumping ground for every document you have.
Guide summary
Use this page to understand the surface before you act inside it.
Attach bounded source material so operators work from relevant references instead of generic memory.
Guide type
WorkflowThis guide reflects the current product workflow and surface ownership.
Sections
8Summary first, then steps, mistakes, and recovery notes.
Related guides
5Written against the current product structure and core execution workflow.
Main limit
Selection is boundedNot every uploaded line can or should be included in a run.
Related action
Verify attachmentVisibility is not the same as being attached to the actual mission or task.
Guide section
What it is
Context Vault stores notes and uploaded source material that can be linked into execution.
When to use it
Use it before runs that need customer notes, competitor material, technical constraints, product details, or curated private references.
Where to find it
Find it under Context Vault and through mission/task context attachments.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Uploading too much context
Related action
Use the “Context not used” troubleshooting guide when the attachment exists but the output still ignores it.
Guide section
Why it matters
It gives operators real references, raises evidence quality, and reduces generic output.
Guide section
How it fits into the workflow
Context sits between setup and execution. It strengthens the mission or task before the run starts.
Guide section
Step-by-step usage
- Add a note or upload supported source material.
- Review the title and make it easy to identify later.
- Attach the context to the right mission or task.
- Launch or continue the run that needs it.
- Verify in run detail or replay that the execution actually referenced the right posture.
Guide section
Inputs and outputs
Inputs needed
Notes or supported uploads
A clear mission or task target
Relevant source material only
Outputs produced
Attachable source material
Safer evidence posture
A clearer input story for operators
Guide section
Common mistakes
- Uploading too much context
- Attaching context to the wrong mission or task
- Expecting context to be copied in full into every run
- Uploading sensitive material that should not be inside the execution system at all
Guide section
Troubleshooting
If context does not seem to influence a run, verify attachment first, then reduce scope so the most relevant material is easier to prioritize.
Guide section
Safe upload behavior and limits
Context selection is bounded. The runtime may truncate, summarize, or selectively reference large material instead of ingesting everything verbatim.
Do not upload provider keys, passwords, bearer tokens, or unrelated private material just because it is available.
What should I not upload?
Secrets, credentials, irrelevant private documents, or anything the run does not actually need.
What if an upload fails?
Check file support, size posture, and whether a simpler note or smaller excerpt would serve the same purpose.