Attach source references to supported claims without manufacturing provenance.
Practical procedure
- Obtain actual Knowledge hits or approved research findings and inspect the quoted passage associated with each claim.
- Preserve the source, document and chunk references when displaying or exporting a result. Include enough context for a reader to verify the relevant passage.
- Separate unverified synthesis from established source findings. If the evidence disappears, refresh the claim rather than presenting a stale link as continuing support.
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
A generated URL or a polished footnote is not evidence. Build citations from the records returned by the evidence workflow.
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.
Continue with related guides
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.