58  Adoption Playbook

59 Adoption Playbook

The public repo needs an adoption flywheel that collects real use without overstating it.

59.1 Maintainer Loop

1. Ship generated templates and bundles with stable seals.
2. Invite users to start from one spell or stack, not the whole book.
3. Ask for an adoption report that includes success, friction, verification, and whether the spell was reused.
4. Import reviewer-supplied model runs only through the manual import contract.
5. Promote vocabulary through the usage graph, then require human audit before canonical status.

59.2 Intake Paths

• Adoption evidence template
• External walkthrough
• Installable library
• Evidence browser
• Canon audit

59.3 Non-Negotiables

• Do not fabricate adoption.
• Do not shrink the concept just because a phase is labor-intensive.
• Do not treat project-owned runs as independent external proof.
• Keep failures, ties, and overkill reports visible.
• Keep jailbreak material defensive and defanged.