{"slug":"platform/capabilities","title":"Platform Capabilities","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/capabilities.mdx","bytes":3186,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nIntegrateWise provides a comprehensive platform for enterprise integration, automation, and intelligence.\n\n## Core Integration Features\n\n### Connector Ecosystem\nWe offer 100+ pre-built connectors for popular business applications:\n\n**CRM & Sales**\n- Salesforce\n- HubSpot\n- Pipedrive\n- Zoho CRM\n\n**Marketing**\n- Mailchimp\n- ActiveCampaign\n- Google Analytics\n\n**Support & Service**\n- Zendesk\n- Freshdesk\n- Intercom\n\n**Finance & Accounting**\n- QuickBooks\n- Xero\n- NetSuite\n\n**Development & Collaboration**\n- GitHub\n- GitLab\n- Jira\n- Slack\n\n### Custom Connector Development\nBuild your own connectors using our SDK.\n\nEach major component must be classified.\nClassification is required across three independent readiness dimensions.\n\n| Component                       | Lifecycle | Implemented | Wired   | Deployed | Verified E2E |\n| ------------------------------- | --------- | ----------- | ------- | -------- | ------------ |\n| Capability Registry             | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Capability Execution Engine     | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Workflow Router / Engine        | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Context Builder                 | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Execution Orchestrator          | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Metrics and Learning Structures | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Capability Discovery UI         | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n| Capability Shell Components     | UNKNOWN   | UNKNOWN     | UNKNOWN | UNKNOWN  | UNKNOWN      |\n\nThese cells must be filled with evidence, not aspiration.\n\nPopulate via:\n\n- `services/workflow` manifest and code review\n- `docs/platform-specs/05-capability-fabric.md`\n- `docs/platform-specs/11-workflow-engine.md`\n- API contracts under `docs/platform-specs/19-api-contracts.md`\n- package/service README evidence\n- Option B and Option B Wave 0 evidence\n\n---\n\n## 3. READY-STATE LANGUAGE\n\nDo not describe Capability Fabric as:\n\n- operational end-to-end\n- fully wired\n- complete\n- production ready\n- Spine connected\n\nmerely because components exist.\n\nExistence of code files is not deployed readiness. Presence in wrangler manifests alone is not verified E2E operation.\n\n---\n\n## 4. GOVERNANCE CONTRACT\n\nEvery capability execution path must include a governed boundary.\n\n```text\nCapability selection\n      ↓\nPolicy evaluation\n      ↓\nGovernance gate if required by policy\n      ↓\nExecution contract accepted\n      ↓\nCapability execution\n      ↓\nCanonical result path\n```\n\nCapability Fabric must not be documented as bypassing governance.\n\n---\n\n## 5. DOCUMENTS THAT PRECEDE THIS\n\n- docs/platform-specs/05-capability-fabric.md\n- docs/platform-specs/11-workflow-engine.md\n- docs/platform-specs/31-evolution-strategy.md\n- docs/ip/tech/CAPABILITY_RESOLVER_PATTERN.md\n- docs/archive/CAPABILITY_FIRST_ARCHITECTURE.md\n- docs/archive/CAPABILITY_FIRST_ROADMAP.md\n\nWhen conflict arises between this document and those documents, this document is canonical.\n"}