Files
geolocal-io/README.md
T
VPS admin 9478aaa22e docs: restore full strategy depth; add UC-01 and UC-02
- Expand CANONICAL_STRATEGY with retrieval substrates, commerce chairs,
  multi-path discovery, ingestion, quality/decommission, trust bar
- Rebalance platform vs SSP (portal is activation, not the company)
- Add principal-PM use cases for endpoint auto repair and tourism board
- Update product docs and README entry points
2026-07-18 06:00:26 +00:00

78 lines
3.3 KiB
Markdown

# geolocal.io
AI-native infrastructure for local business discovery, storytelling, visuals, and booking via MCP. Powers the long tail of independent service businesses 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 endpoint, UC-02 tourism intermediate
## What this is
geolocal.io makes local service businesses discoverable, bookable, and measurable 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 **Cal.com** and **Stripe** for booking and payment — we orchestrate, we do not rebuild those categories
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.