Official registry workflow

AgentRig catalog review and the verified registry mirror are separate workflows.

Catalog listing lifecycle

Public upload is disabled for AgentRig 2.0. Maintainer submissions move through one review lifecycle:

pending_review -> approved | rejected | blocked

When a submission is approved, AgentRig materializes a Convex artifact_listings row with an SDK InstallBundle. That listing is immediately available to the CLI through the agentrig.ai install-bundle endpoint. No repository pull request or merge is required before users can install the approved catalog listing.

Rejected submissions do not create listings. Blocked submissions are retained for moderation and policy history, but they do not resolve to install bundles.

Verified mirror lifecycle

The agentrig-registry repository is an opt-in verified mirror for transparency and audit. It is not part of the approve path, and catalog listings work without a mirrored registry entry.

An AgentRig admin can explicitly choose Start verified mirror on a listing. That action opens a pull request against agentrig/agentrig-registry using the registry mirror GitHub App. The mirror PR serializes the listing's SDK InstallBundle into registry.json, per-artifact history files, lock/source documents, review metadata, and the mirrored version tree.

The mirrored files are useful for offline browsing, GitHub review, signed audit history, and independent inspection. CLI installs still resolve through agentrig.ai and the listing's InstallBundle.

Who triggers what

• Maintainer submit: a maintainer or trusted publisher submits an artifact for review. Automated checks and admin review decide whether the submission becomes approved, rejected, or blocked.
• Approve flow: approval writes the Convex artifact_listings row and SDK InstallBundle. The listing is then available from the AgentRig install-bundle endpoint.
• AgentRig admin: an admin may trigger Start verified mirror per listing. This creates the derivative registry PR for audit visibility.
• Trusted publisher and verified flags: trusted publishing and verified identity are provenance signals for review, UI, and mirror eligibility. They do not give publishers a direct registry write path. See the internal provenance story 0004-trusted-publisher-and-provenance.md for the planned OIDC and verified-publisher model.

Discovery entries

Discovery submissions created from pasted repo URLs or agentrig inspect output help reviewers find candidate files and metadata. They become installable only when the review flow approves a catalog listing and stores an InstallBundle.

Hosted AI enrichment is disabled for AgentRig 2.0. The CLI supports only local BYOK enrichment, where the user's provider key is sent directly to their configured provider and never to AgentRig.

Mirror safety rules

• Keep catalog approval separate from verified mirroring.
• Keep the SDK InstallBundle as the source of mirrored install metadata.
• Keep user repository access on the read-only agentrig-repository-sync app.
• Use the write-capable agentrig-repository-mirror app only for AgentRig-owned registry mirror repositories.
• Treat registry files as audit output, not as a prerequisite for CLI install.