Why the Pack is the unit of reuse
A generic workflow engine cannot know what “ready,” “approved” or “safe to publish” means in software delivery, incident response, model governance or healthcare coordination. Those semantics belong to the domain.
An Industry Pack installs that domain model without placing industry-specific behavior in the kernel. Teams can replace connectors and handlers while preserving the graph, roles, contracts and governance path.
What a Pack contains
| Part | Purpose |
|---|---|
| Ontology | Typed business objects and the semantic relations allowed between them. |
| Execution graph | Stages, parallel work, loops, approvals, escalation and recovery. |
| Roles and tools | Who owns decisions and which external capabilities nodes may use. |
| Quality policy | Evaluations and blocking gates that define domain readiness. |
| Deliverables | Portable outputs with evidence and integrity metadata. |
| Fixtures and handlers | Executable zero-key examples, success and rejection paths. |
| Context projector | The approved state promoted into durable organizational context. |
Six standard executable Packs
| Industry Pack | Representative governed flow | Connector depth |
|---|---|---|
| Professional Software Delivery | Issue → verification → code and release approvals → deployment → observation or rollback | Real GitHub connector |
| Data and MLOps Asset Release | Partitions → quality and lineage → approval → registry → backfill or recovery | Reference adapter |
| Cybersecurity Incident Response | Signal → evidence → declaration → containment → recovery and lessons | Reference adapter |
| Quantitative Finance Governance | Hypothesis → backtests → risk and compliance gates → execution → reconciliation | Reference adapter |
| Healthcare Diagnostic Coordination | Consent → advisory analysis → specialist decision → report → follow-up | Reference adapter |
| Robotics and Fleet Operations | Task → robot bids → safety approval → dispatch → telemetry → bounded replan | Reference adapter |
Reference adapters execute deterministically without credentials; they model integration boundaries rather than claiming to operate specialist systems. Software Delivery is the depth reference because its connector can read real GitHub work items, commits and pull requests while keeping writes disabled by default.
Create a Pack
The public CLI scaffolds a standalone Pack with an executable graph, real handler, fixture, deliverable and context projector:
npx graph-workbench pack init claims_operations
npx graph-workbench pack test packs/claims_operations/src/index.mjs
npx graph-workbench pack run packs/claims_operations/src/index.mjs --set topic=claim-1042The Pack boundary keeps Graph Workbench general: domain semantics extend through versioned contracts instead of forks or industry-specific kernel branches.