Publishing

Publishing snapshots a workflow's graph to an immutable semver version. Versions exist for people: a stable address to share, a changelog, a point to roll back to. They do not gate embeds — embeds always render the live draft.

Versions and the slug

• The first publish claims a permanent kebab-case slug, unique within the org. The slug never changes and is never reused: deleting the workflow retires its slug permanently, so a released address can't be claimed by someone else's workflow later.
• Each publish is a new semver version with an optional changelog entry.
• Rollback restores a version's graph into the draft and bumps the revision, so open editors hit the normal conflict panel instead of silently diverging.

Visibility and community

A published workflow starts private. Flip visibility to public in the publish dialog's share section and it appears:

• in the community feed at /community — public workflows with live shader previews, and
• on its published page at /w/<org-slug>/<slug> — version picker, live render, changelog, and a fork button.

Both pages are public; no account is needed to view them.

Forking

Forking copies a public version's graph into your own org as a private, unpublished workflow. The fork records its origin, and the editor shows a fork-origin badge as long as the origin stays public.