Architecture and core concepts
SeeraOS separates domain modeling, backend generation, service execution and client development. Each part has its own responsibility.
Workflow
The diagram shows roles and the direction of information flow. It is not the result of an integrated deployment test.
Glossary
| Term | Role |
|---|---|
| Ontology | Describes domain concepts, their properties, relationships and constraints. |
DSL .unit | Declares operations and behavior within the scope supported by Composer. |
| Composer | Tools that turn models and configuration into backend artifacts. |
| Unit | A service participating in the platform and exposing a defined capability contract. |
| Unit SDK | Libraries for unit participation: lifecycle, configuration, communication and serving capabilities. |
| Protocol | Data exchange contracts, conventions and conformance vectors used by SDKs. |
| Exposition | Describes a unit’s exposed capability surface. |
| API Catalog | Describes the API offered by Edge and consumed by client tooling. |
| App Toolkit | Tools that use Catalog to prepare Web and Mobile client infrastructure. |
Backend and SDK
Unit SDK handles a unit’s interaction with the platform. It does not prescribe how business logic or data persistence is organized. The unit author implements its operations; separate frameworks may provide building blocks for the unit’s internals.
SDKs in different languages refer to shared contracts. The SDK package version and conformance corpus version are specific dependencies. A shared format or similar version number does not establish compatibility of any arbitrary component set.
From contract to client
Application tools consume API Catalog. They do not read Ontology or .unit files directly. Catalog describes an API, rather than complete application screens.
The team extends the generated infrastructure with UI, sessions, navigation and application behavior. User identity, tenant context and assigned permissions remain separate concerns.
Boundaries of the confirmed scope
The documentation describes confirmed roles and interfaces of components under development. It does not define officially supported deployments or guarantee that the entire flow works with any combination of versions. Verification of a specific solution should identify its components, configuration and test results.
Next: explore Unit SDK .NET.