Define solution vs connector terminology across the ecosystem

[krisrowe]

Problem

The terms "solution" and "connector" are used loosely across the ecosystem. echofit is called a "solution" on echomodel.ai and in brand docs, but there's no clear definition of what makes something a solution vs a connector. With the new Connectors section being added (#1), these concepts need crisp definitions that hold up across all repos and sites.

Current confusion

• echoskill.md in pp calls echofit a "solution app"
• echomodel.ai has a "Solutions" section containing echoskill and echofit
• echoskill is a skills marketplace, not a solution in the same sense as echofit
• gworkspace-access, monarch-access, ticktick-mcp are about to be labeled "connectors" but monarch-access was previously listed alongside echofit as a solution
• The echosphere portal doesn't distinguish between the two

Proposed definitions

Connector — an MCP server that gives AI agents access to an external service's data and actions. It connects an agent to something. Thin integration layer, no domain logic beyond what the service API provides. Examples: gworkspace-access (connects to Google Workspace), monarch-access (connects to Monarch Money), ticktick-mcp (connects to TickTick).

Solution — a product built on top of the ecosystem that delivers domain-specific value. It has its own brand, domain, user experience, and business logic beyond raw API access. A solution may use connectors and frameworks internally. Examples: echofit (fitness/nutrition tracking — has its own food catalog, meal analysis, health insights beyond raw data logging).

Key distinction: A connector asks "how do I access this service?" A solution asks "how do I solve this problem for users?" A connector is infrastructure; a solution is a product.

echoskill is neither — it's a marketplace/platform. It should be in its own category or simply listed as a peer brand on echosphere without the "solution" label.

Work breakdown

• Define "solution" and "connector" in echosphere BRAND.md
• Update echomodel.ai: rename "Solutions" section to reflect actual contents (echoskill is a platform, echofit is a solution — they shouldn't share a label)
• Update echosphere.dev if terminology appears there
• Update pp brand docs (echoskill.md, echofit.md, echosphere.md) to use consistent terminology
• Audit echomodel.ai repo descriptions for consistency
• Ensure new Connectors section (Add MCP Connectors section to echomodel.ai #1) aligns with these definitions