Walkthrough: Deployable package

Concept: packaging produces the exact zip shape Lifecycle Services expects — <Model>/bin/** + Descriptor — with structural validation before you ever upload. The layout isn’t approximated; it was empirically specified against real LCS behavior, including the manifest and package-type ground truth.

Prerequisites

• A model that builds green (see Build Model).
• LCS access for the upload step (done by hand in the LCS asset library).

Steps

1. File → Create Deployable Package and pick the model.
2. Review the validation output — structure is checked before the zip is written.
3. Take the zip and upload it to the LCS asset library manually.

DEPLOYABLE PACKAGE · VALIDATIONReal UI capture pending (shares capture with bd-package-dialog)act-package

Verify it worked

• The zip opens to the LCS layout: <Model>/bin/** plus the Descriptor.
• LCS accepts the upload — the package was validated against the real service’s expectations, so rejection would be a surprise, not a routine.

If it goes wrong

• LCS rejects the package — the rejection reasons map to known root causes (manifest shape, package type, GUID registration); the validation output is your first read, and the layout rationale lives in the engineering spec (design/deployable-package.md in the product repo).

Troubleshoot further: Build, deploy & packaging guide.