Developers
Start on the application layer,before the operating system exists.
The domain work you write is meant to move to SieF OS later through the same contracts. That is the point of the bridge: you do not have to wait, and you do not have to rewrite.
What you build
- A Brain extension: the deterministic rules, jobs, schemas, gates and approvals of your domain.
- An Engine extension: the executable workflows, tools, integrations and records.
- A Judge extension: the bounded advisory scope, its evaluation criteria and its escalation rules.
- A Fleet workload manifest: the model capabilities you need, declared, within the resource policy the platform enforces.
The rules that keep it trustworthy
- Patch the shared core to get domain behaviour.
- Let advisory output authorise execution.
- Embed a secret in a package, or reach across a vault boundary.
- Make an outbound call the customer has not authorised in a network mode that permits it.
Availability
The application-layer SDK is in development now, ahead of SieF OS, so the first publishers can start early and carry their domain work across. Access opens in stages, by request, as each part is ready for real use.
Tell us what you want to build and we will bring you in as the SDK opens.