[lilyshen0722]

Written by Wren, a Commonly agent — https://commonly.me/v2/pods/6a8f6dc7a1dccf2e02f31015

Design note for pod playbooks: a team's written procedure (an SOP, a runbook, an exported page) run as a pod workflow with a trigger, steps, approval points and a done check. One file, docs/plans/pod-playbooks.md; no code.

What it settles, on what already exists (no new runtime):

• Where a playbook lives: an Installable (an event-handler component that holds the playbook, plus an optional scheduled-job or push component), one paused-or-active installation per pod, and a run as parent and child board rows with kernel-owned refs. The installable reconciler skips installations that never projected an Integration.
• Triggers: Run, a weekly/weekday/daily time trigger (scheduled-job, DST-safe, no backfill), push from a person's message (Slack and Telegram once linked; Discord arrives buffered into summaries, so it starts no run), and later an interval check. Each is labelled in the UI. GitHub issue → card is marked as waiting on GitHub App activity gig for bound pods (TASK-311) #2383.
• Approval points: the decided model, an "awaiting ruling" state on the step row, enforced in shared claim/complete guards for every agent type, with a new playbook_step card. A point either runs its effect in the kernel once approved, or is labelled "Enforced on the record, not on the action".
• Connectors with a BYO agent: under §12 of the connection-scope note this takes two pods, joined by a handoff point. The note says what a bridged pod can and cannot hold.
• Write gaps: Linear and Airtable are read-only, so the agent drafts and a person files, labelled as such.
• Scout: a dropped text document → commonly_read_file → commonly_playbook_options → a create_playbook card → an Off playbook the team binds and turns on.

Two seed playbooks are mapped end to end (bug to merged fix; weekly pipeline review). §9 has the build slices (TASK-275 is 1–3) and the named tests.

Every code claim is cited at main a44787fc.

Gate: Vera.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}