archive superseded SSP v1 with decision notes

Move docs/product/ssp.md to docs/archive/ssp-v1.md. The original
thin intent doc is superseded by ssp-refined.md which adds the full
conversational activation spec, two-phase relationship model, and
integration with UC-04/UC-05 use cases.

Update product README to reference ssp-refined.md as the operating spec.
Archive README updated to catalog the archived file.

Decision: original preserved for historical traceability; do not use
as implementation reference.

Co-authored-by: Ty <tybala@outlook.com>
Signed-off-by: Ty <tybala@outlook.com>

docs/archive/README.md

@@ -6,5 +6,6 @@ Historical materials kept for context. **Not operating documentation.**
 |------|------------|
 | [geolocal-copilot-conversation.md](./geolocal-copilot-conversation.md) | Early exploration conversation that informed the strategy |
 | [copilot-activity-history.csv](./copilot-activity-history.csv) | Activity export from that session |
+| [ssp-v1.md](./ssp-v1.md) | Original SSP intent doc — superseded by [ssp-refined.md](../product/ssp-refined.md) (2026-07-30) |
 
 Operating truth lives in [../strategy/CANONICAL_STRATEGY.md](../strategy/CANONICAL_STRATEGY.md).

docs/archive/ssp-v1.md

@@ -0,0 +1,35 @@
+# Self-Service Portal (SSP) — v1 (Archived)
+
+> **Archived:** 2026-07-30
+> **Superseded by:** [docs/product/ssp-refined.md](../product/ssp-refined.md)
+> **Decision:** The original SSP doc was a thin intent sketch — good for early alignment but insufficient as an operating spec. The refined version adds:
+> - Full conversational activation flow (no form-based fallback)
+> - Two-phase relationship model (First Hour + First Month+)
+> - Detailed UX spec with personality and tone
+> - Integration with UC-04 and UC-05 use cases
+> - Owner MCP tool definitions
+> - Product decision record (five decisions from SSP Refinement channel, 2026-07-29)
+> **Reason for archiving:** Original doc preserved for historical context and traceability. Do not use as reference for implementation.
+
+---
+
+*Original content below (as of archiving):*
+
+# Self-Service Portal (SSP)
+
+Activation experience for individual local businesses (Model 1). Important, not the whole company.
+
+## Intent
+
+Owners should feel the value before they pay: genre-aware onboarding, site scrape reflection, a live simulation of an external AI recommending and booking them, pointer install, in-browser preflight against their MCP, optimization guidance, optional partner handoff, and ongoing reports.
+
+The portal chat UI is a **test harness** for how external assistants will interpret the business — not a customer-facing chatbot product.
+
+## Spec source of truth
+
+- Narrative: [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) (product definition + priorities)
+- Operating use case: [UC-01](./use-cases/uc-01-endpoint-auto-repair.md)
+
+## Build status
+
+Not implemented. Engineering Priority 0 includes portal spine after HTTP MCP is real enough to preflight against.

docs/product/README.md

@@ -7,7 +7,7 @@ Product definitions for what we build and sell. Align with [Canonical Strategy](
 1. [overview.md](./overview.md) — platform map and surfaces  
 2. [use-cases/](./use-cases/) — canonical specs (start with UC-01 and UC-02)  
 3. [genre-packs.md](./genre-packs.md) — vertical primitives  
-4. [ssp.md](./ssp.md) — Self-Service Portal as **activation**, not the whole product  
+4. [ssp-refined.md](./ssp-refined.md) — Self-Service Portal, refined spec (conversational, two-phase)  
 5. [intermediate.md](./intermediate.md) — tourism/chamber intermediate surface  
 
 ## Center of gravity

docs/product/ssp.md

@@ -1,18 +0,0 @@
-# Self-Service Portal (SSP)
-
-Activation experience for individual local businesses (Model 1). Important, not the whole company.
-
-## Intent
-
-Owners should feel the value before they pay: genre-aware onboarding, site scrape reflection, a live simulation of an external AI recommending and booking them, pointer install, in-browser preflight against their MCP, optimization guidance, optional partner handoff, and ongoing reports.
-
-The portal chat UI is a **test harness** for how external assistants will interpret the business — not a customer-facing chatbot product.
-
-## Spec source of truth
-
-- Narrative: [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) (product definition + priorities)  
-- Operating use case: [UC-01](./use-cases/uc-01-endpoint-auto-repair.md)
-
-## Build status
-
-Not implemented. Engineering Priority 0 includes portal spine after HTTP MCP is real enough to preflight against.