{"slug":"platform/discovery-activation-view","title":"14 · Discovery & Activation View","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/discovery-activation-view.mdx","bytes":3169,"description":"Discovery is what exists / what is available. Activation is what should become active for this org/runtime/context. Engine, Activation Manager, Activation Bridge, registration, and runtime config.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Two Different Questions\n\n| Question | System | Answers |\n|---|---|---|\n| **Discovery** | Discovery Engine | What exists / what is available across ecosystems, connectors, and capabilities? |\n| **Activation** | Activation Manager + Activation Bridge | What should become active for *this* organization / runtime / Work context? |\n\n\nDiscovery without activation would expose unavailable routes. Activation without discovery would miss what the connected world can actually do.\n\n\n```text\nEcosystems → Discovery Engine → Capability catalogue (available)\n                                    │\n                                    ▼\n                            Activation Manager\n                          (policy + tenant + context)\n                                    │\n                                    ▼\n                            Activation Bridge\n                          (runtime wiring → Fabric)\n                                    │\n                                    ▼\n                   Capability Fabric (what can be done, now — governed)\n```\n\n## Components\n\n* **Discovery Engine** — crawls connected ecosystems and connectors to enumerate capabilities, entities, and routes. Produces the *available* catalogue.\n* **Activation Manager** — decides what becomes *active* for a tenant, Work, or runtime — based on configuration, entitlements, and context.\n* **Activation Bridge** — wires active capabilities into the Capability Fabric runtime so Twin and agents can resolve them under governance.\n* **Capability registration** — active capabilities are registered with metadata, contracts, and authority requirements.\n* **Runtime configuration** — per-tenant/per-environment activation state that controls what the Workbench, Twin, and agents can actually see.\n\n## Why This Separation Matters\n\n* A capability can be *discovered* (Salesforce supports `UpdateOpportunity`) without being *activated* for tenant A, Work type B.\n* Activation is **governed and auditable** — it is not a user toggling a raw MCP tool on.\n* The [Pipeline](/work/pipeline-view) and [Platform Execution](/platform/platform-execution-view) both depend on this boundary: they never assume a capability exists without it having been discovered *and* activated for the current context.\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    What can be done, now that it's active — resolution, ADK, availability.\n  \n  \n    May it be done, for this identity, in this Work, under this policy?\n  \n  \n    Where capabilities are discovered from.\n  \n</CardGroup>\n"}