Skip to content
Ordellum Docs

Ordellum AI Native SDKIn development

Package workflows

Bring your own package, refine what the SDK produced, merge packages with your approval, verify and deploy.

  1. Step 1: Bring your own package

    Upload an AI Native SDK package you created earlier and continue from there.

  2. Step 2: Refine a generated package

    Modify the package the SDK produced to suit your needs.

  3. Step 3: Merge control

    Combine two separately generated packages — only with your approval.

  4. Step 4: Security check

    Run a security review of a generated package.

  5. Step 5: Deploy

    Start deployment for a package, or for merged packages.

Independent building blocks — financial mechanisms, identity layers, game mechanics, governance structures — are treated like construction pieces. Automatic dependency resolution and conflict detection combine them into a complete, production-ready project.

Dependencies are resolved through the knowledge graph; packages are built in the right order, and groups that can be processed in parallel are identified automatically. Version compatibility is checked at every step.

What counts as a composition
Previews, alternative architectures, different module combinations and standalone compositions count towards the composition allowance.
What does not
The main composition inside a package generation, failures caused by the platform and repeats with the same idempotency key.

When several developers change the same project, an AI-based analyser evaluates the semantic intent of each change to resolve merge conflicts. Merging two unrelated changes turns from hours of manual work into an automated step measured in seconds, so teams can move in parallel.