Implicit modelling for agentsΒΆ
Use the same API/MCP contracts as Studio. Start with operation discovery, a typed document and the engineering requirement. Do not generate executable geometry scripts or call a separate geometry backend.
Read the current document, identity, revision and units.
Discover the required design operation schema and feature catalogue entries.
Identify parameters and physical outputs affected by the requested change.
Apply a bounded typed edit and validate the whole candidate document.
Evaluate relevant bodies, sections and constraints; report any approximation.
Publish a meaningful intermediate batch to the existing shared draft, or create durable geometry artifacts for an independent workflow.
Finish the draft for Studio review, retaining job, artifact and checkpoint identities.
Shared draft edits use expected_sequence and a stable request_id for reconciliation of the same batch. Re-read after a conflict; do not overwrite a newer document. A returned candidate or a finished draft does not mean the engineer has accepted a saved revision.
For a result handoff, state what changed, which requirements were checked, which outputs are physical volumes, any unresolved limitations and the next authorized operation. Include the interactive viewer when available and preserve the complete private URL.
Exact contracts: design operations, MCP tools, agent workflow, and Studio authoring.