Ordellum AI Native SDKIn development
How a package is produced
A requirement goes in; a signed, versioned and verified package comes out.
Stage 1: Intent
The need is analysed from plain language or technical requirements.
Stage 2: Context
The project’s existing structure and constraints are extracted.
Stage 3: Knowledge
Relevant standards, patterns and examples are retrieved.
Stage 4: Design
An architecture is drawn up and building blocks are chosen.
Stage 5: Build
Code, tests and documentation are produced.
Stage 6: Verify
Multi-layer checks run until the quality bar is met.
Stage 7: Deliver
A signed package with platform libraries is handed over.
A verified package generation is complete only when all seven steps have run and a versioned artefact exists.
Step 1: Analyse requirements
Plain-language or technical requirements are analysed.
Step 2: Select building blocks
The required modules and dependencies are chosen.
Step 3: Compose
Modules are combined into a compatible project structure.
Step 4: Generate
Code and smart contracts are produced or updated.
Step 5: Build and test
Compilation, linting and unit tests run.
Step 6: Check
Baseline security and standards checks are applied.
Step 7: Sign
A signed artefact, manifest and verification report are created.
Instead of selecting components from a fixed library, the SDK regenerates output for each project: it matches the requirements exactly, carries no unused code and is optimised for the target network. Smaller packages, optimised gas consumption and network-specific tuning lower both infrastructure costs and the costs paid by end users.
The pipeline handles everything from new projects to adding a module to an existing one. When extending a project, the SDK analyses the current structure, identifies the files the change will touch and applies the integration changes without breaking the rest.