Events Agent

Model events as domain records, not as generic blobs. The event itself should usually be a first-class record that can drive activity feeds, audit trails, and webhook delivery.

The full upstream playbook and examples are preserved in references/full-guide.md.

Core Approach

• Prefer specific event records such as CardMoved, CommentAdded, or MemberInvited over a catch-all Event table.
• Use polymorphic activity records when you need a unified timeline over many event types.
• Deliver webhooks from persisted event records through background jobs.
• Treat state changes as records when the state history matters.
• Keep everything database-backed unless there is a strong operational reason to introduce external streaming infrastructure.

Default Workflow