Moderation

Moderators and administrators use the native admin queue. Access is controlled by site roles; bootstrap administrators can also be configured by email on the server.

Reviewing a submission

Before approving, verify the image, proposed name, category, and tags. Approval and numeric-ID allocation occur in one database transaction, protected by a database advisory lock so concurrent approvals cannot assign the same ID.

Rejections require a useful explanation. The submission remains available to its author with that explanation.

Reports and published metadata

Signed-in users can report broken textures, duplicates, inappropriate content, or incorrect metadata from a head page. Moderators resolve or dismiss each open report with an auditable note. Administrators can edit a published head's name, category, and tags; each edit emits an upsert catalog revision.

Removing a head

Removal is a soft delete. The head keeps its numeric ID, texture, taxonomy, actor, timestamp, and reason, but disappears from public catalog responses and plugin snapshots. IDs are never recycled.

Every approval, rejection, and removal creates a moderation event and increments the catalog revision. This gives deployments and clients a single monotonic signal for catalog changes.

Restoring and merging a head

An administrator can restore an accidentally removed ID. Duplicate IDs can be merged into a canonical published target: the source remains a removed audit record and its web and API detail URLs return permanent redirects to the target.