Company as code.
Design. Validate. Launch.

<serviceTask id="checkStock" name="Check stock" />
<exclusiveGateway id="available" default="reject" />
<sequenceFlow sourceRef="checkStock" targetRef="available" />
<sequenceFlow id="reserve" sourceRef="available" targetRef="reserveStock">
  <conditionExpression>allItemsAvailable</conditionExpression>
</sequenceFlow>
<sequenceFlow id="reject" sourceRef="available" targetRef="rejectOrder" />

The task becomes a handler; the gateway becomes a branch. This is a BPMN fragment, not a complete executable process.

// POST /orders → processOrder → inventory adapter
export async function processOrder(order, inventory) {
  const available = await inventory.check(order.items);
  if (!available.allItemsAvailable) {
    return { orderId: order.id, status: "rejected" };
  }
  await inventory.reserve(order.id, order.items);
  return { orderId: order.id, status: "reserved" };
}
// Template: API · validation · handlers · adapters · tests

The template defines the service structure. Developers connect inventory adapters and add transaction, retry and idempotency handling.

# Dockerfile (compiled service with no external runtime dependencies)
FROM node:22-alpine
WORKDIR /app
COPY dist/ ./dist/
USER node
CMD ["node", "dist/server.js"]

# Kubernetes Deployment specification fragment
spec:
  replicas: 2
  template:
    spec:
      containers:
        - name: order-service
          image: YOUR_REGISTRY/order-service:1.0.0
          ports:
            - containerPort: 8080
          readinessProbe:
            httpGet: { path: /health/ready, port: 8080 }

CI builds and pushes the image. Deployment runs the containers; Service routes traffic. Configure the registry, secrets, resource limits and health endpoints before deploying.