Pack Identity and Lifecycle

Worka identifies packs by publisher tenant + pack name.

That identity is what later shows up in:

• registry records
• release records
• workspace attachments
• tool names

Identity

Think in three layers:

• the pack identity: publisher.pack
• the tool identity: publisher.pack.tool
• the release identity: the specific published version the workspace will use

That distinction matters because a workspace usually depends on a release, not on a vague idea of “the latest code in a repo.”

Lifecycle

A pack typically moves through these stages:

1. design or generation
2. source assembly
3. build
4. image or artifact publication
5. registration and probing
6. release creation
7. workspace attachment
8. runtime invocation

Each stage has a different failure mode. Build failure is not the same as registration failure. Registration failure is not the same as attachment failure. Attachment success is not the same as successful runtime invocation.

What to keep visible

When you are building or operating Worka, you should always be able to see:

• which release is attached to the workspace
• where the source and image came from
• whether the tools were discovered successfully
• whether the pack has the connections or secrets it requires

If that lineage is missing, debugging becomes much harder than it needs to be.