Skip to content
published Visibility internal Owner erik@uvilo.com Approver _ Created _ Updated _

Bot Prompt Inspectability Specification

Exact specification from Research decision 5.2 (Charter: Inspectability by Humans).

Artifact-Based Prompt Inspection

Bot system prompts are inspectable by humans using the application/vnd.prompt-version artifact type, the same way:

  • application/vnd.markdown-file is used to inspect files
  • application/vnd.git-changes is used to inspect changes across multiple files

How It Works

An application/vnd.prompt-version artifact is created with a JSON/YAML payload containing:

  • promptId — the prompt’s database ID
  • version — the version number (positive integer)
  • name — the prompt’s name

When opened, the UI loads version N and N−1 from the database and displays a unified text diff. This allows humans to inspect prompt content and track changes over time without direct database access.

Additional Artifacts

Additional artifact types may be created if needed to support prompt inspection workflows.

Follow-up: git-changes Enhancement

A todo item is created to modify the application/vnd.git-changes artifact type to accept two commit hashes as parameters, displaying the diff between them. This makes git-changes useful for comparing arbitrary commits, not just changes vs upstream.

Todo: Modify application/vnd.git-changes to accept two commit hashes for diff display.