Core concepts

#Research conversations and calculation workflows

A research conversation starts with a question. Retrieve materials, analyze a file, discuss results and add context through follow-up messages. Each message starts a round of processing that may return text, database records, charts or files.

A calculation workflow puts steps on a canvas. Nodes accept inputs, process structures, run calculations or produce outputs. Connections define how steps fit together. Use workflows when you need to inspect parameters and repeat a sequence.

A calculation suggested in an answer has not necessarily been executed. Check the processing details or run history for evidence of execution.

The calculation assistant works inside the workflow canvas. It can read, build, modify and run the current graph through conversation. Use the calculation assistant to change that canvas, and Research to start from questions and sources.

#Skills and templates

A skill does not install calculation software or grant tool permissions. A template still needs valid inputs, suitable parameters and executable nodes. See the Skill Center and Template Center guides.

#Attachments and knowledge bases

An attachment is submitted with a message. Use it to analyze a document, table or structure file you are working with.

A knowledge base stores and organizes multiple documents. Uploaded files must finish parsing and indexing. Select a knowledge base in the conversation to include it in that message's retrieval scope. Source text, extracted parameters and model explanations are different kinds of information; keep their sources when using results.

#Drafts, runs and releases

A draft is the workflow currently configured on the canvas. After editing, check that the page reports it as saved.

A run is one execution, with its own inputs, node states, logs and outputs. Editing a draft does not rewrite an earlier run.

A release preserves a workflow version for review or restoration. Creating a release and adding a template are separate actions. Clicking Publish alone does not establish that a workflow is publicly listed in the marketplace.

#Research groups and projects

A research group organizes members and owns projects. Create or join a group before creating a project.

A project records a research goal, direction, planned dates, status and members. Project membership is managed separately from group membership: accepting a project invitation does not also join its research group.

The project timeline shows planned dates, and the budget is a configured limit. Neither is an automatic measure of completed work or actual spending.