# Explicit parcels and lossy shipment summaries

Run the synthetic model with Node.js:

```sh
node model.mjs
```

Two parcels of five kilograms and parcels of one and nine kilograms both have
count two and total ten kilograms. A fictional charge of 12 currency units per
shipment plus three per parcel above eight kilograms produces 12 versus 15.
The model uses whole grams and integer cents; these are not a private tariff
or a historical price.

Further assertions select a particular parcel for a transport leg, allocate
100 item units across two parcels, expand identical copies into separate
records, and compute a separate count-based tariff from the explicit list.
Missing/duplicate identities and unresolved leg/allocation references fail.

The example's strict checks are its own contract, not a claim that every
private input path enforces them identically. It does not implement all
dimensions, unit conversion, eligibility, incomplete-data handling, item
conservation, pricing scopes, or the application's normalization pipeline.
It demonstrates information the explicit model can retain, not full private
pricing equivalence. No files, network requests, dependencies, or caches are
created by the model.