Carlos Florênciostatus, system, specification_version, migration, owners
| status | system | specification_version | migration | owners | |
|---|---|---|---|---|---|
| draft | integrations | 1 | in_progress |
|
Integration system
Purpose
The integration system owns connections to external services and the provider-specific contracts that synchronize or act on external work.
Ownership
This system owns provider credentials, provider identity, external issue and pull-request synchronization, integration settings, provider-aware review automation, external question or answer flows, and provider-specific UI outcomes that expose those contracts.
Exclusions
- Generic authentication belongs to the auth system.
- Durable Kandev tasks belong to the task system.
- Plugin-owned services belong to the plugin system.
- Reusable presentation contracts without provider state belong to the UI system.
Specification map
Requirements
- Azure DevOps Integration
- Bitbucket Connector Plugin
- Claude Fork Review Allowlist
- Clickable integration cards
- Integration Enable/Disable Toggle & Nav Visibility
- External MCP Endpoint
- External Question Answering — authorized, discoverable, idempotent clarification resolution
- Workspace GitHub Authentication
- GitHub PR Merge Queue
- GitHub PR Merge Queue Recovery
- GitHub task pull request sync coordination
- GitLab Integration
- GitLab MR Status Chip
- GitLab MR Badge on the Sidebar and Tasks-List Rows
- GitLab Workflow Sync
- Jira Watcher Task Prompts
- Jira Ticket Status Filter
- MCP Tool Argument Validation
- Pull request outcome attribution
- Pull request link copy actions
- Provider-Aware Review Automation Runtime
- Slack Integration
System design
- External MCP Saved Prompt Reads
- Azure DevOps Integration System Design Part 1
- Azure DevOps Integration System Design Part 2
- Bitbucket Connector Plugin System Design Part 1
- Bitbucket Connector Plugin System Design Part 2
- External Question Answering — authorized, discoverable, idempotent clarification resolution System Design Part 1
- External Question Answering — authorized, discoverable, idempotent clarification resolution System Design Part 2
- External Question Answering — authorized, discoverable, idempotent clarification resolution System Design Part 3
- External Question Answering — authorized, discoverable, idempotent clarification resolution System Design Part 4
- Workspace GitHub Authentication System Design Part 1
- Workspace GitHub Authentication System Design Part 2
- Workspace GitHub Authentication System Design Part 3
- GitHub PR Merge Queue
- GitHub PR Merge Queue Recovery
- GitHub task pull request sync coordination
- Pull request link copy actions
- GitLab Integration System Design Part 1
- GitLab Integration System Design Part 2
- GitLab MR Status Chip System Design Part 1
- GitLab MR Status Chip System Design Part 2
- GitLab MR Status Chip System Design Part 3
- GitLab MR Status Chip System Design Part 4
- GitLab MR Status Chip System Design Part 5
- GitLab MR Badge on the Sidebar and Tasks-List Rows System Design Part 1
- GitLab MR Badge on the Sidebar and Tasks-List Rows System Design Part 2
- GitLab MR Badge on the Sidebar and Tasks-List Rows System Design Part 3
- Jira Watcher Task Prompts
Migration record
Migration remains in progress while legacy source detail is extracted from the canonical requirement and system-design documents above.