SDKs and development tools

Start before the operating system

Independent teams should not have to wait for the whole operating system to learn to build a framework. The application-layer SDK is a deliberate bridge: a framework is built as a desktop application first, against the same contracts the operating system will run.

The intended stack is portable domain extensions, stable SDK contracts, an application-layer host now and a trusted operating-system core later.

An application-layer build is a development and pilot host. It is not a certified sovereign deployment, and release language distinguishes the two.

What the SDK provides

• A starter project that builds with documented steps and no production secrets.
• Stable Brain schemas for roles, rules, jobs, gates, approvals and exceptions.
• Engine interfaces for deterministic tools, workflows, records and test fixtures.
• Declared interfaces for Judge consultation and Fleet execution, with their permission boundaries.
• Simulation, domain coverage reporting, security linting and deployment tests.
• A local encrypted vault, identity, permission and audit APIs.

The development workflow

Connect authorised sources, extract the domain architecture, structure a versioned domain operating model, build the four extensions, simulate and test, pass domain and security review, then sign and publish.

Source material and generated rules carry provenance records. Inference may help draft; no draft is authoritative before verification.

Moving to SieF OS

The two hosts share interface contracts rather than becoming separate products. Migration means adapting the extension packages to the operating system's contracts and re-running validation there. The work is designed to be small and predictable, and it is not zero.