DevRunbook-Public/docs/36-seed-content-delivery.md

36 — Seed content delivery contract

Catalog versus runtime content

catalog/seed-catalog.yaml is the complete 72-item product roadmap. It is not itself the runtime Playbook Package registry.

Runtime built-in content lives under content/playbooks/.

Version 1.1 delivers:

• 28 P0 publishable packages;
• 6 of those duplicated under examples/playbooks/ as normative documentation examples;
• 36 P1 authored backlog definitions;
• 8 P2 authored backlog definitions.

The application must never show an authored-backlog entry as an executable or validated playbook.

P0 release requirement

Every P0 catalog entry must have exactly one matching package directory whose manifest agrees on:

• logical ID;
• slug;
• title;
• category;
• playbook type;
• risk tier;
• default work mode;
• default autonomy.

The build fails on a mismatch.

Initial quality status

P0 packages are reviewed and editorial-reviewed or technical-reviewed. Static structure fixtures do not qualify them as validated. The product may promote an exact version only after the evaluation evidence required by docs/12-quality-evaluation.md exists.

Content import

Milestone 1 imports all package directories under content/playbooks/ idempotently. The seed catalog may be indexed separately in Prompt Lab as a content roadmap, but backlog definitions must not appear in the end-user Library by default.

P1/P2 authoring workflow

To promote a backlog entry:

1. create a complete package directory;
2. preserve catalog identity;
3. write task-specific guardrails and workflow rather than relying only on category boilerplate;
4. add at least one representative example and static evaluation;
5. complete editorial and technical review;
6. change deliveryStatus to publishable-package;
7. increment metadata.publishableCount;
8. pass offline pack validation and runtime package tests.

Content acceptance

A publishable package must be understandable and useful without reading the catalog entry. Its prompt-specific content must explain the task's special reasoning, not merely repeat the title. Generic platform sections are composed around it by the engine.

Future target

The product roadmap may ultimately deliver all 72 concepts, but catalog count must never be used as a marketing claim for available optimized prompts until every listed entry is a package with honest quality status.