SDK Quick Start — Manufacturing, Supply Chain & Logistics

Getting started: Manufacturing, Supply Chain & Logistics

Control what your AI can do. The core SDK checks policy before your workflow runs an action and again before its result is released. Denied actions stop. Actions that need human review stay paused until a signed outcome arrives.

Catalog context. Trace a production or logistics workflow from its input through the resulting action. Include equipment or shipment identifiers only where they are needed and authorized. Telemetry is not a machine-safety control. Keep safety interlocks, operational authorization, and applicable product requirements separate from evidence collection.

Use industry fields with the core SDK

Industry vocabularies supply typed values that the SDK sends as policy fields and evidence attributes with one governed call. Choose values that describe the actual workflow. Adding a vocabulary does not activate rules or assign regulatory requirements.

If you need the cross-industry baseline first, open the core SDK reference, Python core, or .NET core before continuing here.

Step 1 — Install the approved packages

In the customer portal, open Tools and SDKs. Select your language and adapters, then follow the installation instructions shown there.

VeriProof SDKs are distributed through customer-gated GitLab packages, not public registries. See SDK access for workstation and CI guidance.

VeriProof packages used here: @veriproof/sdk-core (TypeScript), veriproof-sdk (Python), Veriproof.Sdk.Core (.NET).

Step 2 — Configure

Store the application SDK key as VERIPROOF_API_KEY and create one client when the application starts. Publish the policy you want to enforce, then confirm its field contract against the facts and industry values your application supplies.

Copy the application ID and key from Set up SDK. The application ID is not its display name. Try a live demo  to see a governed workflow, or request an evaluation  if you need a workspace.

Step 3 — Govern the action

Put the protected business action inside govern. The SDK checks policy before it calls the action and before it releases the result. Deny and human-review decisions stop execution here.

import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';

const veriproof = Veriproof.fromEnv();

export async function runProtectedAction<TInput extends JsonValue, TValue>(
  request: TInput,
  action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
  // Catalog values for this vertical. Replace them with facts from the current workflow.
  const industry: IndustryFact[] = [
    { attribute: "manufacturing.job_order.state", policyInput: "manufacturing_job_order_state", value: "waiting" },
    { attribute: "manufacturing.batch.procedural_element_state", policyInput: "manufacturing_batch_procedural_element_state", value: "idle" },
    { attribute: "manufacturing.equipment.use_state", policyInput: "manufacturing_equipment_use_state", value: "production" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "manufacturing.supply.chain.logistics.evaluate",
    request,
    ({ input, signal }) => action(input, signal),
    { industry },
  );
}

Only completed, completed_with_warning, and transformed results carry a released value. Handle every other status with its safe message, reason code, and evidence reference. For review decisions, save the checkpoint and continue through the human review workflow.

Add typed industry values

Each core SDK ships this vertical's vocabulary as generated types. A typed value becomes one policy field and one evidence attribute when you pass it to the governed call. Use application facts for values that are specific to your workflow.

Find this workflow's vocabulary in the Manufacturing, Supply Chain & Logistics reference. Use the attribute names below and verify their policy-field mapping before using them in a rule. Sample values show the format; they are not recommended outcomes for your application.

TypeScript

import { Industry } from '@veriproof/sdk-core';
import { JobOrderState, JobOrderStateMeta, ISA88BatchProceduralElementState, ISA88BatchProceduralElementStateMeta, EquipmentUseState, EquipmentUseStateMeta } from '@veriproof/sdk-core/industries/manufacturing-supply-chain';

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
const industry = [
  Industry.fact(JobOrderStateMeta, JobOrderState.Waiting),
  Industry.fact(ISA88BatchProceduralElementStateMeta, ISA88BatchProceduralElementState.Idle),
  Industry.fact(EquipmentUseStateMeta, EquipmentUseState.Production),
];

const result = await veriproof.govern(actionName, request, runWorkflow, { industry });

Python

from veriproof_sdk.verticals.manufacturing_supply_chain import JobOrderState, ISA88BatchProceduralElementState, EquipmentUseState

# Replace sample values with facts from the current workflow.
# Each value becomes one policy field and one evidence attribute.
industry = (
    JobOrderState.waiting.fact(),
    ISA88BatchProceduralElementState.idle.fact(),
    EquipmentUseState.production.fact(),
)

result = await vp.govern(action_name, request, run_workflow, industry=industry)

.NET

using Veriproof.Sdk.Core.Industries.ManufacturingSupplyChain;

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
var options = new GovernOptions
{
    Industry =
    [
        JobOrderState.Waiting.Fact(),
        ISA88BatchProceduralElementState.Idle.Fact(),
        EquipmentUseState.Production.Fact(),
    ],
};

var result = await veriproof.GovernAsync(actionName, request, RunWorkflowAsync, options);

Workflow examples from the catalog

• Manufacturing Operations Management (ISA-95 MOM): Job Order State. AI production scheduling agent creates job orders and advances state through the lifecycle. 'Aborted' state triggers automatic root cause analysis and material reconciliation workflow. 'Held' state triggers QA agent investigation before resumption is permitted. (Eu Machinery Reg 2023 1230: Job order state transitions driven by AI scheduling agents are in scope of EU Machinery Regulation (2023/1230) Article 9 if the AI system influences safety-critical work centre operations)
• Manufacturing Operations Management (ISA-95 MOM): ISA88 Batch Procedural Element State. Batch AI agent transitions a pharmaceutical batch procedure through ISA-88 states. 'Held' state is used for planned interruptions (e.g. IPC sampling); 'Aborted' state triggers FDA-required batch failure investigation and deviation report generation.
• Manufacturing Operations Management (ISA-95 MOM): Equipment Use State. AI OEE agent tracks equipment use state transitions to calculate availability. Autonomous work order generation triggers when predicted time-to-failure falls below threshold for critical equipment. (Iso 22400: ISO 22400-2, OEE availability calculation uses production, setup, maintenance, and down states)
• Manufacturing Operations Management (ISA-95 MOM): OEEPerformance Factor. AI OEE agent tags each autonomous improvement action with the targeted OEE factor. Vision inspection AI reducing defect rate tags actions as 'quality'. Predictive maintenance agent reducing unplanned downtime tags actions as 'availability'.

Next steps

• Open the full Manufacturing, Supply Chain & Logistics governance reference for all 26 enum categories, policy patterns, and source standards.
• Review TypeScript SDK core for stop handling, human review continuation, and the OpenAI Agents adapter.
• Review Python SDK core for stop handling, human review continuation, and the Microsoft Agent Framework adapter.
• Review .NET SDK core for stop handling, human review continuation, and the Microsoft Agent Framework adapter.
• Browse all vertical references to understand how the core governance vocabulary layers underneath vertical-specific attribute sets.
• Compare this guide with the public industry pages  for a business overview of the same workflows.