Skip to content
GOCUX
Documentation
GOCUX / Documentationtask api

Choose chat or durable execution

Select the GoCux execution surface instead of importing another service’s processor names.

Select the GoCux execution surface instead of importing another service’s processor names.

Practical procedure

  1. Use normal chat for a direct conversational turn when a durable background record is unnecessary. The Gateway selects the configured route behind the GoCux alias.
  2. Use a work order when work must be tracked as an operation with acceptance criteria, events or attachments. Check optional Cloud Worker availability first.
  3. Use an approved Research plan when the objective is evidence over selected Knowledge sources. Choose Pulse when the same evidence objective must be revisited.

Use a governed work order

A GoCux work order records an outcome, context and acceptance criteria. Use it for durable work that needs the optional Cloud Worker, rather than assuming that every chat turn starts a background job. Select the project and data classification when creating the request. Keep the returned work-order identity so progress, decisions and attachments remain tied to the same operation.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

POST /work-orders — example request body; supply an operation-specific Idempotency-Key

{
  "goal": "Review the supplied project notes",
  "body": "Use only the provided project context.",
  "acceptance": [
    "Identify claims with their supporting source",
    "List unanswered questions separately"
  ],
  "dataClassification": "public",
  "projectId": "project-id",
  "max_wall_seconds": 300,
  "max_tool_calls": 20
}

Inspect the result

A recorded or accepted work order is not proof of completed execution. Read its state, progress and attachments through the task views. Review the output against the acceptance criteria before using it. If a structured result was requested, inspect its validation state separately from the narrative answer.

What to keep explicit

External processor tiers and performance claims do not define GoCux capabilities or billing. Evaluate the actual workflow and its bounded result.

Handle incomplete and refused work

A missing worker or an unavailable dispatch ledger can refuse durable execution while normal chat remains independent. Reuse an operation key only for the same request. After a lost response, reconcile the original operation rather than blindly dispatching new work. A configured maxCost is recorded as context; the work-order schema does not claim it is an enforced monetary ceiling.

Bring this workflow into your workspace.

Set the scope. Review the evidence. Approve the steps that need it.

Open the workspace

Keep exploring