Neutral Core
The shipment stays independent from any participant’s private TMS, ERP, mailbox, or commercial record.
THE INFRASTRUCTURE
Five connected foundations for freight.
Identity establishes who entered. TTID and IDAS establish durable identity and assurance. Nexus governs trust and authority. Shipment Core provides shared context. Automation coordinates authorized action.
01
One persistent identity and authority model
02
One neutral shipment Core with private Layers
03
One attributable state change across connected systems
THE OPERATING LAWS
Shared freight context without surrendered control.
TruckerTech coordinates the relationship between people, organizations, shipments, systems, and services. It does not turn participation into blanket access or replace the systems that remain authoritative for specialized work.
Participant sovereignty
Every organization keeps its systems, Customer Data, policies, commercial terms, and authoritative relationships.
Permission before visibility
Connection, common ownership, or possession of an identifier never creates unrestricted access.
One connected state
Operations, Career, Exchange, Communications, and Driver experiences use governed projections of the same subjects.
FIVE PLATFORM FOUNDATIONS
Five foundations. One connected freight platform.
The three operating outcomes stay simple because five distinct foundations carry identity, verification, governance, shipment context, and execution underneath the experience.
01ACTIVE FOUNDATION
TruckerTech Identity
Authentication, represented organization, memberships, roles, relationships, and ecosystem access resolve into one durable operating identity.
- Person and organization accounts
- Role Organization membership and authority
- Relationship-aware access
- Continue with TruckerTech federation context
ACCOUNT CONTEXTPerson · Organization · Role
✓THE CORE–LAYER–NEXUS MODEL
One Core. Participant Layers. Governed by the Nexus.
The Core preserves the shared shipment. Layers preserve participant sovereignty. The Nexus resolves the authorized relationship between them without replacing any participant’s system of record.
SHIPMENT CORE TT-2026-04189Dallas, TX → Atlanta, GA
NEUTRAL · LIVENeutral Core establishedThe Core is the shipment—not a participant’s private record.
Shared operational context is durable and attributable while customer relationships, commercial positions, and internal systems remain participant-controlled.
Shipper LayerDemand, product, references, origin requirements, and appointment needs
↗Broker LayerCustomer workflow, procurement, rates, settlement context, and policy
↗Carrier LayerAcceptance, equipment, driver assignment, authority, tracking, and dispatch
↗Driver LayerIdentity, consent, assignment, location permission, custody, and capture
↗Facility LayerCapacity, appointments, access, dock state, receiving, proof, and exceptions
↗Partner LayerEntitlement, provider data, result, usage attribution, and writeback requirements
↗MATERIAL STATE CHANGE
One action. One authoritative event. Every permitted view stays aligned.
A button click is not completion. TruckerTech resolves authority, validates policy and evidence, commits the state once, updates internal views, commands authorized external systems, and keeps reconciliation visible.
- 01
Initiate
A user, Partner, system event, schedule, or approved Automation trigger proposes a change.
- 02
Resolve
Identity, Role Organization, purpose, relationship, entitlement, and authority are resolved.
- 03
Validate
Policy, source authority, expected version, evidence, approvals, and risk controls are checked.
- 04
Commit
The valid internal state change is written once against canonical subjects and relationships.
- 05
Attribute
Source, authority, purpose, time, correlation, causation, and result become durable evidence.
- 06
Project
Every applicable TruckerTech view updates from the same authoritative event.
- 07
Connect
Governed, idempotent commands reach authorized customer and Ecosystem Partner systems.
- 08
Reconcile
Acknowledgements, failures, conflicts, retries, and compensations remain visible until resolved.
ONE PLATFORM · INTENTIONAL CONTEXTS
Different work surfaces. The same identity, relationships, and evidence.
Each context is purpose-specific and permission-aware. None becomes a disconnected product maintaining its own copy of the Driver, organization, Core, appointment, document, or Partner connection.
Operations
Action Center, Communications, Time, Flow, Map, Cases, Evidence, and Insights.
- Action Center
- Time + Flow
- Cases + Evidence
Career
Driver opportunities, carrier recruiting, onboarding, qualification, and relationship activation.
- Opportunities
- Consent
- Activation
Exchange
Discovery, comparison, activation, and administration of qualified Partner capabilities.
- Discover
- Authorize
- Administer
Control Center
Authority, integrations, policies, workflows, retention, security, billing evidence, and governance.
- Authority
- Policies
- Integration health
Driver experience
Safety-oriented next actions, assignments, documents, facility instructions, and field evidence.
- Next action
- Documents
- Field evidence
Partner Console
Registration, sandbox, certification, capability publication, integration health, and support.
- Sandbox
- Capabilities
- Support
FROM MODEL TO DAILY WORK
See the connected platform become one role-aware operating workspace.
The Workspace turns the Core, Layers, authority, connected state, and Partner capabilities into a practical daily environment for every authorized freight role.