# geolocal.io

AI-native infrastructure for local business discovery via MCP. Powers the long tail of independent brick-and-mortar — services **and** local retail — that big platforms do not serve cleanly in the agent era.

## Start here

1. **[Canonical Strategy](./docs/strategy/CANONICAL_STRATEGY.md)** — operating truth (final draft)
2. **[North Star](./NORTH_STAR.md)** — short compass
3. **[Product overview](./docs/product/overview.md)** — platform vs activation
4. **[Use cases](./docs/product/use-cases/)** — UC-01 services, UC-02 tourism, UC-03 local retail

## What this is

geolocal.io makes **local businesses** discoverable and actionable inside AI assistants by:

- Hosting a **multi-tenant MCP** agents can call for structured business truth
- Giving businesses a **simple pointer** on their own site (no servers for them to run)
- Providing a **Self-Service Portal** so owners can see and test how AI understands them
- Working with **tourism boards, chambers, and partners** for distribution
- Integrating booking, payment, and later inventory partners where those paths apply — we orchestrate, we do not rebuild Shopify or Calendly

Scope includes **local services and local retail** with real presence (see strategy §1a). Pure online e-commerce is out of scope.

We are not a consumer destination site. We are infrastructure.

## Who should read what

### Partners (agencies, SEO, chambers)

1. [Ideal customer profile](./docs/gtm/ideal-customer-profile.md)
2. [Channel strategy](./docs/gtm/channel-strategy.md) and [Sales and marketing](./docs/gtm/sales-and-marketing.md)
3. [Partner one-pager](./docs/gtm/partner-one-pager.md)

### Investors

1. [Canonical Strategy](./docs/strategy/CANONICAL_STRATEGY.md)
2. [Market data and analysis](./docs/investors/market-data-and-analysis.md)
3. [Business and financial model](./docs/investors/business-and-financial-model.md) and [Moats and risks](./docs/gtm/competitive/moats-and-risks.md)

### Engineering

1. [Canonical Strategy](./docs/strategy/CANONICAL_STRATEGY.md) priorities
2. [Technical roadmap](./docs/engineering/technical-roadmap.md)
3. [code/](./code/) — MCP MVP (TypeScript)
4. [ADRs](./docs/engineering/adrs/)

## Repository map (Phase A)

```text
geolocal-io/
├── NORTH_STAR.md
├── README.md
├── code/                      # MCP server MVP (later → apps/mcp-gateway)
└── docs/
    ├── strategy/              # CANONICAL_STRATEGY.md (operating truth)
    ├── product/               # SSP, intermediate, genre packs
    ├── gtm/                   # channels, sales, competitive/
    ├── investors/
    ├── engineering/           # roadmap + adrs/
    ├── legal/
    └── archive/               # historical exploration only
```

Later monorepo phases add `apps/`, `packages/`, `genres/`, and `infra/` without changing the docs contract above.

## Status

| Area | Status |
|------|--------|
| **Canonical strategy** | Final draft |
| **Market / GTM / legal docs** | Present (some GTM still pre-strategy framing) |
| **Product docs** | Scaffolded |
| **MCP server (`code/`)** | MVP — 5 tools, TypeScript, Railway-ready |
| **Self-Service Portal** | Specified; not built |
| **HTTP multi-tenant gateway** | Priority 0 |

## Doc governance

If a document conflicts with [docs/strategy/CANONICAL_STRATEGY.md](./docs/strategy/CANONICAL_STRATEGY.md), fix the conflict on purpose. Historical exploration lives in [docs/archive/](./docs/archive/), not in operating GTM.