Capabilities
What is built, what is partly built, what is not
An industrial buyer finds out either way. Publishing it here is cheaper than a failed pilot, and a matrix with gaps in it is the only kind anyone believes. Every line below was decided by reading the code and running it — the classifications come from the project’s own technical audit.
Built & tested14Partly built4Simulation only3Not built8
Planning & optimization
This is the part of the system that is genuinely finished.
Mixed-SKU pallet optimization | Built & tested | Shelf first-fit-decreasing with height layering and per-box settling. Deterministic; identical inputs produce an identical plan hash in the browser, the CLI and the Python package. |
Stability scoring | Built & tested | Support measured against the surfaces a case actually rests on, plus a weighted centre-of-mass term. Geometric, not a transport simulation. |
Plan validation | Built & tested | An independent validator: bounds, interpenetration, floating cases, support, height and mass budgets, bottom-up buildability, SKU conservation. |
Crush constraints | Partly built | Enforced when you supply per-SKU crush limits, and explicitly reported as not run when you do not. No crush data ships with the project. |
Constraint modes | Built & tested | heavy-low, fragile-high and speed-mode: deterministic re-orderings of the same packer, checked against the browser port in CI. |
Multi-objective solver (CP-SAT / MILP) | Not built | The current engine is a heuristic and says so. No exact solver is implemented, and no claim of optimality is made anywhere. |
Execution & safety
AI proposes; a deterministic validator checks; a safety gate authorizes; only then does a robot move.
Plan artifact | Built & tested | Immutable and content-addressed, carrying optimizer, validator, SKU, pallet, robot and gripper provenance. Editing a plan changes its hash. |
Execution planning | Built & tested | A validated plan compiles to Cartesian intent — approach, acquire, traverse, place, retreat — bound to that one plan's hash. |
Safety gate | Built & tested | Deterministic, fail-closed, no override parameter. It recomputes both hashes itself and refuses as a whole. It is a software authorization boundary, not a safety controller. |
Simulated cell execution | Simulation only | A real kinematic bookkeeping model: pose, payload, tool state, a virtual clock, and refusals a controller would actually make. Runs in CI. |
Physical robot execution | Not built | No adapter in this project has ever driven a physical robot. The URScript compiler is real code on a real socket that has never been pointed at a controller. |
Certified safety functions | Not built | None. Certification is a property of an assessed installation, not of a software package, and nothing here has been assessed. |
Robots & grippers
Tiers describe evidence, not ambition. Community means it passes the contract suite against a simulator — nothing more.
Universal Robots (UR10e) | Partly built | Community tier. A real URScript compiler that speaks the secondary client interface on TCP 30002, plus a published capability profile. Never run on hardware, and the profile is small for a full GMA pallet — the safety gate will tell you so. |
FANUC / KUKA capability profiles | Partly built | Community tier. Published specifications modelled for reach and payload checking. No adapter exists for either. |
ABB / Yaskawa / Doosan | Not built | Not present. Earlier copy on this site described certified connectors for these vendors; there were none. |
Gripper capability model | Built & tested | Vacuum, parallel clamp and fork envelopes, each answering “can this tool lift this SKU?” before a pick is planned, including the surface it cannot hold. |
Adapter contract suite | Built & tested | One reusable suite every adapter must pass, including the test that an adapter refuses to move without a granted authorization. |
Integration
SKU / WMS CSV ingest | Built & tested | Fuzzy header mapping with a confidence score, so a messy export maps without hand-editing. |
MCP server | Built & tested | Dependency-free JSON-RPC over stdio with optimize, validate and ingest tools. Tested end to end, including a subprocess round-trip. |
HTTP API | Built & tested | /api/v1 — plans, plan history, URScript and CSV exports, API keys — with an OpenAPI document at /api/v1/openapi.json, per-plan quotas counted in the database, and contract tests for 401, 403, 429 and 503. The public demo endpoints (optimize, validate, ingest, co-pilot) are unversioned and rate limited per instance. |
Signed verification attestations | Built & tested | The hosted validator re-verifies a plan and signs what it found (Ed25519). Verifiable offline with `palletizer attest verify` against a pinned key; Node-signed, Python-verified in CI. A record of a check, not a certificate. |
Paid plans | Built & tested | Each line of /pricing is an entitlement a gate reads (ENTITLEMENTS.md, generated from the constants the gate imports). A test fails if one is read by nothing. No plan authorizes robot motion. |
OPC UA | Simulation only | A real client and a real mock server. They have only ever talked to each other, and the motion writes (TargetPose + ExecuteMove, and the AI correction path) are quarantined: they refuse. |
ROS 2 | Simulation only | Nodes exist and the package imports without rclpy. The bridge is quarantined — execute_plan and estop refuse — and the LiDAR path returns a constant pose when Open3D is absent. |
MQTT / PROFINET / EtherNet-IP / MES / ERP | Not built | Not present in the codebase. |
Operations
Deterministic replay | Not built | Execution events are recorded; the replay command and viewer are on the roadmap, not built. |
Telemetry pipeline | Partly built | A real async JSONL writer with rotation and backpressure. Nothing currently produces into it. |
Fleet management / cloud | Not built | Does not exist. The gateway package is a demo API and an edge orchestrator, not a fleet platform. |
OTA updates, audit logs, RBAC | Not built | Not implemented. (Subscription tiers do gate the hosted API, history, exports and limits — see Paid plans above — but there is no audit log or role model.) |
On the word “certified”
Nothing in this project is certified, and no amount of software architecture will make it so. Certification is granted to an assessed installation by an accredited body, against the standards that apply where the cell is installed. What the software can do is be built so that such an assessment is possible: deterministic plans, an authorization boundary that fails closed, evidence artifacts, and a record of what was planned and why. That is the work in progress.