Skip to content
GOCUX
Documentation
GOCUX / Documentationfindall api

Build an evidence-backed collection

Organize a set of entities or records supported by project documents.

Organize a set of entities or records supported by project documents.

Practical procedure

  1. Write the inclusion rule before collecting candidates: what counts as a matching record, which sources can establish it and which fields the result needs.
  2. Import authorized source material and create a Research plan that finds evidence for the inclusion criteria. Keep a reviewed candidate list in your own collection artifact.
  3. Verify each included record against the source passages. Keep missing evidence, duplicates and rejected candidates separate from confirmed entries.

Build an approved evidence path

GoCux Research works with Knowledge sources in the selected project. A plan separates the question and ordered steps from the source allowlist. Creating the plan records a draft; it does not approve or execute the work. Review the actual source selection before approving, because an empty allowlist permits no source and an execution request cannot expand an approved plan.

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 /research-plans — example request body

{
  "projectId": "project-id",
  "title": "Review documented renewal conditions",
  "question": "What renewal conditions are supported by these documents?",
  "steps": [
    "Find the renewal terms and their effective dates"
  ],
  "allowedSourceIds": [
    "source-id"
  ]
}

Inspect the result

Read the saved plan before deciding. After approval and execution, retrieve its findings and inspect the cited source chunks. A finding supported by a quotation is different from a question for which no source was found. Keep that difference in the final report and in any downstream table.

What to keep explicit

This is a GoCux research workflow, not a FindAll API implementation. A search result count is not proof that a collection is exhaustive.

Handle incomplete and refused work

An unapproved plan cannot execute. A 409 can mean the state or expected version changed; reread before deciding again. A 503 means the research store is unavailable, not that research found no evidence. Access is scoped to the authenticated company; knowing an identifier does not grant another company access.

Bring this workflow into your workspace.

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

Open the workspace

Keep exploring