Skip to content
Talk to us

Infrastructure 03 of 06

SieF SDKs and Development Tools

The documented contracts, tools and development environments an independent company needs to build a framework without rebuilding the platform.

In development

What it enables

  • Building a framework on the application layer now, ahead of the operating system, against contracts that carry over.
  • Turning an authorised domain operating model into Brain rules, Engine tools, a bounded Judge scope and a Fleet workload manifest.
  • Testing, simulation and coverage reporting, so a publisher can show what their framework does deterministically and what it does not.

Who it serves

  • SieF Ventures building their first framework.
  • SieF Developers writing modules, connectors and tools.
  • Lanvex’s own first-party teams, who use the same contracts as everyone else.

Scope and boundaries

  • The application layer is a transitional host. A desktop build is not a certified operating-system deployment and is never described as one.
  • Domain ingestion and runtime execution are separate permissions. Access to source material is not access to a customer’s systems.
  • Access to the SDK is not an assignment of anyone’s code. A publisher owns what it writes; Lanvex keeps its own.
  • Moving from the application layer to the operating system takes some adaptation, and the contracts are designed to keep that work small and predictable.

In practice

  • A starter project builds and runs with documented steps and no production secrets in it.
  • An adapter reads an authorised procedure manual into a versioned domain model, keeping the provenance of every rule it proposes.
  • A connector reaches one approved enterprise system, under the customer’s authorisation, and nothing else.

Where we are

In development, and the first part of the platform publishers will touch. Access to the application-layer SDK opens in stages, by request, as each piece is ready for real use.

Questions

Can I start before SieF OS exists?
That is the point of the application-layer bridge. The domain work you write is meant to move to the operating system later, through the same contracts.
Who owns what I build?
You do. Your company owns its framework, its brand and its customers, subject to your own contributor agreements.