Agentic board design
Updated v2.5.7At a glance
- The production Agentic MCP uses the same eCAD model, checks and transactions as the native workspace
- Live discovery exposes the current workflow and exact schema for every available eCAD operation
- Revision, idempotency and source-digest fences prevent stale work from changing the board
- Routing, fill, DRC, STEP and fabrication run as bounded cancellable jobs
- Exact-key recovery returns a committed result without duplicating copper or revisions
- Settled workspace views and screenshots report the requested current board
- Engineering review remains a human action and exact artifact hashes travel in Project Memory
The built-in Agentic MCP can carry an eCAD project from requirements or a supported import through part selection, schematic organization, PCB layout, native routing, checks, mechanical review and exact fabrication delivery.
Discover the live interface
After binding the intended open project, the client reads ecad.guide.get. It can search the available operation registry with ecad.operation.list and retrieve one operation's exact input schema, units, defaults, effects and limitations with ecad.operation.get.
The operation registry is the same one that validates production requests. A client should discover it at runtime instead of copying a fixed list from documentation.
Safe mutations and jobs
Every document mutation carries the current numeric revision and a unique idempotency key. Imports, arrangements, placement, routing, fill, DRC, STEP and fabrication candidates are tied to one exact document generation, revision and source digest. An edit or project replacement makes stale work unusable.
Long operations are bounded jobs with progress and cancellation. Cancellation observed before a commit leaves the document unchanged; cancellation or a lost response after commit preserves one recoverable result. Repeating the same idempotency key returns that result without another revision or duplicate copper, while a changed payload conflicts instead of being guessed. Results stay private to the bound document and return paged metadata rather than dumping whole board or binary artifact data.
Workspace changes, fits and screenshots settle against the requested document generation and view. They do not mutate geometry or require a manual redraw before review evidence is captured.
Review and handoff
Automation can prepare candidates and request review. It cannot approve its own engineering gate. The final Project Memory handoff records requirements, sourcing and physical pin evidence, rule and profile choices, routing/DRC coverage, model omissions, exact fabrication hashes, approvals and remaining limitations. The saved .jc3 keeps the project library and model bytes for offline reopen.