Freight-specific agents
Quote, sourcing, tracking, compliance, document, payment, exception, customer-update, and claims agents operate against AutumnLogic freight records.
Technology
AutumnLogic keeps freight operations vertical while EchoAtlas provides generic governance primitives: permissions, approvals, telemetry, traces, and usage records.
AUTUMNLOGIC OPS
Architecture
The technology model is intentionally narrow: freight-specific decisions are visible, policy-bound, and interruptible by human operators.
Quote, sourcing, tracking, compliance, document, payment, exception, customer-update, and claims agents operate against AutumnLogic freight records.
EchoAtlas remains horizontal: actor identity, policy checks, approval envelopes, telemetry, traces, and usage metering.
Low margin quotes, high-risk carriers, document failures, severe updates, and payment thresholds stop for review.
AutumnLogic talks to EchoAtlas through src/lib/echoatlas/client.ts only.
Loads, quotes, tenders, carriers, documents, invoices, claims, and exceptions live only in AutumnLogic.
API boundaries use structured schemas, canonical field names, and ISO-8601 UTC timestamps.
System boundary
AutumnLogic uses EchoAtlas without turning the platform into a freight database.
AutumnLogic owns loads, carriers, shippers, tenders, documents, pricing, trust, and quote-to-cash state.
Identity, permissions, approvals, event logging, risk envelopes, payments orchestration, and traces stay horizontal.
Each AI recommendation includes thresholds, confidence, risk factors, and the approval state needed before action.
Shipment events, AI actions, approvals, documents, and payment recommendations remain auditable across the load lifecycle.
Freight schemas do not leak into the horizontal platform. AutumnLogic stays the vertical system of record for brokerage data.
The platform favors explicit schemas, seeded behavior, role-scoped access, and repeatable validation over ad hoc automation.
AutumnLogic can walk through a quote, carrier assignment, exception, document validation, or payment release as a traced workflow.