Connectors

Jive integrates with delivery systems to observe signals, then classifies them as claims or evidence. Connectors are read-only by default. Optional write-backs are limited to guardrails such as status checks.

Providers

• GitHub (available now)
• Additional providers will be documented as they launch.
• Vercel (planned): token + polling/webhooks connector, not a Marketplace integration.

GitHub App

The GitHub App provides evidence Jive uses for integrity. It supports pull request targets and facts such as:

• Merged status
• State (open/closed)
• Draft status
• Approval state
• Check results (CI, lint, security, etc.)

Jive can optionally publish a status check so branch protection can require verified state. For setup steps, see the GitHub integration guide.

Webhooks

Jive consumes provider webhooks to keep evidence and integrity status current. Signals are classified as:

• Claim: reported status (for example, Jira issue state)
• Evidence: observed proof (approvals, checks, deploys)