Participants
SieF Developers
Enrolment, the credentials a publisher needs, the toolchain, and what a conformant framework must prove.
Who this is for
Individuals and companies that build SieF-compatible frameworks, modules, integrations, tools and technical services, whether for a venture, for an enterprise customer, or to publish themselves.
What you need
- Working knowledge of the four pillars and the authority boundaries between them.
- The Architect pathway credential for framework publication, issued by Lanvex after practical, proctored assessment rather than course attendance.
- Company enrolment to publish commercially, which is a separate gate from any individual credential.
What conformance means
A conformant framework proves, with tests:
- It never patches or overrides the trusted core.
- Advisory output cannot authorise execution, change policy or bypass Brain.
- Declared permissions match what it actually uses.
- Unsafe paths are rejected, and the rejections are covered by tests.
- Its audit log records what happened, including what failed.
What Lanvex owes developers
Onboarding, usable SDKs, documentation, testing tools, secure publishing, predictable review timelines, clear intellectual-property terms, and real commercial demand to build against.
Intellectual property
You own what you write. Access to the SDK is not an assignment of your code, and it is not a licence to extract Lanvex's. Where code is reused in either direction, a specific licence says so.