Skip to content

Plugin Catalog

Guide Maps

graph LR
  console["Console notifier"] --> webhook["Webhook notifier"]
  webhook --> pager["Pager notifier"]
  pager --> proof["Public proof routes"]
flowchart LR
  question["Which built-in plugin should I inspect?"] --> plugin["Choose one concrete adapter"]
  plugin --> contract["Read its fields, actions, and docs"]
  contract --> compare["Compare why it proves a different framework pressure"]

Use this guide when the capstone's concrete plugins still feel like implementation filler. The goal is to show why each built-in adapter exists and what metaprogramming pressure it helps prove.

Built-in plugins

Plugin Why it exists Best proof surface
console proves simple string rendering with defaults, choices, and boolean coercion make demo, plugin delivery console, and field tests
webhook proves required fields, numeric coercion, and deterministic structured payloads plugin delivery webhook and runtime tests
pager proves multiple actions, nested action history, and concrete JSON preview output make trace, plugin delivery pager, and runtime tests

What to compare across plugins

  • which fields are required versus defaulted
  • which actions return strings versus structured dictionaries
  • which plugin is best for watching wrapper history become visible
  • which plugin is best for reviewing field coercion pressure

Best companion guides