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

docs: restore full strategy depth; add UC-01 and UC-02

Browse Source 
- 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
This commit is contained in:
VPS admin
2026-07-18 06:00:26 +00:00
parent 3f9c86f823
commit 9478aaa22e
12 changed files with 680 additions and 188 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/product/overview.md
+28 -9
View File
@@ -1,20 +1,39 @@
# 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.
geolocal.io is **AI-readiness infrastructure** for local services. Assistants call structured endpoints. Businesses own their presence. Intermediates and partners help distribution. Booking and payments are orchestrated through specialists, not rebuilt here.
See [Canonical Strategy](../strategy/CANONICAL_STRATEGY.md) sections 4–5 for the full product definition and the four business models.
## Platform vs activation
| Layer | Responsibility |
|-------|----------------|
| **Platform** | Multi-tenant MCP, multi-path discovery pointers, ingestion/content sync, genre packs, telemetry, quality enforcement (including quarantine/decommission), intermediate aggregation |
| **Activation** | Self-Service Portal and assisted onboarding so ordinary operators can turn the platform on |
| **Distribution** | Tourism boards, chambers, agencies |
The portal is how Model 1 scales. It is not the product definition of the company.
## 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 |
| Genre packs | Vertical structure for agents + owners | Specified; auto pack first via UC-01 |
| Self-Service Portal | SMB owners / delegates | Specified in strategy + [ssp.md](./ssp.md); not built |
| Intermediate MCP + board tools | Tourism boards / chambers | Specified via UC-02; not built |
| Partner flows | Agencies / local web | Distribution; after core attach |
## Related docs
## Canonical use cases
- [ssp.md](./ssp.md)
- [intermediate.md](./intermediate.md)
- [genre-packs.md](./genre-packs.md)
- [UC-01 Endpoint — auto repair](./use-cases/uc-01-endpoint-auto-repair.md)
- [UC-02 Intermediate — tourism board](./use-cases/uc-02-intermediate-tourism-board.md)
## Where we sit in the assistant journey
We barely try to own pure discovery SEO. We are primary for evaluation, selection, and complementary fulfillment, and second chair for interpretation and feedback. Detail: [Canonical Strategy §5](../strategy/CANONICAL_STRATEGY.md).
## Related
- [genre-packs.md](./genre-packs.md)
- [ssp.md](./ssp.md)
- [intermediate.md](./intermediate.md)
- Engineering priorities in the strategy, roadmap under `docs/engineering/`