Problem
Prompts and rubrics define runtime behavior, but they are not currently treated as versioned deployable artifacts. Platform improvements can leave old installs on stale prompt behavior forever, or risk overwriting local edits.
Desired shape
Prompts and rubrics should be first-class versioned artifacts.
They need:
- stable artifact IDs
- content hashes
- version metadata
- changelog or migration notes
- local override detection
- diff support
- upgrade planner support
Applies to:
- agent instructions
- generation rubrics
- maintainer rubrics
- relation extraction prompts
- daily memory prompts
- AI system task prompts
Acceptance criteria
- Prompt/rubric artifacts can be installed from bundles.
- Installed/current hashes are tracked.
- Clean prompts can auto-update.
- Locally modified prompts require PendingAction approval.
- Prompt diffs are readable through CLI and suitable for UI.
Context
The WooCommerce brain will improve through prompt/rubric iteration as much as PHP code. Those improvements need a safe upgrade path.
AI assistance
- AI assistance: Yes
- Tool(s): OpenCode (GPT-5.5)
- Used for: Drafting the issue from product/design discussion; Chris remains responsible for prioritization and implementation.
Problem
Prompts and rubrics define runtime behavior, but they are not currently treated as versioned deployable artifacts. Platform improvements can leave old installs on stale prompt behavior forever, or risk overwriting local edits.
Desired shape
Prompts and rubrics should be first-class versioned artifacts.
They need:
Applies to:
Acceptance criteria
Context
The WooCommerce brain will improve through prompt/rubric iteration as much as PHP code. Those improvements need a safe upgrade path.
AI assistance