AxiolidGeometry infrastructure without format or backend lock-in.

A kernel is a boundary, not a format parser ​

Axiolid is the neutral middle layer for applications that import, construct, query, compile, or render geometry. It is designed so source-format semantics stay in adapters and execution choices stay in providers.

flowchart LR
  accTitle: Axiolid boundary from source adapters to providers
  accDescr: Source adapters translate into neutral values and a geometry graph. Typed operation contracts carry requests to explicitly selected providers.
  Sources["Source adapters<br/>IFC, STEP, applications"] --> Neutral["Neutral values / graph<br/>Axiolid model"]
  Neutral --> Contracts["Operation contracts<br/>typed results and budgets"]
  Contracts --> Providers["Providers<br/>reference / CPU / GPU seams"]

That separation keeps a mesh-only user from paying for topology or GPU APIs, lets a future adapter reuse the same representation, and makes backend claims inspectable rather than implicit.

Start with evidence ​

Axiolid is early software. The project deliberately distinguishes storage, contracts, and algorithms that are actually exercised. Before choosing it for an application, read:

• Getting started for dependency and feature selection.
• Capabilities for what is implemented, represented, or intentionally deferred.
• Architecture for dependency direction and execution seams.
• Geometry concepts for interactive STL examples, equations, tolerance, orientation, and open-profile semantics.
• Architecture decisions for the non-negotiable design choices.
• Roadmap and changelog for current direction and user-visible history.