Architecture principles

A dispatcher changing an assignment should not leave the load, stop context and document history in contradictory states. A proposed modular monolith lets those related operations share a transactional foundation while their domain interfaces are being understood. Microservices are not a prerequisite for modular software.

Module boundaries should express ownership of rules, not only folders or screens. Load management maintains movement identity; dispatch coordinates assignment; documents preserve evidence; integrations translate external messages. Extraction into separate services should follow measured constraints, not precede a validated core workflow.

The warehouse owns readiness and receipt, the ERP commercial order context, and accounting financial posting. Kaporeal's proposed role is to retain shared freight references and operational evidence between those systems. Duplicating every upstream rule would increase reconciliation work rather than solve it.

A REST-oriented interface is a design direction. The product is planned in Rust with Dioxus interfaces, but until public source release the crates, schemas, authorization and API contracts remain unverified. This website is a separate TypeScript build and must not be presented as the TMS.

A useful design includes late observations, reassignment, disputed documents and unknown references. Expected milestones must remain distinct from observed events. A correction should explain what it changes and who authorized it instead of silently replacing earlier evidence.

Operational simplicity is not the absence of rules. It is making those rules legible: which actor may perform a transition, what evidence supports it, what happens if an integration retries, and how an operator reviews an exception. These questions guide the conceptual contracts in the following guides.