Skip to main content

Create, Build, and Publish

The build path in Worka matters because a pack is only useful once the platform can discover, probe, register, release, and attach it.

That means you need more than a successful local run. You need a build flow that produces:

  • a valid manifest
  • a runtime artifact or image
  • registration metadata the platform can inspect

Think in stages​

The reliable sequence is:

  1. create or refine the source
  2. validate the manifest
  3. build the pack image or artifact
  4. register and probe it
  5. publish the release
  6. attach it to a workspace

Skipping those stages often leads to “it built but the workspace still cannot use it.”