Registry
Trust tiers
How agentrig evaluates registry sources.
Trust tiers
AgentRig assigns trust at the registry artifact level. Discovery metadata and author identity stay separate from install trust.
| Tier | Source | Behavior |
|---|---|---|
official | Official AgentRig registry artifact | Installable. |
reviewed | Reviewed registry artifact that satisfies the canonical contract | Installable. |
listed | Discovery listing only | Not installable. |
blocked | Hard-blocked artifact | Not installable. |
yanked | Historical or advisory-only artifact | Not installable for new installs. |
How trust is determined
- Trust applies to published registry artifacts, not to arbitrary sources.
- The official AgentRig catalog can publish an approved SDK
InstallBundle; explicitly configured third-party sources must be static signed registries. - Directory presence can at most produce
listed, which is discovery-only. - Direct URLs, ZIPs, author repos, and raw Convex storage bytes are outside the install contract. An approved listing served by the official install-bundle endpoint is inside it.
Identity is orthogonal
verified-author is not a trust tier.
It is identity or ownership metadata only and must never be used to imply installability.
Discovery versus install
- Discovery may show
listedprojects, external repos, and submit-for-review flows. - Discovery must not present the same install CTA as
officialorreviewed. - Install trust comes from approved catalog or signed registry state plus digest verification, not from directory or profile metadata.
Selection installs
Selection installs inherit trust from their signed registry source. Selecting a skill, MCP, or hook from a plugin does not create new trust; the parent registry artifact must still be installable.
AgentRig refuses selection installs from listed, blocked, or yanked
entries. Directory presence, author identity, or AI-enriched metadata never
override registry installability.