Co-engineer¶

← Home · Co-engineer

The Protos Co-engineer is an AI assistant available across all features. It accelerates work by structuring data, configuring simulations, and surfacing connections that would take hours to find manually — always with traceable sources.

Important: Co-engineer only surfaces information it can trace. It will not speculate or fill in gaps with assumptions. Every claim links back to a source you can inspect.

What Co-engineer Can Do¶

Capability	Example
Schema authoring	Create or update a schema based on your description — e.g. "Create a schema for tablet formulation experiments"
Data document creation	Extract structured data from an uploaded file and create a data document following your schema
Canvas building	Build a simulation canvas — adds blocks, writes the code, and wires everything together
Knowledge surfacing	Find relevant entries from the Knowledge Library as you work
Requirements parsing	Parse an uploaded spec document into structured targets and constraints
Design comparison	Compare design variants against requirements and surface gaps

How to Use It¶

The Co-engineer panel is available from any screen via the chat icon in the bottom-right corner.

Type in plain language:

"Create a schema for tablet formulation experiments with fields for particle size, binder type, and dissolution rate."
"Extract the key parameters from this test report and create a data document."
"Are there any prior experiments on this material in the Knowledge Library?"
"Build a canvas that takes my formulation data and calculates the adjusted capacity."

Co-engineer responses always include source traces — click any claim to see where it came from.

Co-engineer and Your Data¶

Co-engineer can take direct actions in your project — creating schemas, data documents, canvases, and requirements — based on what you ask it. These actions happen through the chat; the Co-engineer will tell you what it created or changed.

You can review all Co-engineer sessions for a project by opening the Co-engineer panel and browsing past sessions.

How Co-engineer Gets Smarter¶

Co-engineer's quality depends on the richness of your workspace:

Model Library: The more models registered and documented, the better Co-engineer's simulation configuration suggestions.
Knowledge Library: The richer the library, the more relevant connections Co-engineer can surface as you design.
Schema quality: Well-defined schemas with units and descriptions give Co-engineer more signal when extracting data from files and creating documents.

Investing in these foundations makes Co-engineer progressively more useful over time.