Ecosystem 02 of 07
SieF Developers
The engineers and companies who build frameworks, modules, connectors and tools on SieF.
In development
Who it is for
Independent developers and software companies, whether working for a venture, for an enterprise customer, or publishing their own work.
What it takes
- Working knowledge of the four-pillar architecture and where its authority boundaries sit.
- The Architect pathway through Lanvex Academy is the route to the credential a publisher needs; the credential is issued by Lanvex, not by a course completion.
- For publishing: enrolment as a company, which is a separate gate from any individual credential.
How it works
- Start on the application-layer SDK, ahead of the operating system.
- Build domain extensions against the contracts: Brain rules, Engine tools, Judge advisory scope, Fleet workload manifest.
- Prove you never patched the shared core, with tests that reject the unsafe paths.
- Submit for review, sign, and support what you ship.
What you own, and what you answer for
- Your code, your vulnerabilities, your maintenance, inside documented contracts.
- No secret in a package, no unrestricted ingestion, no reaching across a vault boundary.
- Outbound access only where the customer has authorised it and the network mode allows it.
Where we are
In development. Access opens in stages, by request, as each part of the SDK is ready for real use.
Questions
- Is there a free tier?
- Learning material is free. Development entitlements are not the same as a commercial licence, and a sandbox build is not a published product.
Tell us what you want to build, and we will bring you in as the SDK opens.