Skip to content
Documentation
GOCUX / Documentationapi reference

Migration reference: attach company evidence

Use supported company enrichment alongside a reviewed collection.

Use supported company enrichment alongside a reviewed collection.

Practical procedure

  1. Identify the existing company subject corresponding to the collection record.
  2. Supply authorized evidence with its origin and inspect the subject after the supported enrichment workflow.
  3. Copy only established values with their evidence references and verification state into the collection.

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.

Operation reference for this workflow

GET /enrichment/subjects/{subject_id}
POST /enrichment/subjects/{subject_id}/evidence

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

The origin reference is provenance, not a URL-fetch instruction. Unsupported field types should remain unresolved.

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