Supply Chain Orchestrator Setup

Deploy 4 agents: inventory, routing, procurement, and compliance.

Roles

Setup Procedure

Step 1: Ask the user which role this agent should play and what prefix to use.

Step 2: Install the skills for the chosen role:

# For inventory:
clawhub install pilot-metrics pilot-cron pilot-alert pilot-stream-data
# For routing:
clawhub install pilot-task-router pilot-stream-data pilot-receipt
# For procurement:
clawhub install pilot-webhook-bridge pilot-audit-log pilot-escrow
# For compliance:
clawhub install pilot-audit-log pilot-event-filter pilot-alert

Step 3: Set the hostname and write the manifest to ~/.pilot/setups/supply-chain-orchestrator.json.

Step 4: Tell the user to initiate handshakes with the peers for their role.

Manifest Templates Per Role

inventory

{
  "setup": "supply-chain-orchestrator", "role": "inventory", "role_name": "Inventory Manager",
  "hostname": "\x3Cprefix>-inventory",
  "skills": {
    "pilot-metrics": "Track stock levels, turnover rates, and demand forecasts.",
    "pilot-cron": "Run scheduled inventory audits and demand recalculations.",
    "pilot-alert": "Emit reorder alerts when stock falls below safety thresholds.",
    "pilot-stream-data": "Stream real-time warehouse activity to downstream agents."
  },
  "data_flows": [
    { "direction": "send", "peer": "\x3Cprefix>-procurement", "port": 1002, "topic": "reorder-request", "description": "Reorder requests when stock is low" },
    { "direction": "send", "peer": "\x3Cprefix>-routing", "port": 1002, "topic": "fulfillment-order", "description": "Fulfillment orders for customer deliveries" },
    { "direction": "receive", "peer": "\x3Cprefix>-compliance", "port": 1002, "topic": "compliance-clearance", "description": "Clearance to release held stock" }
  ],
  "handshakes_needed": ["\x3Cprefix>-procurement", "\x3Cprefix>-routing", "\x3Cprefix>-compliance"]
}

routing

{
  "setup": "supply-chain-orchestrator", "role": "routing", "role_name": "Logistics Router",
  "hostname": "\x3Cprefix>-routing",
  "skills": {
    "pilot-task-router": "Assign shipments to carriers based on cost, speed, and capacity.",
    "pilot-stream-data": "Stream shipment tracking updates in real time.",
    "pilot-receipt": "Generate delivery confirmations and proof-of-delivery receipts."
  },
  "data_flows": [
    { "direction": "receive", "peer": "\x3Cprefix>-inventory", "port": 1002, "topic": "fulfillment-order", "description": "Fulfillment orders to route" },
    { "direction": "send", "peer": "\x3Cprefix>-compliance", "port": 1002, "topic": "shipping-manifest", "description": "Shipping manifests for regulatory review" }
  ],
  "handshakes_needed": ["\x3Cprefix>-inventory", "\x3Cprefix>-compliance"]
}

procurement

{
  "setup": "supply-chain-orchestrator", "role": "procurement", "role_name": "Procurement Agent",
  "hostname": "\x3Cprefix>-procurement",
  "skills": {
    "pilot-webhook-bridge": "Interface with supplier APIs for quotes and order placement.",
    "pilot-audit-log": "Log all procurement decisions, bids, and purchase orders.",
    "pilot-escrow": "Hold funds in escrow until delivery confirmation."
  },
  "data_flows": [
    { "direction": "receive", "peer": "\x3Cprefix>-inventory", "port": 1002, "topic": "reorder-request", "description": "Reorder requests from inventory" },
    { "direction": "send", "peer": "\x3Cprefix>-compliance", "port": 1002, "topic": "purchase-order", "description": "Purchase orders for compliance validation" }
  ],
  "handshakes_needed": ["\x3Cprefix>-inventory", "\x3Cprefix>-compliance"]
}

compliance

{
  "setup": "supply-chain-orchestrator", "role": "compliance", "role_name": "Compliance Checker",
  "hostname": "\x3Cprefix>-compliance",
  "skills": {
    "pilot-audit-log": "Maintain immutable audit trail of all compliance decisions.",
    "pilot-event-filter": "Filter and classify events by regulatory category.",
    "pilot-alert": "Flag compliance violations and emit escalation alerts."
  },
  "data_flows": [
    { "direction": "receive", "peer": "\x3Cprefix>-procurement", "port": 1002, "topic": "purchase-order", "description": "Purchase orders to validate" },
    { "direction": "receive", "peer": "\x3Cprefix>-routing", "port": 1002, "topic": "shipping-manifest", "description": "Shipping manifests to check" },
    { "direction": "send", "peer": "\x3Cprefix>-inventory", "port": 1002, "topic": "compliance-clearance", "description": "Clearance to release goods" }
  ],
  "handshakes_needed": ["\x3Cprefix>-procurement", "\x3Cprefix>-routing", "\x3Cprefix>-inventory"]
}

Data Flows

• inventory -> procurement : reorder requests when stock drops below threshold (port 1002)
• inventory -> routing : fulfillment orders for customer deliveries (port 1002)
• procurement -> compliance : purchase orders requiring regulatory validation (port 1002)
• routing -> compliance : shipping manifests for export/import checks (port 1002)
• compliance -> inventory : compliance clearance to release held stock (port 1002)

Workflow Example

# On inventory -- low stock triggers reorder:
pilotctl --json publish \x3Cprefix>-procurement reorder-request '{"sku":"WH-4821","warehouse":"us-east-1","current_qty":12,"reorder_point":50,"suggested_qty":200}'
# On procurement -- place PO after supplier selection:
pilotctl --json publish \x3Cprefix>-compliance purchase-order '{"po_id":"PO-9934","supplier":"GlobalParts Inc","sku":"WH-4821","qty":200,"unit_price":14.50}'
# On inventory -- ship customer order:
pilotctl --json publish \x3Cprefix>-routing fulfillment-order '{"order_id":"ORD-77201","sku":"WH-4821","qty":5,"dest_zip":"94105"}'
# On routing -- submit manifest:
pilotctl --json publish \x3Cprefix>-compliance shipping-manifest '{"manifest_id":"SHP-3301","carrier":"FedEx","items":[{"sku":"WH-4821","qty":5}]}'
# On compliance -- approve:
pilotctl --json publish \x3Cprefix>-inventory compliance-clearance '{"ref_id":"PO-9934","status":"approved"}'

Dependencies

Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.