The orchestration engine.
Circuit 42 is the system-level execution engine behind Circuit 40s: structuring workflow logic, assignment rules, event propagation, audit trails, and shared shipment state across product surfaces.
Everything flows through C42.
When a customer books via Circuit 41, Circuit 42 receives the event, evaluates rules, capacity, corridor context, and operator availability, then creates the required execution state. When an operator updates a status in Circuit 44, Circuit 42 propagates that state to the relevant surfaces. When an enterprise system pushes a booking via Circuit 43, the same orchestration model handles the work.
The purpose is not to be consumer-facing. C42 is the underlying coordination engine that keeps product surfaces aligned around the same operational truth.
- Configurable routing and assignment rules
- Status synchronisation across connected product surfaces
- Conflict detection and resolution on slot availability
- Centrally managed corridors, rates, and capacity constraints
- Complete event history and audit log per shipment
- Webhook fanout to connected enterprise systems
Built for operational scale.
Assignment logic
Shipments are evaluated against corridor, capacity, current load, operator scope, and configurable priority rules before work is assigned.
State propagation
Operator actions become structured state changes that can update customer surfaces, enterprise webhooks, and operational control views.
Slot management
Corridors, departure slots, and weight limits are managed centrally. C42 enforces availability constraints at booking time, across all entry points.
Immutable event log
Every state change — booking, assignment, status update, escalation — is written to an append-only log. Complete traceability per shipment.
Exception handling
Delays, failed deliveries, and escalations are detected automatically and routed to the control tower with full context for resolution.
Event-driven webhooks
Enterprise systems connected via Circuit 43 receive webhook events for every significant shipment state change, in structured JSON.
Programmatic access to the coordination layer.
Enterprise integrations via Circuit 43 communicate directly with Circuit 42's routing and event infrastructure. Programmatic booking, real-time status polling, and event-driven webhooks for every shipment state.
Every API call is authenticated, rate-limited, and fully logged. Circuit 42 maintains the authoritative state — integrations read and write against the same model as every other surface in the network.
# POST /webhooks/your-endpoint
# X-Circuit-Signature: sha256=...
{
"event": "shipment.status_updated",
"timestamp": "2026-05-20T11:42:00Z",
"data": {
"shipment_id": "SHP-2026-04471",
"status": "customs_cleared",
"corridor": "LHR-LOS",
"operator_id": "OP-0091",
"updated_at": "2026-05-20T11:41:58Z"
}
}