Accurate product language
GOCUX Gateway is the model-routing boundary. GoCux CLI is the local agent surface. Research, Pulse, knowledge and artifacts are distinct workspace journeys whose availability should be checked in the product.
Statements that need current evidence
Funding, customer relationships, performance records and partnerships require their own current evidence. None is established by the third-party reference library. Contact support for a specific product question.
A practical starting point
Research with traceable evidence. These steps describe the GoCux workflow and its permission boundaries.
- Define a research question, the project it belongs to, and the sources that may support the answer. Separate a factual question from the action you might take after reading the result.
- Review the proposed research plan before approving execution. Keep the approved scope stable; a different question deserves a revised plan rather than silent expansion.
- Read each finding alongside its citation and source excerpt. Treat missing evidence as an unresolved question, and keep the final report distinct from any subsequent external action.
What to verify
A useful report connects its conclusions to sources and makes unresolved questions visible. A fluent paragraph alone does not establish that a research task succeeded.
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.