Native Prompts

This topic explains how PaperProof treats prompts as governed, versioned artifacts rather than hidden application strings.

Official Copilot prompts are protocol-native content. They are not only strings embedded in the static website bundle. Prompt artifacts Prompt packages are published as PaperProof generic_file artifacts backed by Walrus content. This gives each prompt: an artifact series; version history; content commitments; Walrus references; an auditable update path. Prompt registry The prompt registry maps an application route to a prompt artifact series and a version policy. Examples: copilot/global copilot/memory A route may: follow the latest version of the series; pin a specific version. Why this matters Official prompts become traceable, versioned, auditable, and replaceable. Applications can update prompt behavior without treating one static build as the only source of truth. Prompt registration is controlled through the governance-bound active operator....