What can be checked

The proof engine

We do not ask for trust; we show what can be checked. This page sets out what the engineering consists of, what can be inspected, and — just as importantly — what is not being claimed.

Honest surfaces

What a static public site can truthfully say about itself, its build, and the status of the products behind it.

What this page can actually know

Served as a static site — it has no connection to build systems, monitoring or production services, and does not pretend otherwise.

Public website

Static export, served from the repository build output.

Static

Engineering test suites

Executed in the development environment before each build. Results are not published to this site.

Not published here

Product services

ZylForge, ZylCode and the wider ecosystem are in development; no production service status is claimed.

In development

Live monitoring

No uptime, latency or incident feed is wired into this site, so none is displayed.

Not wired

When a verifiable figure exists — a released version, a published package, a documented specification — it appears on the relevant product page with its source. Nothing on this page is simulated measurement.

Engineering surfaces

The components the work actually consists of — stated without invented counts or coverage figures.

Repository

Private / Secure

No public source mirror is published

Test discipline

Automated suites

Run before every build — totals not published

Runtime

Python 3.12+

Local execution by default

CAD kernels

CadQuery, FreeCAD

OpenCascade-based geometry stack

Formats

STEP, STL, DXF

With G-code export preparation

Simulation

FEA validation path

Coverage percentage intentionally not claimed

Explore the Architecture

Dive deeper into the engineering principles and the design decisions behind each Zylvex product.

Explore ZylForge Corporate Trust Centre