One platform, distinct responsibilities
Normal web conversation and the customer CLI use GOCUX Gateway. The CLI owns its local tools and permissions. Optional server-side automation supports durable or specialized work without becoming a dependency of ordinary conversation.
Context that stays attached to work
Projects organize knowledge, research and outputs. Memory has explicit scopes, while approvals and evidence help people understand what a task can do and what it actually did.
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.
Bu iş akışını çalışma alanınıza taşıyın.
Kapsamı belirleyin. Kanıtları inceleyin. Gereken adımları onaylayın.