57  Adoption Evidence

58 Adoption Evidence

Adoption evidence is the record of where the grimoire helped, where it was too heavy, and what should change before wider use. This page deliberately separates project-owned dogfood from reviewer-supplied and external-user reports.

58.1 Report Contract

Required fields:

  • id
  • title
  • provenance
  • task
  • spell_or_stack_used
  • surface
  • artifact_produced
  • verification_performed
  • time_cost
  • failure_or_friction
  • reuse_decision

Allowed provenance values:

  • project-owned
  • reviewer-supplied
  • external-user

Template: adoption-report-template.json

Create a draft report without publishing it:

python3 scripts/create_adoption_report.py   --id adoption.example-review.v1   --title "Example Review"   --provenance reviewer-supplied   --task "Describe the real task and artifact boundary."   --spell-or-stack-used spell.safe-refactoring.v1   --surface "Reviewer tool or workflow"   --artifact-produced "Patch, review, test, decision, or design artifact."   --verification-performed "Tests, checks, screenshots, or review performed."   --time-cost "Setup/runtime and whether the structure was worth it."   --failure-or-friction "Failures, overkill, unclear clauses, or friction."   --reuse-decision reuse   --write-report tmp/adoption-report.json

The generator validates one standalone report. It does not add the report to published evidence or increment external adoption counts; maintainer review is still required.

58.2 Intake Decision

Use the pending intake decision template and validator when a maintainer is ready to review a submitted report:

python3 scripts/check_adoption_intake.py validate examples/adoption/adoption-intake-decision-template.json

The pending template is not adoption evidence. A report counts only after a named maintainer accepts a reviewer-supplied or external-user report and the accepted report is published.

Pending intake template: adoption-intake-decision-template.json

58.3 Project-Owned Dogfood Reports

Report Provenance Spell or Stack Verification Reuse Decision
Release Gate Stack Dogfood project-owned stack.release-gate-stack.v1 Local validation, Quarto render, pytest, GitHub Pages workflow, and live URL checks. Reuse for public releases and major roadmap phases.
Jailbreak-Resilience Bench Dogfood project-owned spell.jailbreak-resilience-review.v1; stack.ai-red-team-loop.v1 Canary non-leakage checks, utility-preservation scores, fixture validation, and internal-link audit. Reuse for AI workflow security reviews.
Semantic Canon Self-Review project-owned spell.safe-refactoring.v1 as a review discipline; canon quality validation Pattern scan found 1,345 generated-template summaries despite zero stub rows. Reuse for future canon corrections and release reviews.

58.4 External Status

  • External reports published: 0
  • Reviewer-supplied runs imported: 0
  • Policy: Do not fabricate external adoption. Project-owned dogfood is useful but labeled separately.
  • Next request: Invite external users or reviewers to submit reports using the template.

58.5 Rules

  • Do not count project-owned dogfood as independent adoption.
  • Do not remove failed or awkward reports; those are product evidence.
  • Do not include secrets, proprietary code, or private customer data.
  • Record the verification path before claiming the spell or stack worked.