Why AI work needs an artifact registry
Reusable agent work becomes safer when identity, versions, permissions, provenance, and delivery share one contract.
Copying prompts and scripts between chat windows is quick, but it erases provenance. A registry gives reusable AI work a durable identity, immutable versions, explicit permissions, and checksums.
Trust needs context
A verified publisher is useful, but it is not a substitute for inspecting permissions or pinning a version. Potion presents those signals together so installation can be an informed decision.
Reuse needs boundaries
Artifact types use closed contracts. Premium source remains separate from public previews, and clients receive only the data their authorization permits.