{"slug":"developers/08_IW_SPINE_NETWORK_MARKETPLACE_SPEC","title":"08 — IW-Spine-Network Marketplace Specification","section":"developers","sectionLabel":"Developers","status":"current","type":"document","path":"developers/08_IW_SPINE_NETWORK_MARKETPLACE_SPEC.mdx","bytes":4535,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Active frontend handoff\n**Governing contract:**\n`../architecture/IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md`\n\n## Product identity\n\nIW-Spine-Network is the public distribution identity. It has two marketplace\nartifacts:\n\n| Lane                         | Artifact                    | Surface                                                                                         |\n| ---------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------- |\n| Plugin marketplace/directory | **IW-Spine-Network Plugin** | MCP-backed app with a focused embedded host UI, workflow skills and optional templates          |\n| MCP marketplace/registry     | **IW-Spine-Network MCP**    | Remote 19-tool MCP, text/JSON fallback, optional focused widgets and the full browser Workbench |\n\nUsers never install Loader, Normalizer, Triage, Projection Engine, Governance,\nHermes, credentials or the internal MCP Pool.\n\n## Plugin marketplace experience\n\n```text\nPlugin Directory\n→ Install IW-Spine-Network Plugin\n→ host/workspace permission check\n→ connect IW app and complete OAuth\n→ Gateway resolves or creates isolated customer tenant\n→ Activation applies Customer Zero-proven reference profile\n→ discover authorised IW and explicitly delegated host capabilities\n→ render embedded IW control surface\n```\n\nThe embedded surface is a sandboxed MCP App UI, not a browser/DOM patch. It may\nshow:\n\n- active work and context summary;\n- connected-source/network status;\n- searchable entity or work picker;\n- capability/action picker;\n- exact proposal, evidence and approval confirmation;\n- governed execution progress;\n- **Open Workbench**.\n\nChatGPT or the compatible AI host controls conversation and declared tool\norchestration. The IW widget sends user intent/context through the host bridge\nand calls only declared IW server tools.\n\nIf the host has ten or twenty other apps connected, IW does not automatically\ninherit their credentials or enumerate them. The host may compose those apps in\nthe same conversation when permitted. A persistent IW network binding requires\nexplicit host delegation or a direct connector through Integration Manager.\n\n## MCP marketplace experience\n\n```text\nMCP Marketplace / Registry\n→ Connect IW-Spine-Network MCP\n→ complete OAuth, tenant selection and consent\n→ receive exact 19-tool IW Spine Tools catalog\n→ use text/JSON in ordinary MCP clients\n→ render focused widgets in MCP App-compatible clients\n→ open full browser Workbench when a complete UI is needed\n```\n\nThe browser Workbench is the primary standalone control surface and does not\nrequire ChatGPT. It calls Gateway through the one typed frontend client.\n\n## Customer Zero relationship\n\nCustomer Zero validates the exact deployment profile, activation sequence,\nwidgets, browser Workbench, 19 tools, discovery, approval and reconciliation\npath.\n\nExternal installation instantiates that **reference profile** for an isolated\ncustomer tenant. It never copies or shares Customer Zero data, credentials,\nmemory, queues, D1/KV state, R2 evidence or audit history.\n\n## Connector Marketplace distinction\n\n```text\nIW-Spine-Network Plugin = embedded host experience\nIW-Spine-Network MCP    = remote MCP + optional widget + browser Workbench\nConnector Marketplace  = in-product provider connector tray\nInternal MCP Pool       = Customer Zero/Platform operations only\n```\n\n## Frontend states\n\nThe frontend supports:\n\n- marketplace origin and package type;\n- install/connect/consent state;\n- tenant/workspace selection;\n- activation profile and progress;\n- discovered, delegated, direct and duplicate connection origins;\n- operational/degraded/revoked/partial-discovery state;\n- embedded-widget versus full-Workbench presentation;\n- human approval and governed execution status.\n\n## Public copy\n\n### Plugin listing\n\n```text\nName: IW-Spine-Network\nType: Plugin with MCP-backed app and interactive UI\nPrimary action: Install and connect\n```\n\n### MCP listing\n\n```text\nName: IW-Spine-Network\nType: Remote MCP server + optional MCP App UI\nTechnical surface: IW Spine Tools — exactly 19 tools\nPrimary actions: Connect MCP · Open Workbench\n```\n\n## V0 rule\n\nDevelopment may simulate installation only behind an explicit development flag\nand visible demo state. Customer Zero and Production must use real marketplace\nidentity, OAuth, tenant activation, discovery and Platform responses.\n"}