Use EvoX
Start with a clear goal, provide useful context, and review the result.
From a goal to a useful result
EvoX supports chat, cowork, and coding work. The workflow below applies across those modes while the visible controls vary by version and task.
State the goal
Describe the outcome you want in one sentence, including what should be different when the task is complete.
Add relevant context
Provide only the files, references, constraints, examples, and background needed for the task.
Set boundaries
Name what may change, what must remain untouched, and which external effects require approval.
Review the result
Inspect the output, changes, sources, and verification evidence before accepting the work.
Choose the shape of the task
Match the request to the result you expect, then choose chat, cowork, or coding according to the amount of execution and technical detail required.
| Type | Best for | Example |
|---|---|---|
| Answer | Explain or summarize information | Compare two approaches and identify the trade-offs. |
| Draft | Create a document or structured deliverable | Prepare a short decision memo from the supplied notes. |
| Change | Modify files within an explicit boundary | Update one page and run the named checks. |
| Review | Inspect existing work and report findings | Check a document for unsupported claims and inconsistencies. |
Work with useful context
Good context is specific and bounded. Include the goal, source material, constraints, expected format, and acceptance criteria. Avoid sharing secrets or unrelated personal data.
Choose Collaboration in the desktop composer, supply the materials, and define read and write boundaries. Keep the app and computer available during execution. Review the plan, confirm important actions, and open the actual deliverable for acceptance. Follow a practice case when you are ready for a complete task.
EvoX Collaboration
From task input to a reviewable result
Ask for a verifiable result
Research and synthesis
Ask for a concise answer with assumptions, evidence, open questions, and source links.
Documents and plans
Specify the audience, structure, tone, length, and decision the document should support.
Software changes
Name the repository scope, files that may change, required tests, and behaviors that must remain stable.
Review and quality
Request concrete findings with severity, evidence, and a recommended next action.
Write an actionable request
A useful request combines the goal, context, boundaries, and completion signal.
Review the attached materials, identify unsupported claims, and return a concise revision plan. Do not change product definitions. Mark every item that still requires owner confirmation.
Bring the right context
Keep related work together
Use the same project or task context when several steps depend on the same source material.
Attach only relevant files
Provide the smallest set of documents, images, or code needed to understand and verify the request.
Explain unfamiliar terms
Define internal names and decisions that cannot be discovered from the supplied material.
Make the result ready to use
Before accepting a result, check that it answers the requested goal, stays within scope, distinguishes facts from assumptions, and includes the promised verification evidence.
- Goal is satisfied
- No prohibited scope was changed
- Claims have support
- Tests or review evidence are included
- Open questions are visible