# broCAD/M guides

Start work directly from the project library. An empty library and empty toolpath preview display a CAD-to-machined-part illustration alongside guidance; there is no first-run popup to dismiss. Choose **Design in CAD**, **Import DXF** or **Open machine program** to begin. Skeleton shapes indicate loading without blocking those controls. Storage failures keep their own diagnostics, and an empty search result keeps its filter controls.

Use [CAD design](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/cad/index.md) to build parametric sketches and solid parts in the desktop workspace, then send an exact sketch directly to CAM. CAD uses the same local browser cache or optional workbench folder.

Use the [saved-process simulation guide](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/simulation/index.md) to inspect a saved UPID job with rough stock, released pieces and optional STEP machine geometry. [Agent tools](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/agents/index.md) describe precise edits, exports and preview capture in a compatible browser.

broCAD/M turns a saved UPID project into a controller-neutral execution plan. A post translates that plan into an exact controller program. The user installs one **complete `.wireedm-package`** containing the machine, post, setup, evidence and tests.

Start with the [authoring workflow](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/authoring/index.md) and open the [Package workbench](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/tools/index.md) to check and build files in your browser. Use the [contract reference](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/reference/index.md) while implementing. For an existing package, start with [compatibility and repairs](https://insignifi4nt.github.io/wireedm-gcode-parser/documentation/compatibility/index.md).

## What belongs where

| Surface | Owns |
| --- | --- |
| UPID and application | Geometry, contour order, machining intent, material-side decisions, entry/exit geometry, positioning and explicit stop/thread/separation events |
| Postprocessor | Controller commands, modal state, supported capabilities, command formatting, wrappers, numbering, extension, encoding and line endings |
| Physical machine and setup | Exact machine/controller identity, evidenced limits, hardware, post ID/version/hash and complete property values |

A post must not silently repair geometry, choose a contour order, insert unplanned machining strategies or assume another controller's G-code semantics.

## Give an agent this task

> Read this documentation and its current compatibility record. Help me build a complete Wire EDM machine package for my exact machine. First identify missing machine/controller information and evidence. Implement only supported behavior, validate the entire package, explain remaining limitations, and deliver the `.wireedm-package` with its source folder and test report.

The app works locally in browser cache or an optional workbench folder. Loading this documentation grants no access to those files. The user supplies the package, project and controller evidence needed for the task.