Workflow state
Carry operational context across multi-step freight processes without losing the decision trail.
01
PLATFORM / ARCHITECTURE
The logistics agent layer behind your product.
Sumlabs connects a partner-owned product surface to configured agent workflows, deployment-specific models, and the tools required to do real freight work.
One product surface. Four controlled layers.
The partner owns the customer-facing experience and existing system access. Sumlabs operates the orchestration layer behind it, inside boundaries agreed for each workflow.
The architecture starts narrow: one tenant, one workflow, and only the tools required for that job.
01YOUR BRAND
PARTNER PRODUCT
Branded agent experienceTender received
02ORCHESTRATE
SUMLABS CONTROL PLANE
Tenant rules · workflows · evals03PRIVATE OPTION
MODEL LAYER
Deployment-specific model boundary↗TMS
@EMAIL
)))VOICE
//SMS
▤DOCS
01Partner surface — product, brand, customer, support
02Control plane — state, rules, versions, evaluation
03Model layer — selected and bounded per deployment
04Tools — partner-scoped access to operational systems
05Handoff — explicit operator decision points
An operational runtime, not a chat wrapper.
Models become products when they can keep state, use tools, follow policy, surface exceptions, and leave a usable record of what happened.
Scoped tools
Expose only the reads, writes, channels, and verification calls each workflow requires.
Rules + policies
Apply partner policy, customer-specific constraints, permissions, and escalation paths.
Human handoff
Route exceptions with the context an operator needs to make the next decision.
Audit trail
Retain the sequence of model, policy, tool, and human actions defined for the deployment.
Evaluation
Test workflow behavior against agreed freight tasks before versions move forward.
Tenant boundaries stay visible.
Partner, customer tenant, workflow, user, policy, and tool permissions are treated as separate scopes. The exact isolation, retention, and provider boundary is documented during architecture review.
Partner
Owns the product surface, distribution, and customer relationship.
Customer tenant
Contains customer-specific rules, context, users, and allowed workflows.
Workflow
Defines the job, inputs, tools, policies, handoffs, and expected output.
Execution
Produces a versioned sequence of model, policy, tool, and human events.
05
ARCHITECTURE REVIEW
Map your first workflow
to a real system boundary.
Bring the workflow, current integrations, and deployment constraints. We’ll define the narrowest credible path to a partner-branded pilot.