Owning surface
Context Vault plus the mission or task context attachment surfaceStart where the product already explains or controls the problem.
Support
Context not used
Context problems usually come from attachment posture, scope, prioritization, or truncation rather than the concept of context itself being broken.
Guide summary
Use this page to understand the surface before you act inside it.
Recover when source material is visible in the product but does not seem to influence the run.
Guide type
SupportThis guide reflects the current product workflow and surface ownership.
Sections
5Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Escalation rule
Use support with contextAttach the relevant run, mission, task, or artifact whenever possible.
Related action
Contact Support only after inspectionSupport is strongest when the dominant symptom is already known.
Guide section
Symptoms
These signals usually indicate this specific class of problem.
What it is
Recover when source material is visible in the product but does not seem to influence the run.
When to use it
Use this guide when these symptoms match what you see in the product.
Where to find it
Start from the owning surface: Context Vault plus the mission or task context attachment surface.
What happens next
You narrow the problem before you retry or escalate.
Common mistake
Escalating too early without checking whether the owning surface already explains the blocker.
Related action
Open the owning surface first, then return here if the diagnosis is still unclear.
- The output ignores expected source material
- Replay or run detail do not reflect the right context posture
- Too much uploaded material produces generic output anyway
Guide section
Likely causes
- Context was never attached to the mission or task
- Too much context diluted the important material
- The wrong mission or task owns the run
- Bounded selection or truncation reduced the effective context window
Guide section
How to fix it
- Verify the context is attached to the correct mission or task
- Reduce the amount of attached context to the most relevant material
- Rename and structure notes so they are easier to identify
- Rerun after correcting the context posture
Guide section
Where to inspect next
Use the product surface that owns the problem first.
Where to find it
Context Vault plus the mission or task context attachment surface
What happens next
The owning surface should tell you whether the next move is fix, retry, continue, or support.
Related action
Move into Context Vault plus the mission or task context attachment surface now if you have not already done so.
Guide section
When to contact support
Escalate when the attachment is clearly correct and the run still behaves inconsistently.
Tip
Report with the right object
A linked run or artifact is much easier to investigate than a generic support request with no runtime context.