Repository navigation
Packvium 1.3.0
Portable operational artifacts: hand a packing result to a WMS, a TMS or a printer that runs
no engine. Nothing breaks 1.2.0.
Added
packvium.artifacts—build_operational_artifact(request, result, loading_orders=)and
canonical_artifact_json(). Onepackvium-operational-artifact/v1document carries the
execution plan, exact geometry, the values a work order shows, and the request that produced
it. Every Packvium engine builds the same bytes from the same result.packvium.artifact_exports—export_json,export_csv(RFC 4180, 18 columns) and
export_work_order_html: a printable work order in one HTML file with no scripts and no
external resources.examples/artifacts.py.
Changed
packvium.execution,packvium.artifactsandpackvium.artifact_exportsare in the frozen
API snapshot, with the same guarantee as the rest of the public surface.canonical_plan_jsonwrites RFC 8785. Every plan the engine produces keeps its 1.2.0
bytes. A float, U+2028 or a key outside the Basic Multilingual Plane is now spelled as the
other engines spell it, and an integer beyond 2^53 − 1 raises instead of being written.- Faster commerce lookups, same answers. A pinned catalog or tariff version resolves
without scanning the history (1000 lookups over 16000 versions: 374 ms → 1.2 ms), a
snapshot's SKU lookup builds its index on first use, andpackvium.paretofinds a two-axis
frontier with one sort instead of comparing every pair.