container-cargo-entities

To model container cargo data for terminal simulations, use canonical TypeScript interfaces, enums, and constants that define consistent structures for container concepts and cargo flows. This reduces ambiguity and enables reliable simulation logic.

Shipping container lifecycle state machines require TypeScript enums and interfaces defining container states, hazmat handling rules, and stowage planning. These standardized structures drive consistent state transitions throughout the simulation.

Create default container models for testing by using factory helpers that provide default constructors and reusable utilities. These bootstrap test data instantly, allowing you to customize fields and simulate terminal cargo flows without external lookups.

Yes, you can use these container data models without external lookups in your simulation context. They provide concrete data structures, factory helpers, and constants loaded directly into the context, satisfying all simulation requirements internally.

Yes, the skill includes hazmat handling and stowage planning definitions for cargo simulations. It provides standardized state-machine rules and TypeScript data structures specifically designed to manage hazardous materials and stowage decisions accurately.