Pipecircuit CLI

Create a workspace with a pure core, a semantic program, and a physical CLI:

pipec new my-program
pipec new path/to/project --name my-program

For an unpublished Pipecircuit checkout, point at the framework crate:

pipec new my-program --framework-path /path/to/Pipecircuit/pipecircuit

The generated dependency direction is src -> programs -> core. Both libraries are no_std; all packages inherit the same strict Rust and Clippy rules. A project may grow additional local or shared core/program libraries. The generator refuses an existing destination, validates portable project names, and embeds all templates in its executable. It performs no network requests, Cargo execution, or Git initialization. On an I/O failure, the newly created partial directory is retained for inspection.

Without --framework-path, the template pins Pipecircuit 0.0.17, which must be available from the registry before that generated project can build. A checkout path enables development before publication.

Render a state machine from the current crate:

pipec diagram Inns
pipec diagram Inns --crate path/to/core --target mermaid
pipec diagram Inns --crate path/to/core --target graphviz