Registry and Publication
Worka’s registry and publication model determines whether build output becomes usable capability or just build debris.
When Forge produces a pack or service, several separate things may exist:
- source
- an image or other runnable artifact
- a release record
- a marketplace or discovery listing
- a workspace attachment
Treat those as related but separate concerns. “It built successfully” does not mean “users can use it.”
What the registry is for
The registry is the system of record for artifact identity and release state.
It needs to tell you:
- what was built
- which version exists
- where the runnable image lives
- where the source lives
- which release is installable
- who can see it
That metadata is what later lets the platform:
- attach the result to a workspace
- search for existing capability before rebuilding it
- trace a running pack or service back to its origin
Publication decisions you need to make
Operators need clear defaults for:
- private vs shared vs public publication
- allowed source destinations
- allowed image destinations
- whether free or trial environments may publish publicly
- who can approve publication
Do not let those defaults emerge accidentally from the first successful Forge run.
Marketplace and reuse
Publication is not only about storage. It is also about future reuse.
If an artifact is meant to be found and reused, the marketplace or discovery layer needs enough metadata to answer:
- what it does
- whether it is installable
- whether it is trusted
- who published it
- what it depends on
That is how Worka avoids rebuilding the same capability repeatedly.
What operators should inspect
Regularly review:
- recent publication failures
- public artifacts
- stale private artifacts that are no longer attached anywhere
- artifacts whose source and runnable image are out of sync
- artifacts that are installable but not reviewed to your standards
The goal is to keep the publication layer understandable, not just full.