Ty_Tech/geolocal-io
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
- 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
This commit is contained in:
VPS admin
2026-07-18 05:23:39 +00:00
parent 36853f3bab
commit 3f9c86f823
32 changed files with 250 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+50 -60
View File
@@ -1,86 +1,76 @@
# geolocal.io
> AI-native infrastructure for local business discovery, storytelling, visuals, and booking via MCP. Powers the long tail of independent SMBs ignored by big platforms.
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.
## What Is This?
## Start here
`geolocal.io` makes local service businesses discoverable, bookable, and payable in the agentic AI economy.
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)** — what we build
We do this by:
## What this is
- **Hosting a multi-tenant MCP server** that exposes rich, structured business data (story, visuals, services, pricing, availability) to any AI agent.
- **Providing a simple JSON pointer** (`/.well-known/mcp-server`) that any business can add to their website to connect to our hosted MCP server—no coding required.
- **Enabling a complete transaction loop** by integrating with Cal.com for booking and Stripe for payment capture.
- **Building a partner-first distribution engine** by working through agencies, SEO consultants, and Chambers of Commerce who already serve these businesses.
- **Creating a self-reinforcing data network** where AI agents provide verification and competitive intelligence data through our "related businesses" handshake.
geolocal.io makes local service businesses discoverable, bookable, and measurable inside AI assistants by:
We are not a destination site. We are an invisible, critical layer of infrastructure that powers the agentic economy's discovery of local businesses.
- 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
## The Problem We Solve
We are not a consumer destination site. We are infrastructure.
- **45% of consumers** now use AI tools to find local businesses—up from just **6% one year earlier**.
- **ChatGPT recommends just 1.2% of local businesses**, according to SOCi's 2026 Local Visibility Index.
- **AI is now the third most-used business discovery channel**, behind only Google and Facebook.
## Who should read what
The major platforms (Google, Yelp, OpenAI) are building MCP infrastructure to serve their own data. They are **not** building infrastructure to serve the businesses themselves. We bridge that gap.
### Partners (agencies, SEO, chambers)
## Quick Start
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)
### For Partners (Agencies, SEO Consultants, Chambers)
### Investors
1. Read the **[Ideal Customer Profile](./docs/gtm/Ideal%20Customer%20Profile.md)** to understand who we target.
2. Review the **[Channel Strategy](./docs/gtm/ChannelStrategy.md)** and **[Sales and Marketing](./docs/gtm/Sales%20and%20marketing.md)** for the playbook.
3. Use the **[Partner One-Pager](./docs/gtm/Partner%20One-Pager.md)** as your sell-sheet.
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)
### For Investors
### Engineering
1. Read the **[North Star](./NORTH_STAR.md)** document for our vision and principles.
2. Review the **[Market Data & Analysis](./docs/investors/Market%20Data%20&%20Analysis.md)** for the opportunity size.
3. Explore the **[Business and Financial Model](./docs/investors/Business%20and%20financial%20model.md)** and **[Competitive Moats & Risks](./docs/gtm/Competitive%20moats%20and%20risks.md)** for our defensible position.
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/)
### For Developers & Engineers
## Repository map (Phase A)
1. Read the **[Technical Roadmap](./docs/engineering/technical%20roadmap.md)** for our phased implementation plan.
2. Explore the **[code/](./code/)** directory for the MCP server implementation.
3. See **[package.json](./code/package.json)** for dependencies and scripts.
## Repository Structure
```
```text
geolocal-io/
├── NORTH_STAR.md # Single source of truth for vision & principles
├── README.md # This file
├── code/ # MCP server implementation (TypeScript)
│ ├── src/
│ │ ├── index.ts # Server entry point (stdio transport)
│ │ ├── mcp-server.ts # Tool registration (5 MCP tools)
│ │ ├── config.ts # Environment configuration
│ │ ├── manifest-generator.ts # /.well-known/mcp-server JSON
│ │ ├── db/ # PostgreSQL schema + seed data
│ │ ├── tools/ # get_business_info, get_hours, etc.
│ │ └── routes/ # Multi-tenant gateway
│ ├── package.json
│ ├── tsconfig.json
│ ├── Dockerfile
│ └── railway.json
├── NORTH_STAR.md
├── README.md
├── code/ # MCP server MVP (later → apps/mcp-gateway)
└── docs/
├── investors/ # Market data, financial model
├── gtm/ # ICP, channel strategy, partner one-pager
├── engineering/ # Technical roadmap
└── legal/ # Data flow, partnership agreement, IP notes
├── 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 |
| :--- | :--- |
| **Strategy & Vision** | ✅ Complete |
| **Market Data & Analysis** | ✅ Complete |
| **Competitive Intelligence** | ✅ Complete |
| **Business & Financial Model** | ✅ Complete |
| **Product & Technical Roadmap** | ✅ Complete |
| **GTM Strategy** | ✅ Complete |
| **Legal & Compliance** | ✅ Complete |
| **MCP Server (code/)** | ✅ MVP — 5 tools, TypeScript, Railway-ready |
|------|--------|
| **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.