PROJECT / GOALS → ARCHITECTURE → EVIDENCE

Capability parity at the contract level, with stronger evidence.

The goal is not to be another packer with a different heuristic. It is to make the same capabilities the mature engines have expressible in one contract, and then to prove them harder than anyone else does.

01

Self-contained, not a wrapper

A capability belongs in the public model, the solver portfolio, the validator and the conformance fixtures together. If an engine cannot honour a rule, it rejects it explicitly instead of silently ignoring it.

02

Expressiveness that survives contact

Per-axis rotation control, stack density checked at every level, contact graphs, centre of mass, axle load and loading order are all in the public contract, so nobody has to maintain a private fork to express them.

03

Evidence as a feature

Four runtimes, one corpus, and a validator that shares no code with any solver. Of the six open-source engines in our published comparison, none documents an independent check of its own output.

04

Honest about the gaps

One capability gap, uneven quality between the reference engines and the native ones, and a measured speed frontier that supports no speed claim. All three are named in the docs and owned by work items.

ARCHITECTURE

Layers that keep a solver free of the outside world.

UnitsExact fixed-point lengths and weights. No floating point anywhere above this line.
DomainItems, containers, obstacles, rotations, placements, requests and results as immutable values.
ConstraintsHard predicates: bounds, collision, weight, orientation, floor, compatibility, support, top load, obstacles.
AlgorithmsPython and PHP: six single-container solvers and the multi-container orchestrator, behind one deadline. Rust runs its own portfolio; the JavaScript fallback runs a deterministic greedy search over one item ordering under fast and eight under balanced and quality.
ObjectivesLexicographic ranking of feasible solutions as exact integers.
ValidationIndependent recomputation from the result, sharing no code with candidate generation.
SerializationOne JSON contract and a CLI, identical across runtimes.
Nested packingA packed container becomes an item for the next level.
ExtensionsConstraints, ordering, scoring, selection and complete solvers, registered per application.
CommerceRating, policy and catalog versioning. A leaf: it imports nothing from the solver, and nothing in the solver imports it, so a quote cannot reach into a search.
SOURCE

Everything above is checkable in the source.

The schema, the fixtures, the validator and the release gate are in the open. Reading them is the fastest way to decide whether this project's claims are worth anything.

Browse the packages, each linked to its repository