Smooth Bundle projects describe how assets should be organized before delivery. The public UI should explain the workflow first, then recommend a technical project type.

In code and API payloads, the project types are still basic and versioned. Public copy should call them Continuous projects and Release projects.

Continuous projects use mutable stable paths. They represent the current state of a project, media library or synced folder.

• Best for CMS media, browser uploads, folder sync and current asset libraries.
• URLs do not include a version segment.
• Files can be updated under the same path when the workflow expects the current file.

https://cdn.smoothbundle.com/<user-slug>/<project-slug>/<asset-path>

Release projects use explicit versions. They are meant for app assets, CI/CD output, design systems and other workflows where a published set of files should remain addressable.

• Best for versioned build output, release previews and production app assets.
• Version URLs include a version, tag or latest segment.
• The CLI supports sbundle create-version, sbundle push and sbundle publish-version.
• Use pinned versions when a consumer must stay on one exact asset set.

https://cdn.smoothbundle.com/<user-slug>/<project-slug>/1.4.0/<asset-path>

Rollback should currently be described as repointing latest or a tag to an older version. Do not present it as a dedicated rollback command or audit workflow.