Start from search and package detail when the question is “what is this package?” rather than “who owns this release?”
Workspace
Use the workspace that actually owns the release boundary
Use rawctx Hub for review, then move into the workspace for invites, tokens, settings, claim, and publish actions.
Settings, invites, access grants, favorites, claim, and publish belong inside the workspace that owns the scope.
Do not collapse candidate discovery and ownership. Review publicly, then claim and publish from the workspace that actually maintains the package.
The workspace is not a prettier copy of rawctx Hub. It is the ownership surface. Use it when access, org membership, settings, or release state need to be bound to a specific workspace.
This is the same boundary the web UI enforces: public review can stay open, but release and access management stay workspace-scoped.
rawctx login --registry https://api.rawctx.dev
rawctx search "customer orders" --registry https://api.rawctx.dev
rawctx claim @dbt-hub/jaffle-shop --registry https://api.rawctx.dev
rawctx publish ./my-package --registry https://api.rawctx.dev