docs: Phase A repo structure — archive, product, kebab-case

- Move copilot history and CSV to docs/archive/
- Add docs/product/ (SSP, intermediate, genre packs) and engineering/adrs/
- Rename all spaced/special-char doc paths to kebab-case
- Nest competitive GTM under docs/gtm/competitive/
- Point README and NORTH_STAR at CANONICAL_STRATEGY
- Leave code/ unchanged for later monorepo Phase B

docs/product/README.md

@@ -0,0 +1,13 @@
+# Product
+
+Product definitions for what we build and sell. Aligns with [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md).
+
+| Doc | Purpose |
+|-----|---------|
+| [overview.md](./overview.md) | Product map across the four models |
+| [ssp.md](./ssp.md) | Self-Service Portal (primary SMB experience) |
+| [intermediate.md](./intermediate.md) | Tourism boards, chambers, visitor bureaus |
+| [genre-packs.md](./genre-packs.md) | Vertical primitives strategy |
+| [use-cases/](./use-cases/) | Canonical use cases (to be filled) |
+
+These folders start thin on purpose. Expand them as decisions lock; do not reintroduce conflicting product stories in GTM-only docs.

docs/product/genre-packs.md

@@ -0,0 +1,18 @@
+# Genre packs
+
+Generic business fields are scaffolding. Durable differentiation is **genre-specific primitives** — structured tools and schemas that match how a vertical actually works.
+
+## Planned early packs
+
+- Auto repair  
+- Beauty  
+- Home services  
+- Tourism activity (especially with destination pilots)
+
+## Detail source
+
+[Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) (§5.3).
+
+## Repo note (future)
+
+Genre packs will live under top-level `genres/` in a later monorepo phase. Product intent is documented here first.

docs/product/intermediate.md

@@ -0,0 +1,15 @@
+# Intermediate product (tourism, chambers, visitor bureaus)
+
+Model 2: destinations and membership organizations as discovery nodes.
+
+## Intent
+
+One intermediate relationship should bring many member endpoints online. Boards get an aggregating MCP, member onboarding (via SSP patterns), and a simple dashboard of hits and category demand. Funding often sits in lodging-tax or destination marketing budgets.
+
+## Detail source
+
+[Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) (§4 Model 2, §7 GTM wedge).
+
+## Build status
+
+Not implemented. Engineering Priority 1 after Model 1 spine is real.

docs/product/overview.md

@@ -0,0 +1,20 @@
+# Product overview
+
+geolocal.io ships **AI-readiness infrastructure** for local services: hosted multi-tenant MCP, a discovery pointer on the business site, the Self-Service Portal, intermediate (destination/chamber) surfaces, and later telemetry and graph products.
+
+See [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) sections 4–5 for the full product definition and the four business models.
+
+## Surfaces
+
+| Surface | Audience | Status |
+|---------|----------|--------|
+| MCP gateway | AI agents | MVP in `code/` (stdio); HTTP is Priority 0 |
+| Self-Service Portal | SMB owners | Specified in strategy; not built |
+| Intermediate dashboard | Tourism boards / chambers | Specified; not built |
+| Partner surfaces | Agencies / SEO | Distribution; after core attach |
+
+## Related docs
+
+- [ssp.md](./ssp.md)
+- [intermediate.md](./intermediate.md)
+- [genre-packs.md](./genre-packs.md)

docs/product/ssp.md

@@ -0,0 +1,17 @@
+# Self-Service Portal (SSP)
+
+Primary product experience for individual local businesses (Model 1).
+
+## Intent
+
+Owners should feel the value before they pay: genre-aware onboarding, site scrape reflection, a live simulation of an 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* AI assistants will interpret the business — not a customer-facing chatbot we sell as the product.
+
+## Detail source
+
+Full narrative and priorities: [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) (§5 Self-Service Portal, §10 priorities).
+
+## Build status
+
+Not implemented. Engineering Priority 0 includes the portal spine once HTTP MCP is underway.

docs/product/use-cases/README.md

@@ -0,0 +1,5 @@
+# Use cases
+
+Canonical use cases (Bob’s Garage, destination board, etc.) will land here as structured product specs.
+
+Until then, narrative examples remain in the strategy and archive; do not treat the archive as the product spec.