Roles and statuses

Three roles run the marketplace, and every skill version moves through a small, explicit set of statuses. Nothing is published implicitly.

Roles

Role	Can do
`provider`	Register an organisation (instant, no approval step) and publish skills for review. The only role a visitor can claim at registration.
`reviewer`	Governance: claim submissions from the review queue, inspect bundles and check reports, approve, reject, or request changes.
`superadmin`	Everything a reviewer can, plus manage organisations, users and roles, suspend accounts, and archive skills.

Governance roles are granted by a super admin and can never be self-assigned.

Skill version statuses

Status	Meaning
`submitted`	Waiting in the review queue, with its automated check report attached as evidence.
`in_review`	A reviewer has claimed it.
`changes_requested`	Sent back with notes; the provider fixes and resubmits.
`rejected`	Declined with notes; nothing published.
`published`	Live in the catalog with a public review trail.
`superseded`	Replaced by a newer approved version of the same skill.

Skill and source statuses

The skill itself is in_submission until its first version is approved, published while a version is live, and archived when it is removed from the catalog. The source that carries the skills is active or archived; the owning provider (or a super admin) archives a source in one action, and every published skill in it leaves the catalog together. Skill names are unique per organisation, so two providers can publish the same name without conflict.

Organisation visibility

Organisations have no approval step. They are publicly visible only while they have at least one published skill; a super admin can reject an organisation (removing its publishing rights) or delete it with everything it published. See Providers.