bpmn-package-explorer

BPMN Package Explorer

Generate and view BPMN 2.0 process packages: a process plus the decisions its rule tasks evaluate, the forms its user tasks present, and a manifest binding them — kept as plain, vendor-neutral BPMN 2.0. Buildless and offline: it vendors pre-built viewers and a self-contained Node layout bundle; generating or rendering a package needs no npm install, no bundler and no network. Requires Node ≥ 20.12 and a browser.

When to use

Model a business process from a prose description; make/view a BPMN diagram or a DMN decision table; build a cross-linked process package. Hungarian triggers: „csinálj egy folyamatábrát”, „rajzold meg a folyamatot”, „döntési tábla”, „nézd meg ezt a .bpmn fájlt”.

The two guarantees

• Never a corrupt diagram. A language model can author correct BPMN semantics but not a readable coordinate set. bpmn-auto-layout fills that gap but fails silently on sub-processes, pools and lanes (all outputs stay schema-valid). A layout guard verifies every laid-out diagram against its own semantics and aborts on any corruption, in strict mode.
• Vendor-neutral. The .bpmn/.dmn/.form files carry no engine extension. A sidecar package.yaml holds the link graph (bindings, roles), so a package opens in Camunda Modeler, Signavio or any conformant tool.

Generation workflow

The agent authors the artifacts (guided by the references); the pipeline runs the mechanical steps, each failing loudly:

1. Author semantics — one or more semantics-only .bpmn (no geometry), applying the authoring envelope and identifier rules. Emit <bpmn:incoming>/<bpmn:outgoing> on every connected flow node.
2. Author artifacts — the .dmn decisions and .form schemas.
3. Write package.yaml — the bindings and roles.
4. Validate the manifest — node scripts/generate-cli.mjs <packageDir> runs the envelope check, manifest validation, layout + guard, and assembles a render root; it stops before serving on any error.
5. Serve + canvas — serve the printed render-root path with node scripts/serve.mjs <renderRoot> [port] (CORS-enabled) and open the printed URL on the canvas (never file://). Do not use serve_mockup for canvas display: it omits Access-Control-Allow-Origin, so the viewer's fetch('package-data.json') fails in the opaque-origin sandbox (“Failed to fetch” → blank diagram).