Locked inputs
Forge manifest, lockfile, copied Mod manifests and sources, provenance, and SHA-256 hashes.
Lyrinox Forge
Lyrinox Forge is the early SDK foundry for Lyre-connected software. It composes LyreSDK core, selected Forge Mods, native bindings, validation, codecs, cache flows, tests, provenance, and eligible Market components into project-specific build artifacts.
Plain English
The Lyre owns identity, routing, provider resolution, contracts, and execution. Forge builds the project-facing SDK layer around that foundation.
Forge Mods are local executable bindings, validation, codecs, and hybrid local or remote wrappers. They are different from provider extensions, which describe provider capability adapters in the Lyre layer.
Search answers
Lyrinox Forge is an SDK foundry for Lyre-connected software. It packages LyreSDK, Forge Mods, native libraries, wrappers, tests, hashes, and provenance into a locked project artifact.
Lyrinox Market is for listings, licensing, purchases, and entitlements. Forge is for building the SDK runtime and language bindings your project needs.
Forge is in public preview. The current runtime worker is local-development-only until a production isolation backend is added, so the launch should be framed as an early public test.
Build output
Forge manifest, lockfile, copied Mod manifests and sources, provenance, and SHA-256 hashes.
A native Linux amd64 runtime library plus a C-like runtime header for host integration.
Go-facing package and tests, plus Python wrapper and native-loading integration test in the current slice.
A packaged tarball with test report and build outputs for local development use.