Current

08 — IW-Spine-Network Marketplace Specification

Status: Active frontend handoff
Governing contract:
../architecture/IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md

Product identity

IW-Spine-Network is the public distribution identity. It has two marketplace
artifacts:

Lane	Artifact	Surface
Plugin marketplace/directory	IW-Spine-Network Plugin	MCP-backed app with a focused embedded host UI, workflow skills and optional templates
MCP marketplace/registry	IW-Spine-Network MCP	Remote 19-tool MCP, text/JSON fallback, optional focused widgets and the full browser Workbench

Users never install Loader, Normalizer, Triage, Projection Engine, Governance,
Hermes, credentials or the internal MCP Pool.

Plugin marketplace experience

Plugin Directory
→ Install IW-Spine-Network Plugin
→ host/workspace permission check
→ connect IW app and complete OAuth
→ Gateway resolves or creates isolated customer tenant
→ Activation applies Customer Zero-proven reference profile
→ discover authorised IW and explicitly delegated host capabilities
→ render embedded IW control surface

The embedded surface is a sandboxed MCP App UI, not a browser/DOM patch. It may
show:

active work and context summary;
connected-source/network status;
searchable entity or work picker;
capability/action picker;
exact proposal, evidence and approval confirmation;
governed execution progress;
Open Workbench.

ChatGPT or the compatible AI host controls conversation and declared tool
orchestration. The IW widget sends user intent/context through the host bridge
and calls only declared IW server tools.

If the host has ten or twenty other apps connected, IW does not automatically
inherit their credentials or enumerate them. The host may compose those apps in
the same conversation when permitted. A persistent IW network binding requires
explicit host delegation or a direct connector through Integration Manager.

MCP marketplace experience

MCP Marketplace / Registry
→ Connect IW-Spine-Network MCP
→ complete OAuth, tenant selection and consent
→ receive exact 19-tool IW Spine Tools catalog
→ use text/JSON in ordinary MCP clients
→ render focused widgets in MCP App-compatible clients
→ open full browser Workbench when a complete UI is needed

The browser Workbench is the primary standalone control surface and does not
require ChatGPT. It calls Gateway through the one typed frontend client.

Customer Zero relationship

Customer Zero validates the exact deployment profile, activation sequence,
widgets, browser Workbench, 19 tools, discovery, approval and reconciliation
path.

External installation instantiates that reference profile for an isolated
customer tenant. It never copies or shares Customer Zero data, credentials,
memory, queues, D1/KV state, R2 evidence or audit history.

Connector Marketplace distinction

IW-Spine-Network Plugin = embedded host experience
IW-Spine-Network MCP    = remote MCP + optional widget + browser Workbench
Connector Marketplace  = in-product provider connector tray
Internal MCP Pool       = Customer Zero/Platform operations only

Frontend states

The frontend supports:

marketplace origin and package type;
install/connect/consent state;
tenant/workspace selection;
activation profile and progress;
discovered, delegated, direct and duplicate connection origins;
operational/degraded/revoked/partial-discovery state;
embedded-widget versus full-Workbench presentation;
human approval and governed execution status.

Public copy

Plugin listing

Name: IW-Spine-Network
Type: Plugin with MCP-backed app and interactive UI
Primary action: Install and connect

MCP listing

Name: IW-Spine-Network
Type: Remote MCP server + optional MCP App UI
Technical surface: IW Spine Tools — exactly 19 tools
Primary actions: Connect MCP · Open Workbench

V0 rule

Development may simulate installation only behind an explicit development flag
and visible demo state. Customer Zero and Production must use real marketplace
identity, OAuth, tenant activation, discovery and Platform responses.