How it works

HLCL is built around a pure Python generation pipeline. Vendor spreadsheets, STEP assembly rules, IPC inputs, and drawing standards all flow through the same code paths whether you run locally or in the app—no hidden binaries and no opaque “trust us” footprints.

In the web app that pipeline executes inside your browser via Pyodide (CPython compiled to WebAssembly). You pick families, tune tolerances and HLCL-001 drafting rules, and trigger a build; downloads are emitted as ordinary files—the catalog database, PCB library, models, and related artifacts tailored to your configuration.

Because generation is deterministic and parameterized, you can treat HLCL like infrastructure: check in configuration, reproduce an old drop for a legacy design, or diff two outputs when a vendor releases a new density recommendation.

The configure UI walks the workflow from presets through generate and migration cues so teams can adopt HLCL without a separate “library maintainer toolchain” beside Altium itself.